Your First WizTree Scan on Windows

Start with a single drive and identify its largest folders before considering cleanup.

Home / Guides / Getting started

Short answer: Start with a single drive and identify its largest folders before considering cleanup.

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

When this guide is useful

For a laptop with a nearly full C: drive, inspect Users before browsing operating system folders. Downloads, recorded videos and old project exports are often easier to evaluate than application internals.

Recommended workflow

  1. Select the Windows drive.
  2. Start a scan and wait for it to complete.
  3. Expand the largest folder one level at a time.
  4. Record three paths you recognize and their sizes.

Limits and precautions

A large folder is a lead for investigation, not permission to delete it.

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

QuestionWhat to record
What did you inspect?The exact volume or folder, not just the PC name.
What action is justified?Record three paths you recognize and their sizes.
What could go wrong?A large folder is a lead for investigation, not permission to delete it.

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

Download information · How we verify guidance

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.