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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-11-12T21:20:21+00:00

    Hi Joachim,

    As a matter of fact I did download the free version and played with it for a bit, I really do like it.

    I haven't had a chance yet to dive into my windows folder sizes and compare the 2, I'll post something when I get the chance.

    What I have noticed is that the disk usage section of the new control panel, "Settings" I guess they call it, is useless.

    Settings/System/Storage is it's GUI path

    If you go down to "view storage used on other drives"

    I keep "My Documents" on my D drive it says that I have 4.41 gigs used, even windows explorer says it's 203 gigs

    Even if I subtract out my pictures music and video folders there is still over 7 gigs left, I can't even find a single folder that's 4.41 gigs on the drive!

    That issue probably deserves it's own thread (maybe it has one)

    Have a great week

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-11-13T16:41:53+00:00

    The bug introduced by Microsoft with the 1803 release was fixed in the 1903 release for Windows 10. I think someone posted that the Server Version still has the problem?

    Was this answer helpful?

    0 comments