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-08-21T12:24:25+00:00

    its fixed in 1903 update

    Dear Allan_AU,

    Please forgive my scepticism but, I earlier couldn't found any reference to this problem in MS documentation, although I'm one of the several victims of this undocumented issue which has a long history. And I still can't find any reference in MS related documentation that this issue has been fixed in 1903 update of Windows 10.

    Can you please refer to any MS related documentation, etc. showing they accepted this as an issue and fixed it in 1903. Life with Windows 10 becomes unbearable and I'm looking for options like rolling back to pre-1803 W10 or moving my data from NTFS to other OSes and filesystems.

    Your response is very important to finalize my decision.

    Best regards,

    Cagatay

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-09-20T23:53:28+00:00

    Long Path support is built into 1903 and added to RS5 devices by KB 4516077

    See text in Enable Long Paths in Windows 10, Version 1607, and Later on DOCS that reads....

     Starting in Windows 10, version 1607, MAX_PATH limitations have been removed from common

    Win32 file and directory functions. However, you must opt-in to the new behavior.

    To enable the new long path behavior, both of the following conditions must be met:

    1. The registry key

    HKLM\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled (Type: REG_DWORD) must exist and be set to 1.

    The key's value will be cached by the system (per process) after the first call to an affected Win32 file or directory function (see below for the list of functions). The registry key will not be reloaded during the lifetime of the process. In order for all apps on the system to recognize the value of the key, a reboot might be required because some processes may have started before the key was set.

    Note

    This registry key can also be controlled via

    Group Policy at Computer Configuration > Administrative Templates > System > Filesystem > Enable NTFS long paths.

    The application manifest must also include the longPathAware element.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more