Windows File Explorer Not Showing Correct Folder Size If Folder Named 'Applications'

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!

@Socket462,

Thanks for the reply, I tried your solution of enabling 'long paths' with the Group Policy Editor and rebooting, but the problem remains. It's annoying because if I move or copy Directories Windows can find and report the size of the Folders and number of files contained accurately, so why can't it do the same using Right Click -> Properties. 

Thanks anyway,

Dave.

I bought a brand new NAS Synology DS918+. I tried to copy all the data from my drive E: to that NAS.

What a surprise when all was done, the Explorer said that on NAS is 222GB and on the E: is 277GB. Where is the 55Gigs? So it started. So many dirty words. So much wasted time. Here is what I found.

If you don’t want to be sick don’t read this article, throw away your PC and move to some uninhabited island.

The problem is in the Path length of Windows Explorer.

Path Length = PL

There are two different PL in an Explorer. "Directory PL" and "File PL"

The "Directory PL" can not be longer than 247 characters.

If you try to create or copy a Directory where the result Directory PL will be longer than this limit, the operation will be rejected and you will see warning "The Path is too long. Make it shorter".

If you try to rename (prolong) the last Directory name it won't let you add a next character (no warning).

If you try to rename (prolong) any Directory name within the tree, it lets you until you reach the limit on that particular name. Than it wont let you add next character. It means that in this case the PL is checked (counted) only from root to this Directory name. The Directory names behind are not counted

BUT! (read later…)

The "File PL" can not be longer than 259 characters.

If you try to create or copy a File where the result File PL will be longer than this limit, there is no problem (strange!).

If you try to rename (prolong, shorten or just change) the File name which is now and than longer than the limit, it won't let you save it and you will see warning "The File name is invalid or too long. Rename it".

If you try to rename (shorten) the File name which is now longer but the result will be shorter than the limit, it works (of course).

Why is the limit 12 characters longer? Probably because of the old DOS 8.3 convention. 8 characters name, one dot and 3 characters suffix, All together 12.

The meaning is probably that if you have the full limit Directory PL you have still space for standard DOS File name.

These are the limits of the „Explorer Editor“. The Properties have a little different limits.

Now about the Properties.

For the tests there is 9 Directories, 25 characters each and one with 10 characters, plus the E:\ (3 chars), plus the \ after every Directory. All together 247 characters (full Directory PL limit).

In the last Directory is one file 1023 Bytes long.

Here I made the tests.

If we have the full Directory PL and one file which does or doesn’t exceed the File PL limit, we will see this:

So far so good.

Let‘s add one or two… or 8 characters into the Directory tree. And… nothing happened! The result will be the same.

The limit of Directory PL for Properties is 255! (No it’s not! You’l see!) If we add 9 characters we are out of limit. But this means that the Editor limit was pushed by 9 characters and now we are unable to edit the name of the last Directory unless we short it by 9 characters. What a mess you think? Wait!

Now let‘s see what happens if we cross the limit by one character…

In the Properties window we see 3 nonsenses. 0 Files (one is there, obviously), 0 bytes (the File has 1023 bytes) and 257 Folders (WTF?).

Even when I deleted the file it looks the same.

What about the limit 255? Yes it is, but only in this exact example (one file in only one last Directory).

If I add at the end some Directories of the same name length with the same File the limit shrinks.

Let’s make 5 Directories with 5 Files and let’s see what happens.

Here it is OK. The Directory PL is 250.

Rise it to 251 and here is a mess again. It found only 2 Files from 5.

I tried with 10 Directories/10 Files and the result is the same. Seems the real Directory PL limit is 250 (for Explorers Properties).

So here are some rules for the Properties of Explorer:

All the Files which are behind the 255 Directory PL limit are not found.

Some Files which are behind the 250 Directory PL limit are not found (the exact rule is unknown).

The lenght of the File name doesn’t matter (hopefully).

It's sad that after 25 years of Windows on the market, the most fundamental function such as files and folders processing, does not work properly.

 Shame on you Microsoft.

This seems to be a recent issue that occurred for me after one of the many updates Microsoft provides. I just noticed this December 16, 201****03? I agree with the other post that this creates some potentially catastrophic situations and you should really figure it out and fix it ASAP!

Not sure what when wrong so I'll try to reply again!

This seems to be a recent issue that occurred for me after one of the many updates Microsoft provides. I just noticed this December 16, 201****03? I agree with the other post that this creates some potentially catastrophic situations and you should really figure it out and fix it ASAP!