This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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:
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.
Seeing the same problem. I initially reported it here.
Have seen this behavior on another PC as well.
I have tried to set the parameter in the registry to allow long folders/filenames but it doesn't seem to have done anything.
Running the tool TLPD, I have so many instances above the 255 limit that it would take ages to correct manually. Anyone know of a utility that can not only detect possible problems with long paths/filenames, but correct it too?
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.
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!!!
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.
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.
