Short answer
NTFS is the file system used by many Windows drives. On a supported drive, Disk Analyzer can read the master file table (MFT) for a fast inventory. If it cannot use the MFT, it scans accessible folders instead.
After a switch to folder scanning, treat the result as partial. Check the item-level messages or run a second scan before relying on the totals.
When to use this method
The app chooses the scan path for the volume it can access. The useful comparison is not speed alone. Compare the scope each method actually read and every item-level access, protection or skipped cue.
Before you start
Keep the target drive connected and let the scan finish. NTFS is a common Windows file system. Its MFT is the built-in file index. A fallback scan walks accessible folders instead. An inventory can be incomplete when protected, damaged, disconnected or otherwise inaccessible content cannot be read.
How we checked this guide See what we reviewed, what we confirmed, and where the feature stops.
- What we reviewed
- Reviewed Disk Analyzer MFT selection, compatible fallback, progress, item-level access or skipped cues and the drive-level fallback warning path.
- What we confirmed
- Supported NTFS volumes can use the built-in file index; other targets and NTFS volumes without native access use compatible folder traversal.
- Important limit
- Damaged records, locked paths, reparse points that redirect to another location, protected locations or a disconnected drive can leave a useful but incomplete inventory.
Read the scan result in context
Choose the target
Scan one drive when the problem is known or use Scan All when it is not.
Let the app select the method
The compatible path depends on the file system and available access.
Read the completion state
Check the reported method and any item-level access, protection or skipped cues. Do not assume that a finished state proves every requested location was inventoried.
Retry only when it can help
Reconnect a drive or resolve a known access issue, then compare the new result instead of assuming the first total was complete.
MFT scan compared with a folder scan
Coverage and completion matter alongside speed.
Scroll the table horizontally on a narrow screen.
| Question | MFT scan | Compatible folder scan |
|---|---|---|
| Best fit | A supported NTFS volume with native access | A non-NTFS file system, or an NTFS volume where native access is unavailable |
| How it works | Reads NTFS file-system metadata | Walks accessible folders and files |
| Typical tradeoff | Often faster for a broad inventory | Walks every accessible path, so duration rises with tree size and access checks |
| What can limit coverage | Damaged records, reparse points or restricted native access | Locked, protected, disconnected or inaccessible paths |
| Trust signal | Method plus item-level access, protection or skipped cues; verify coverage after a fallback | Method plus item-level access, protection or skipped cues; verify coverage after a fallback |
Scan interpretation mistakes
- Calling every result a complete drive inventory
- Comparing methods by speed without checking scope
- Ignoring item-level access, protection or skipped cues
- Ignoring the fallback warning and scan method shown in the completion view
Checkpoint: Scan result checks
- The reported method matches the target.
- Item-level access, protection or skipped cues have been reviewed.
- A finished state is not treated as proof of complete coverage.
- A fallback result is checked against another inventory or a focused rescan before its total is trusted.
Osenpa Disk Analyzer
Inventory local storage with a compatible scan path, responsive filters and item-level access or skipped cues, then verify coverage if the scan falls back.