“Not accessible” describes several problems: an account may lack permission, a volume may be locked, directory information may be damaged, or reads may be failing. Preserve the exact message and check the disk state before choosing a fix. Where the source is readable but its file system is damaged, export wanted files before considering repairs.
Use the error and its scope
Does the error affect one folder, the whole volume or only one computer? Record the wording and whether other folders still open. Avoid applying a recursive permissions reset or disk repair to every inaccessible drive.
| Condition | First useful distinction |
|---|---|
| Access denied on a known NTFS folder | Check the authorized account and permissions |
| Locked BitLocker volume | Use the legitimate password or recovery key |
| Directory corrupted/unreadable or RAW | Treat this as possible file-system damage |
| Parameter incorrect | Record the exact message. If one item is affected, check whether other files open; if the whole drive is affected, inspect its Disk Management state and readability before repair |
| CRC/I/O error, stalls or disconnections | Assess the reading path and source stability |
Windows identifies multiple volume states in its Disk Management troubleshooting. Use the displayed state alongside the error; neither alone is a complete diagnosis.
For permissions or encryption
Try the original authorized account or computer if it remains available and the disk reads normally. Check whether the intended data folder is accessible there. Do not assume that taking ownership decrypts files or that a recovery scan removes access credentials.
For BitLocker, find the valid key or password. XRecovery supports scanning BitLocker data after authorized unlocking with valid credentials; that is not a password-bypass claim. If access is restored and the files are present, copy them normally to separate storage. Missing files can then be investigated as a separate recovery task.
For a damaged but readable volume
Cancel formatting prompts. Do not run repair switches on the original merely because Windows offers to check it. Use a separate Windows environment, identify the physical disk and prepare another device for output. Consider preserving an image when appropriate and safely feasible.
XRecovery supports finding remaining files when file-system structures are abnormal and exporting from readable RAW volumes. Select the affected source, scan it, and inspect the relevant folders or type-based results. Preview supported items, then export a few priority examples to the healthy destination.
Open those copies and inspect their actual content. Check whether a document is the needed revision and whether project files can find their dependencies. Once the sample is useful, export the important folders and keep a separate missing/damaged inventory. Restoring a file to another device does not make the original volume healthy.
If access fails during reading
If the disk repeatedly disconnects, stalls or returns CRC/I/O errors, stop treating the problem as permissions. A limited compatible-cable check can help identify a connection fault when no physical symptoms are present. Persistent errors require a preservation plan or professional assessment, particularly for unique data.
Do not combine several unverified fixes at once. Record the message and volume state, then note the result of each change. That makes the cause easier to trace than a long sequence of ownership changes, formatting and scans. After the important data is safe, decide separately whether the source should be repaired, replaced or retired.