One of the most frustrating Windows storage errors appears when you try to open a folder and receive the message:

Location is not available

The file or directory is corrupted and unreadable.

Many users immediately assume that the hard disk has failed or that all their data has been lost. Fortunately, this is not always true.

In most cases, Windows can still detect the drive, assign it a drive letter, and even display the folder name. The problem usually lies in the NTFS file system metadata rather than the physical storage media.

This guide explains the causes, diagnosis, recovery methods, and preventive measures in detail.

Understanding the Error

Windows stores information about every file and folder inside a special database called the Master File Table (MFT).

Each folder also contains an Index Record that tells Windows which files exist inside it.

If either of these becomes corrupted, Windows may display:

The file or directory is corrupted and unreadable.

while the drive itself remains accessible.

Typical Symptoms

• Drive appears normally in File Explorer.
• Capacity and free space display correctly.
• Disk Management shows Healthy Partition.
• Device Manager reports "This device is working properly."
• Root directory opens.
• One or more folders cannot be opened.
• Error appears only for specific folders.
• Disk is still detected correctly.

Example Scenario

Suppose:

Drive F:

shows

465 GB NTFS
104 GB Free

You can open:

F:\

and see

Project Backup

But opening

F:\Project Backup

produces

The file or directory is corrupted and unreadable.

This usually indicates directory corruption rather than complete disk failure.

Common Causes

1. Unsafe USB Removal

Disconnecting an external drive while data is still being written.

2. Power Failure

Unexpected shutdown during file copy operations.

3. NTFS Metadata Corruption

Corrupted:

• Master File Table
• Directory Index
• Bitmap
• USN Journal

4. Bad Sectors

Physical sectors containing NTFS metadata become unreadable.

5. USB Cable Problems

Loose USB connections may interrupt write operations.

6. Malware

Some malware damages file system structures.

7. Sudden System Crash

Kernel crashes during disk activity.

Before Attempting Any Repair

Never immediately run repair commands.

Avoid:

• Formatting the drive
• Copying new files onto the drive
• Defragmenting
• Partition resizing
• Installing recovery software onto the same drive

These actions may permanently overwrite recoverable data.

Step 1 – Check Disk Status

Open Disk Management

diskmgmt.msc

Verify:

• Online
• Healthy
• NTFS
• Correct capacity

If the partition appears RAW instead of NTFS, the recovery approach changes significantly.

Step 2 – Check Device Status

Open Device Manager.

Expand

Disk Drives

Verify:

This device is working properly.

If Device Manager reports hardware problems, investigate the drive before repairing NTFS.

Step 3 – Run Read-Only CHKDSK

Never start with repair mode.

Run:

chkdsk F:

This performs analysis only.

Possible findings include:

• Index errors
• MFT corruption
• Security descriptor issues
• Bad clusters
• Bitmap errors

Step 4 – List Folder Contents

dir F:\

If the root directory lists correctly, NTFS is still readable.

Now check the problematic folder.

dir "F:\Project Backup"

This helps determine whether only one directory entry is damaged.

Step 5 – Check Short File Names

Sometimes the long filename becomes corrupted.

dir /x

If an 8.3 filename exists, it may still be accessible.

Example:

PROJEC~1

Step 6 – PowerShell Verification

Get-ChildItem F:\

Then

Get-ChildItem "F:\Project Backup"

PowerShell sometimes returns more descriptive errors than File Explorer.

Step 7 – Check SMART Health

Using WMIC:

wmic diskdrive get model,status,size

Possible output:

Status
OK

If SMART reports failures, clone the drive immediately.

Step 8 – Repair NTFS

Only after confirming there are no serious hardware issues.

chkdsk F: /f

Windows repairs logical file system errors.

Step 9 – Scan for Bad Sectors

If physical damage is suspected:

chkdsk F: /r

This command:

• locates bad sectors
• attempts data recovery
• marks sectors unusable

Note:

This scan can take several hours on large drives.

Useful PowerShell Commands

Show Drive Information

Get-Volume

List Physical Disks

Get-PhysicalDisk

Check Disk Health

Get-Disk

View Storage Status

Get-StoragePool

Useful Command Prompt Commands

Check File System

chkdsk F:

Repair Errors

chkdsk F: /f

Recover Bad Sectors

chkdsk F: /r

Show Folder

dir

Show Hidden Files

dir /a

Show Short Names

dir /x

Verify Windows System Files

sfc /scannow

Repair Windows Image

DISM /Online /Cleanup-Image /RestoreHealth

When CHKDSK Is Safe

Safe when:

• Disk is healthy.
• SMART status is OK.
• No clicking sounds.
• No bad sectors reported.

When NOT to Run CHKDSK

Avoid repair if:

• Drive disconnects randomly.
• Clicking noises occur.
• SMART warnings exist.
• Disk is extremely slow.
• Large numbers of bad sectors are detected.

Instead:

Clone the drive first using professional imaging software.

Data Recovery Tools

If Windows repair cannot restore access:

• TestDisk
• PhotoRec
• R-Studio
• DMDE
• UFS Explorer

Always recover data to another drive.

Preventive Measures

• Always use "Safely Remove Hardware."
• Use quality USB cables.
• Maintain backups.
• Monitor SMART health regularly.
• Replace failing drives early.
• Use UPS on desktop systems.
• Never disconnect external drives during copying.

Sample Diagnostic Batch Script

Save as:

Disk_Diagnose.bat

@echo off
echo =====================================
echo Disk Diagnostic
echo =====================================
wmic diskdrive get model,status,size
echo.
echo Running Read Only CHKDSK...
chkdsk F:
echo.
dir F:\
echo.
pause

Sample PowerShell Diagnostic Script

Write-Host "Disk Information"
Get-PhysicalDisk

Write-Host ""
Write-Host "Volumes"
Get-Volume

Write-Host ""
Write-Host "Disk Status"
Get-Disk

Troubleshooting Table

Best Practices

✔ Keep multiple backups.

✔ Monitor SMART health monthly.

✔ Never interrupt file transfers.

✔ Replace suspicious USB cables.

✔ Perform regular Windows updates.

✔ Use quality external drive enclosures.

✔ Keep antivirus software updated.

Frequently Asked Questions (FAQs)

Q1. What does "The file or directory is corrupted and unreadable" mean?

It usually indicates corruption within the NTFS file system, such as damaged directory entries, MFT records, or index structures.

Q2. Does this mean my hard disk has failed?

Not necessarily. Many cases involve logical file system corruption rather than physical hardware failure.

Q3. Is CHKDSK safe?

Yes, when the drive is physically healthy. However, on failing disks, create a clone before attempting repairs.

Q4. Can I recover files without formatting?

Yes. Many logical corruption issues can be repaired or recovered without formatting the drive.

Q5. What is the safest first command?

chkdsk F:

This performs a read-only analysis and does not modify the disk.

Q6. Why can I see the folder but cannot open it?

The folder entry exists, but its NTFS metadata (such as the directory index or MFT record) may be corrupted, preventing Windows from accessing its contents.

Q7. What if the drive shows as RAW?

A RAW drive usually indicates severe file system corruption or a damaged partition. Avoid formatting and attempt data recovery first.

Q8. Should I use recovery software before running CHKDSK?

If the drive shows signs of physical failure (bad sectors, clicking, SMART warnings), recover or clone the data first. For purely logical corruption on a healthy drive, CHKDSK may resolve the issue.

Conclusion

The "The file or directory is corrupted and unreadable" error often appears alarming, but it does not automatically mean your data is lost. By diagnosing the drive carefully, verifying its physical health, and using the correct sequence of commands, many NTFS corruption issues can be resolved safely. Always begin with non-destructive diagnostics, avoid unnecessary writes to the affected drive, and maintain reliable backups to minimize the impact of future storage issues.