Monday, 1 December 2025

Windows Explorer size reporting issues (still...) solved by switching to Treesize Free

 Monday, 1st of Dec, 2025 - 2210

Another surprise: T410 running Linux Mint; connect (2.5”) harddrive via eSATA; works & accessible straight away. At least something is functional.


I've moved the Rock old desktop setup with its ailing monitors out of LE’s side of the cellar; it was a bit of a pisstake using up some of their space.


Back to the issue of misreported folder sizes; it's reared its annoying head again. Some googling has revealed that this is a common Windows (especially 10, though that might be recency bias) problem, sometimes indeed to do with permissions.


I had a ridiculous situation where I went to copy a 299GB directory into 360GB’s worth of space, but only after completing most of the copying did the system inform me that I needed an additional 200-odd gib of space. 


It seems that copying folders solves the misreporting problem; you just have to ‘authorise’ the copying with admin permission once, and it works.


As an experiment, I copied the contents of the (allegedly) 299GB directory into a new folder on the same disk; as if by magic, the new folder’s size was 430GB. Silly Windows.


I had been using WinDirStat as a handy tool to quickly analyse & visualise directory sizes, but it misreports in exactly the same way as File Explorer (or File Mangler, as we used to call File Manager, many years ago).


The earlier googling suggested using Treesize Free instead, and it seems to be much more accurate. I'll use that in future, despite its constant advertising.


I just need to sit down for a day and get on with this silly project.