Fix 0x0000030C: Self-healing disabled on disk

Quick answer (advanced users)

Open Command Prompt as Administrator and run: fsutil repair set [drive letter:] 1. Replace [drive letter:] with the affected drive, like C:. No reboot required.

Why does this happen?

ERROR_DISK_REPAIR_DISABLED (0x0000030C) shows up when you try to run a disk repair—like chkdsk /f or repair-volume in PowerShell—but the NTFS self-healing feature is turned off. This usually happens after a previous repair job was interrupted (system crash, power loss, or you canceled it mid-scan). Some third-party disk tools also disable self-healing as part of their own maintenance routine and forget to re-enable it.

The error message is clear: “The attempted operation required self-healing to be enabled.” Without self-healing, Windows won’t let you fix file system corruption because it can’t guarantee the repair will complete safely. This isn’t a hardware failure—it’s a flag that got stuck.

Fix steps

Open Command Prompt as Administrator. Click Start, type cmd, right-click Command Prompt, and pick “Run as administrator.” If you’re on Windows 11, you can also right-click the Start button and select “Windows Terminal (Admin).”
Check the current self-healing status. Type:
```
fsutil repair query C:
```
(replace C: with your drive letter). You’ll see one of two outputs:
- Self-healing is enabled. — Problem is something else, try chkdsk /f as normal.
- Self-healing is disabled. — This confirms our fix.
Re-enable self-healing. Run:
```
fsutil repair set C: 1
```
Again, swap C: for your drive. No confirmation message appears—that’s normal. After you press Enter, the change is applied instantly.
Verify the change. Run the query command again:
```
fsutil repair query C:
```
It should now say Self-healing is enabled.
Run your repair now. Try the original command that failed. For example:
```
chkdsk C: /f /r
```
If it’s the system drive, you’ll be asked to schedule a scan on next reboot—type Y and restart. The scan will run before Windows loads.

Alternative fixes if the main one fails

If fsutil says “Access denied” or you can’t enable self-healing: Your account might lack full admin rights, or the drive has a hardware issue. Try these in order:

Boot into Safe Mode with Command Prompt. Restart your PC, hold Shift while clicking Restart, go to Troubleshoot > Advanced options > Startup Settings > Restart, then hit 6 or F6 for Safe Mode with Command Prompt. Run the same fsutil commands from there.
Check for pending repairs. Sometimes a stuck repair job blocks self-healing. Run chkdsk /f C: (it might fail with a different code, but it can clear the lock). Then retry the fsutil command.
Use a Windows recovery environment. Boot from a Windows installation USB, select “Repair your computer,” then Troubleshoot > Command Prompt. Run the fsutil commands from that environment.
If the drive is a RAID or NVMe SSD and self-healing still won’t flip on, check your storage controller drivers. Update them from the manufacturer’s site (Intel, AMD, Marvell, etc.). Old drivers can block NTFS features.

Prevention tip

The easiest way to avoid this error: don’t interrupt disk repairs. If you start chkdsk /f, let it finish—even if it takes hours on a large drive. For SSDs, chkdsk /f usually finishes in under 10 minutes, so there’s really no reason to cancel it. Also, avoid using third-party disk tools that disable self-healing. If you must use one, check afterward with fsutil repair query and re-enable if needed.

One more thing: if you see this error on an external USB drive, connect it directly to a SATA port if possible. USB controllers sometimes mess with disk flags. After re-enabling self-healing, run a clean chkdsk on the native SATA connection, then you can go back to USB.