Windows File Explorer Not Showing Correct Folder Size If Folder Named 'Applications'

Anonymous
2018-05-03T21:08:26+00:00

Since installing the 1803 update, Windows File Explorer doesn't display the correct folder size if the folder is named 'Applications'.

There seems to be a bug that if the folder name is 6 characters or more and starts with 'Appli', the folder size shows significantly less than it actually is.  For example if the folder is named 'Apps' or 'Appli', it will display the size correctly.  If however it is named 'Applications' or 'Applix' or 'Appliy', then it won't display correctly.

The Feedback app doesn't work on my computer due to having telemetry settings set to 'Basic', therefore I am reporting the bug here instead.

OS Version:

Windows 10 Pro X64 (17134.1, 1803)

Screenshots:

Windows for home | Windows 10 | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

102 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-01-27T18:55:21+00:00

    Another one with the same problem.

    I usually copy files from a device to another and after that I compare the exact sizes. Sometimes, it reads correctly from the first device but with quantity errors on the second. And no way to solve it, even having both folders the same names.

    Fortunately, at least with TreeSize I can compare the number of files correctly... but it has no sense to need to use an external software to do this task...

    Regards,

    Miguel

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-01-24T02:44:29+00:00

    Correct you are!

    If I dig all the way down to a file it always reports it's size correctly, the issue is with parent (and grandparent) folders reporting incorrectly.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-01-23T21:38:57+00:00

    Just spent several hours undeleting a drive I thought I had lost tons of data from when I moved it from one drive to another - the folder size was reporting I was missing 50Gigs+ of data....

    Turns out it had actually copied correctly - all files were actually there - but were getting miscounted - it was the bug reported here I hadnt been aware could happen until now....

    MS please fix... its a real issue.

    Note: sometimes - the file properties on the file explorer RIGHT pane reports the correct file size - but properties on the parent folder gives incorrect file size when I do a file properties on the parent folder.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-01-10T08:30:49+00:00

    why hasnt this been fixed yet? its a huge bug yet they ignore it?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-01-08T04:22:47+00:00

    Bump.

    OP must have had some files buried deep within the structure that got "revealed" when that folder name up above was shortened.

    Just ran into this problem with a backup 2 TB external hard drive that's showing only 59 GB used in File Explorer in Windows 10, but the drive Properties shows 843 GB used. As another poster mentioned, who's responsible if the folder shows 0 bytes size erroneously and it gets deleted? What exactly does M$ use internally to avoid this problem themselves?

    Ridiculous that M$ hasn't had any official presence since the very first boilerplate "send us a bug report" response, over 7 months ago.

    Was this answer helpful?

    0 comments