Plan a Useful WizTree CSV Inventory

Short answer: A useful inventory states its scope, measurement and privacy limits alongside the exported rows.

By DiskAnalyzer editorial resource · Published 2026-10-05 · Documentation reviewed 2026-10-05

When this guide is useful

For a support case, export only the branch needed to explain the problem. Store the report in an access-controlled location and avoid sending a whole-drive inventory when a short summary is sufficient.

Recommended workflow

Choose the drive or folder.
Record filters and user context.
Export the intended selection.
Check a few rows against the visible scan.

Limits and precautions

Filenames and paths can reveal confidential data even without file contents.

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?	Check a few rows against the visible scan.
What could go wrong?	Filenames and paths can reveal confidential data even without file contents.

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.

Sources and verification

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.