Share a Disk Usage Report Without Exposing Private Paths

Reduce and redact a report before sharing it outside the machine's authorized users.

Home / Guides / Reports and diagnosis

Short answer: Reduce and redact a report before sharing it outside the machine's authorized users.

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

When this guide is useful

For public troubleshooting, a folder category and rounded size may be enough. Keep the full private inventory for the administrator and share only the minimum detail needed to answer the question.

Recommended workflow

  1. Choose only relevant rows.
  2. Remove unrelated usernames and sensitive filenames.
  3. Check screenshot backgrounds.
  4. Use an approved sharing channel.

Limits and precautions

A screenshot can expose path names, account information and other open windows.

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?Use an approved sharing channel.
What could go wrong?A screenshot can expose path names, account information and other open windows.

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.