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
    2018-12-07T21:09:42+00:00

    I'd guess it's related to path name length.

    It is. I have over 8 TB of data in a folder- which I normally back up.   When I have files with total file paths over about 240 characters (I have not tested the actual file path length) 1. I get erroneous folder sizes in File explorer-- and 2. I cannot edit the filename without moving it to a higher level first.  

    I have been using TLPD (Too Long File Path) https://sourceforge.net/projects/tlpd/ to find longer files and editing them (It is an immense comic book collection which I manage and maintain- so removing characters is not an issue usually) which is excruciatingly painful to do- even in batches using Renamer.

    I have enabled this local policy now- and hope to find it takes care of the problems altogether.

    1. Open Group Policy Editor (Press Windows Key and type gpedit.mscand hitEnterkey*.*
    2. Navigate to the following directory:  Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem
    3. Click Enable NTFS long paths option and enable it.

    I hope this works!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-12-07T20:50:01+00:00

    My issue was resolved, unfortunately I don't remember how?  I think it was one of the Microsoft Updates that fixed it?  Sorry really can't help, it was so long ago!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-09-18T14:09:49+00:00

    So it's a path length problem! Thought I was going out of my mind when copying large folders with multi-level subfolders from one drive to another. It told me the correct size on the original, but suggested I had failed to copy multiple GB to the destination. In the end I installed a handy little utility called TreeSize Free which assured me that both directories were identical. Spent a lot of time scratching my head before that.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-09-03T02:42:34+00:00

    It's definitely related to 1803 as I had a backup of files and folders on an external Seagate USB drive which were created before I installed 1803.

    After reading this post I created a backup of the exact same files and folders which had not changed since the backup before 1803 and now the properties are different.

    This was a previous issue that Microsoft fixed and whatever they have done in 1803, they have created the issue again, so let's get it fixed again Microsoft!!!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-08-13T14:49:41+00:00

    Windows has a limit of 260 characters (The system allows paths with more characters, but apparently has some problems). Use the Path lenght Checker tool to check your folders for paths that exceed these limits. I did this in my folders and this wrong size reading problem was fixed.

    Was this answer helpful?

    0 comments