Update WizTree Without Losing Your Audit Context

Home / Guides / Getting started

Short answer: Record the current version and scan settings before an update so changed results can be investigated fairly.

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

When this guide is useful

When comparing versions, stop large downloads and cloud synchronization where appropriate. Record whether each scan used elevated rights and the same filters, otherwise a difference in totals has several possible causes.

Recommended workflow

Note the version currently installed.
Save an existing report.
Check the developer's release notes.
After updating, repeat the same scan scope.

Limits and precautions

A new scan may differ because files changed, not because the update changed measurement.

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?	After updating, repeat the same scan scope.
What could go wrong?	A new scan may differ because files changed, not because the update changed measurement.

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.