Windows 10 Folder Properties File Count Wrong

Posted on
Windows 10 Folder Properties File Count Wrong Rating: 6,3/10 1649 votes
  1. Windows 10 Folder Properties Incorrect
  2. Folder Properties Show More Files

Jun 18, 2019  Windows now reported 151,879 files & 12,753 folders totalling 164,632 (one less than that reported by Everything) and occupying 64.4 GB of drive space. Seems removing the long file path solved the issue; returning it to the directory tree resulted in only 44,743 files reported in Windows properties.

File

Hi VinOth, Windows and indeed Windows Explorer has always been useless when it comes to working out where your hard drive space is being used.Click the link below to download a small free utility called Treesize. Using that tool, you will instantly see where this space is being used and the exact size of foldersStandard Disclaimer This is a non-Microsoft website.

Windows 10 Folder Properties File Count Wrong

The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products).

Windows 10 Folder Properties Incorrect

Thoroughly research anyproduct advertised on the site before you decide to download and install it. Power to the Developer! MSI GV72 - 17.3', i7-8750H (Hex Core), 32GB DDR4, 4GB GeForce GTX 1050 Ti, 256GB NVMe M2, 2TB HDD. I too am seeing this incorrect folder size problem. But my experience is a little different, namely that I am only seeing it on a specific external device - a Seagate 2TB external HDD.A recently written parent folder is under reporting the size of its sub folders by over 50%.The same folder written to a USB memory stick reports correctly.I haven't noticed this problem on my internal Windows 10 HDD as of yet.Until I read this thread, I thought I was going mad!I'd be grateful for any thoughts on this. I am seeing this bug in 1803 on my C: drive, which is a Samsung 970 Pro SSD. I also see it on regular internal hard drives.It has nothing to do with external drives or hidden files.

The problem is caused by very long folder names and/or paths. Folder propertiesfile enumeration appears to break when it encounters one of these.The potential for loss of data seems very real.

One scenario: a folder containing a set of nested folders forming a long path that breaks folder properties, with no files in any of the folders. This top-levelsubfolder is followed by other subfolders with thousands of files. Folder properties would show 0 files thanks to this bug.

Folder Properties Show More Files

User shift-deletes the root folder thinking it's safe and watches in horror as their data is purged.Browsers and modern dev tools like npm create these long paths all the time! It's a really dangerous bug and it needs immediate attention.