Home / Guides / Reading results
Short answer: Compare identical volumes, current scans and consistent measurements before investigating a residual difference.
By DiskAnalyzer editorial resource · Published 2026-10-05 · Documentation reviewed 2026-10-05
When this guide is useful
A changing download or backup job can invalidate a comparison taken several minutes apart. Record the time and scan context first, then investigate permission coverage and filesystem overhead rather than assuming corruption.
Recommended workflow
- Check the drive letter on both displays.
- Rescan after active writes settle.
- Remove unintended filters.
- Compare allocated totals with Windows used space.
Limits and precautions
Some storage is not represented as ordinary files in a path inventory.
Keep a useful record
Record the drive or folder, scan time, application version and the measurement you used. Keep observations separate from proposed changes. If a result leads to a cleanup, record the file owner, backup status and actual free-space change. This makes the result easier to review and helps explain differences in a later scan.
Quick review checklist
| Question | What to record |
|---|---|
| What did you inspect? | The exact volume or folder, not just the PC name. |
| What action is justified? | Compare allocated totals with Windows used space. |
| What could go wrong? | Some storage is not represented as ordinary files in a path inventory. |
Next steps
If the result is unclear, preserve the current report and narrow the investigation to one folder or application. Make one approved change at a time, then repeat the relevant measurement. Avoid presenting a predicted saving as a measured outcome.
Related guides
- Read WizTree Tree View Without Losing the Path
- Use WizTree File View to Investigate Large Files
- Understand WizTree Treemap Blocks
- Find the Largest Files on a Windows Drive
Download information · How we verify guidance
Sources and verification
- WizTree developer documentation
- WizTree developer FAQ
- WizTree developer download notes
- Microsoft Windows storage guidance
Prepared from public documentation and practical storage-audit reasoning. No hands-on Windows test or independent binary inspection was performed for this publication. Menu names and package requirements can change; check the developer documentation for your installed version.