Home / Guides / Reports and diagnosis
Short answer: Establish whether Windows can access the volume before troubleshooting the analyzer.
By DiskAnalyzer editorial resource · Published 2026-10-05 · Documentation reviewed 2026-10-05
When this guide is useful
If a disk disconnects repeatedly or reports errors, prioritize protecting its data. Repeated scans are not a repair method and can distract from checking cables, power and the drive's condition.
Recommended workflow
- Check the drive in File Explorer.
- Verify connection and drive letter.
- Check whether the volume is locked.
- Rescan after access is restored.
Limits and precautions
A missing or unreadable volume can indicate a hardware or encryption issue.
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? | Rescan after access is restored. |
| What could go wrong? | A missing or unreadable volume can indicate a hardware or encryption issue. |
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
- Handle Access Denied During a Storage Audit
- Why Free Space May Not Increase After Deleting Files
- Troubleshoot Empty WizTree Search Results
- Your First WizTree Scan on Windows
Download information · How we verify guidance
Sources and verification
- WizTree developer documentation
- WizTree developer FAQ
- WizTree developer download notes
- Microsoft Windows storage guidance
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.