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 No comments

102 answers

Sort by: Oldest
  1. 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 No comments
  2. 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 No comments
  3. Anonymous
    2019-01-29T04:27:19+00:00

    This seems to be a recent issue that occurred for me after one of the many updates Microsoft provides. I just noticed this December 16, 201****03? I agree with the other post that this creates some potentially catastrophic situations and you should really figure it out and fix it ASAP!

    Yes this is catastrophic. And the catastrophe has just occurred for me.  After spending the last couple weeks consolidating tens of terabytes of data across numerous backup USB drives and eliminating duplicate files off of older backup drives with the help of Duplicate Cleaner, I know realize that I have likely deleted many old unique original files that Microsoft Windows Explorer said were empty trees.  I would use folder properties to check a directory tree to see if there were any files remaining, and if it was zero I would permanently delete (Shift-Del) the tree in Microsoft Windows Explorer.  I only discovered this problem today when I figured out what Windows Explorer folder properties was reporting at one level was far different than the sum at the next level up the tree.  Some of the drives have already been overwritten - and trying to recover files across this many devices would be far more work than I have time for. I'm running Windows 10 1803.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2019-02-01T21:16:09+00:00

    Same here. Multiple drives and TB's of information all displaying inaccurate sizes. Sometimes you just select 5 files in a directory that add up to 42MB, but the right click properties claims 0.99GB. It's all over the place. Making backing stuff up and finding files that need to be removed extremely difficult to the point that I have given up. Too much information to sort through without the proper help from Windows.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2019-02-03T11:51:08+00:00

    It didn't happen with Windows 7.

    The basis of an operative system it's to manage files, and Wnidows 10 is showing that it isn't capable of doing that simple task properly.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments