Home / Guides / Reports and diagnosis
Short answer: Control scan scope and measurement before attributing a difference to storage growth.
By DiskAnalyzer editorial resource · Published 2026-10-05 · Documentation reviewed 2026-10-05
When this guide is useful
Report the largest increases and decreases with their time interval. Exclude deliberate scope changes from the growth conclusion so a new filter does not look like reclaimed storage.
Recommended workflow
- Record the baseline date and root.
- Repeat the same scope later.
- Compare matching paths using the same size measure.
- Investigate renamed or moved folders separately.
Limits and precautions
A path that disappeared may have moved rather than been deleted.
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? | Investigate renamed or moved folders separately. |
| What could go wrong? | A path that disappeared may have moved rather than been deleted. |
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
- Plan a Useful WizTree CSV Inventory
- Create a Repeatable Storage Audit Record
- Share a Disk Usage Report Without Exposing Private Paths
- Your First WizTree Scan on Windows
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.