ACL Corruption on NTFS Drive – What Actually Works
This error shows up when Windows can't read file permissions on a hard drive. Most fixes online are useless, but checking the ACLs directly with icacls and repairing them works every time.
You're sitting there, trying to open a folder on your external drive or maybe your C: drive, and Windows throws up "File system ACL corruption detected" or error code 0x80071772. If you're lucky, you also see Event ID 55 in the system log. I see this most often after a sudden power loss or when someone yanks a USB drive out without clicking "Safely Remove". A client of mine last month got this after his kids pulled the plug on his desktop during a Windows update. The drive still shows up in File Explorer, but you can't access half the files. The permissions are just scrambled.
Root Cause
The security descriptor on the NTFS volume got corrupted. Every file and folder on NTFS has an ACL (Access Control List) that tells Windows who can read, write, or run it. When that list gets messed up – maybe from a bad sector or incomplete write – Windows panics and blocks everything. It's not a physical failure in most cases. It's a metadata problem. The drive itself is probably fine.
Why does it happen? Often from improper shutdowns. A power loss while the ACLs are being updated. A drive that was disconnected during a file operation. Rarely, a buggy driver or anti-virus that locks a file while Windows is writing permissions. I've also seen it from drive letter conflicts after plugging multiple external drives. The OS gets confused about which device has which permissions.
What You Need
- Windows 10 or 11 (works on older versions too)
- An admin account – you'll need to run commands as admin
- Patience. The fix involves a few command-line steps but it's not hard
The Fix – Step by Step
Step 1: Run chkdsk on the drive (for starters)
Open Command Prompt as administrator. Click Start, type cmd, right-click it, and choose Run as administrator. Then run:
chkdsk X: /f /rReplace X: with the actual drive letter. For system drive C:, you'll be asked to schedule it for next reboot. Say yes. This fixes any underlying file system errors first. I've had cases where chkdsk alone fixed the ACL corruption, but don't count on it. It's just prep work.
Step 2: Reset the ACLs with icacls
Still in the admin command prompt, run:
icacls X:\ /reset /t /c /qWhat this does: it resets every ACL on the drive to the default inherited permissions. The /t means it goes through all subfolders. /c makes it continue on errors. /q keeps the output quiet so you don't get a wall of text. This is the actual fix. I've used it on dozens of drives and it works.
If the drive is your system drive (C:), you can reset ACLs for specific folders instead of the whole drive. For example:
icacls C:\Users /reset /t /c /qStep 3: Take ownership of the drive (if icacls fails)
Sometimes icacls throws errors because Windows can't even read the current owner. In that case, you need to take ownership first. Use these commands:
takeown /f X:\ /r /d y
icacls X:\ /grant Administrators:F /t /c /qThe first command makes the Administrators group the owner of everything. The second grants full control to that group. This bypasses the broken ACLs and sets new ones from scratch.
Step 4: Run SFC (System File Checker)
If the drive is your system drive, corrupted system files can cause ACL issues too. In the same admin command prompt, run:
sfc /scannowLet it finish. It takes 10–20 minutes. If it finds corrupted files, it'll replace them from the Windows cache. This is a bonus step – not always needed, but I include it because I've seen SFC fix permission problems that icacls couldn't touch.
What to Check if It Still Fails
If the error persists after all that, you might have a deeper problem. First, check the drive with a SMART tool. I use CrystalDiskInfo (free). If the drive shows reallocated sectors or pending sectors, that's a hardware issue. The ACL corruption might be happening because the disk is physically failing. Back up whatever you can immediately.
Second, try the drive on a different computer. If it works there, the problem is your Windows install, not the drive. In that case, a Windows repair install (using the Media Creation Tool) can fix the OS without losing files. I did that for a client last week and it sorted out a weird ACL loop.
Third, if the drive is still under warranty and the data isn't critical, consider an RMA. But honestly, 90% of the time, the icacls reset does the job. Don't fall for third-party tools that promise to "fix" permissions. They just run the same commands I gave you and charge you $30.
One last thing: always properly eject external drives. And if you're running Windows 11 22H2 or later, disable Fast Startup in Power Options. That feature saves kernel state on shutdown and can corrupt ACLs on external drives. Learned that the hard way after three clients in one month.
Was this solution helpful?