Investigate a Slow WizTree Scan

Short answer: Check the scan context before comparing speed with another drive or another computer.

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

When this guide is useful

A local system volume and a remote archive differ in access method and workload. Benchmark them separately, and include the machine, version and scope with any timing claim.

Recommended workflow

Record filesystem and scope.
Check access rights.
Look for active disk or network work.
Repeat once under comparable conditions.

Limits and precautions

There is no universal scan-time guarantee.

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?	Repeat once under comparable conditions.
What could go wrong?	There is no universal scan-time guarantee.

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.