Windows 10: Can't see folder size in Explorer

So the consensus seems to be that although all previous versions of Windows was able to calculate the total size of files in a folder, Windows 10 can't? This is silly. What computers do more easily than anything else is add up numbers. Yeah, if you have a million files it might take a while. And you'd probably not be surprised if it took a long time. But most of the time, a tree of folder does NOT contain a million files. For me this is just one more of the many failings and annoyances of Windows 10. It seems to be more entertainment than work.

 

Not as a column in file explorer.




Here you can see XYplorer, which supports that- you can also see computation has not completed.




If Windows routinely did this, file explorer would be very slow to open.
You can argue that it should at least have the option...

 

Welcome to the forum.

The folder properties will show the disk space consumed. This is the same as in previous versions of Windows. But be aware that this value is only an approximation. This is far more complex than merely adding up a series of numbers. This situation is not unique to Windows. And it really can't be any other way.

Windows Explorer does not show folder sizes in a column as it does for file sizes. This is the same as in previous versions of Windows. I have explained the reasons for this elsewhere in this thread and I will not repeat it here.

 

Mouse hover tips?

 

And yet Apple has been doing it since at least os 7, which was released in 1991. If Apple can do it without slowing the system down why can Windows not do the same?

 

Just as a point of interest, I noted that when I launched XYplorer for the first time, it seemed to do a scan calculating folder sizes (as stated in the status bar) which didn't last long.

Thereafter, whichever partition I viewed, there was no significant delay with respect to folder size. (Under a second at most, on a 1Tb SSHD).

Perhaps there is a parallel there with the way fast indexing search tools like Everything, Ultrasearch and Locate32 use the file system.

 

Yes, using the MFT instead of churning thru the file system is much faster.

 

Arguing Speed on this is a cop-out. Each node should know what is stored in it. Implementation error. Bad one. Data is likely stored in the File System, the API must have been changed to obfuscate it. Information hiding you know.