Investigate Files Behind Recent Disk Growth

Short answer: A date-focused audit gives candidates for a recent change, not proof of the application's behavior.

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

When this guide is useful

If an overnight job consumes space, compare its output directory before and after the next run. Avoid treating a timestamp alone as evidence when the program rewrites an existing database.

Recommended workflow

Record when space started shrinking.
Inspect large recently modified files.
Check which application owns their directories.
Compare with a saved earlier report if available.

Limits and precautions

Modified dates can change during copying and may not indicate initial creation.

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?	Compare with a saved earlier report if available.
What could go wrong?	Modified dates can change during copying and may not indicate initial creation.

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.