TreeSize Problems & Issues
Real user-reported problems, complaints, and limitations for TreeSize. Based on analysis of 11 signals.
Overall score: 70/100
Issues by Category
TreeSize ends support for perpetual licenses: forced subscription
Tech coverage from July 2026 reports JAM Software will no longer renew security updates and support for perpetual licenses unless the customer moves to a subscription. IT departments that bought perpetual licenses criticized it as breaking the terms they bought under. Vendor docs describe a reduced-price switch within three months of support expiry.
Why does TreeSize cost a yearly fee for a disk analyzer?
Personal (20.40 EUR) and Professional (from 41 EUR) are billed per user per year. Over several years the total can exceed a one-time price, and free tools like WinDirStat cover the basics at no cost.
TreeSize Free limits: no duplicates, no snapshot comparison, not for servers
The free edition lacks duplicate file search, disk-usage comparison over time and email reports, and cannot scan network drives inside Windows domains. Use on Windows Server is not supported; the vendor points to Professional.
TreeSize Personal and Free licensing confusion: is it allowed for work?
The current pricing page marks Free as for private, non-commercial use, while a vendor knowledge-base answer says Free may be used in commercial environments. Check the license text before using it at a company.
TreeSize scan is slow on network drives and large non-NTFS volumes
Local NTFS scans use the Master File Table and are fast, but network shares and non-MFT scans walk the file system with a few threads and are much slower. Reviewers pick WizTree when raw speed matters.
TreeSize uses a lot of RAM scanning huge drives
TreeSize keeps the scanned directory structure in memory, so the largest scan is limited by your RAM. The vendor suggests turning off user, file-type and file-age statistics under Tools > Options > Scan.
TreeSize size doesn't match Windows Explorer
TreeSize can show different totals than Explorer or the drive list because it reports occupied size, not allocated space, skips locations it cannot access, and handles hard links and junctions differently. This is the most common confusion for new users.
TreeSize crashes or won't start with Windows Defender protections
JAM Software documents that some Windows Defender protection features can make TreeSize crash on start or not launch at all. The fix is an exclusion or turning the feature off.
TreeSize access denied or folders missing unless run as administrator
Without elevation, protected folders cannot be read and the scan covers less of the disk. The vendor says starting as administrator exposes larger parts of the drive.
TreeSize interface looks dated and Windows only
Reviewers call the interface old compared with newer analyzers, and all editions are Windows desktop software with no macOS or Linux version listed on the product page.
TreeSize can't see mapped network drives when run as admin
Windows keeps elevated and non-elevated sessions separate, so drives mapped in your normal session may not appear in an elevated TreeSize. Using a UNC path or running without admin rights are the usual workarounds.
Regret Patterns
Common reasons users regret choosing TreeSize.
Bought perpetual, then pushed to subscribe
Teams that bought perpetual licenses learn support renewal now requires a subscription.
Free edition lacks duplicates and comparison
Users install Free expecting the duplicate finder and find it only in Personal.
Totals do not match Explorer
Users doubt the results because Explorer shows different numbers.
Free used on a server
Admins run Free on Windows Server, which is no longer supported.
Paid for what a free tool does
Users pay yearly then realize WinDirStat or WizTree covers their need.
When TreeSize Breaks Down
Specific scenarios where TreeSize fails or underperforms.
Scanning a network share or non-NTFS drive
No MFT access, so scans are slower and Free cannot scan domain network drives.
Scanning a multi-terabyte drive on a low-RAM PC
Directory data is held in memory, limiting the size you can scan.
Running elevated with mapped drives
Mapped drives from the normal session may not appear.
Reconciling with Explorer after deduplication
Hard links make sizes appear unchanged until you compare allocated space.
Running on macOS or Linux
No version listed; you need another tool.