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.
Windows File Explorer Not Showing Correct Folder Size If Folder Named 'Applications'
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.
102 answers
Sort by: Oldest
-
Anonymous
2018-09-18T14:09:49+00:00 -
Anonymous
2018-09-30T13:17:24+00:00 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?
-
Anonymous
2018-11-10T11:25:07+00:00 As far as I see per today (Nov. 10, 2018) the issue is still not fixed...
(And it's present for almost all folders, not only Applications one/)
It's present even in the 1809 October update. (Maybe it is the root cause for file deletion problem.)
Is seems to have something with the PATH length, but shortening the path is not an alternative in daily life.
IMHO unfortunately as I saw lately with some other problems nobody from Microsoft seems to (really) care.
-
Anonymous
2018-12-07T20:36:35+00:00 Same issue. Renaming the files won't work. MICROSOFT, fix it. All your fancy updates that slow down my PC are great and stuff, but it would be really helpful if you stopped messing up everything that worked.
-
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!