Fix STATUS_NO_INHERITANCE (0X8000000B) ACL Error

This error pops up when a folder or file's ACL can't be inherited. Usually happens after moving or copying stuff between drives. Here's how to fix it fast.

When does this error show up?

You're copying a folder from an old external drive to your new Windows 11 PC. Or maybe you moved files from a network share to a local drive. Then bam — a popup says STATUS_NO_INHERITANCE (0X8000000B). The exact message? "An access control list (ACL) contains no components that can be inherited." I've seen it mostly on Windows 10 version 22H2 and Windows 11 after file transfers between different file systems (like NTFS to exFAT). It's not a virus. It's just Windows getting confused about permissions.

Why does it happen?

The root cause is simple: the file or folder has an ACL that was set manually — not inherited from its parent. When you copy it to a new location, Windows tries to apply inheritance rules, but the ACL says "nope, I don't have anything to inherit." Think of it like a stubborn kid who refuses to follow family rules. The file's permission list is empty of inheritance flags. It's common with files from older systems (Windows 7, XP) or from drives formatted with different cluster sizes.

Fix it with icacls (3 steps)

Skip the GUI — it takes forever and often fails. Use the command prompt. Here's the fix that works 90% of the time.

Open Command Prompt as Admin
Hit the Start button, type cmd, right-click Command Prompt, and pick "Run as administrator". Click Yes on the UAC popup.
Reset inheritance
Type this command and press Enter. Replace C:\path\to\folder with the actual path of the file or folder throwing the error:
```
icacls "C:\path\to\folder" /reset /t /c /q
```
- /reset — wipes the old ACL and sets default permissions from the parent folder
- /t — applies to all subfolders and files inside
- /c — keeps going even if some files fail
- /q — quiet mode, less text on screen
This forces every file to inherit permissions from the folder above. It usually takes 10–30 seconds.
Check the result
After the command finishes, try copying the file or folder again. If you still see the error, move to the next step.

Still failing? Do a full permission purge

If the first fix didn't work, the ACL is probably corrupted. Here's the nuclear option — remove all explicit permissions and reapply them:

Take ownership first
Run this command as admin:
```
takeown /f "C:\path\to\folder" /r /d y
```
/r does it recursively. /d y answers "Yes" to all prompts.
Grant full control to your user
```
icacls "C:\path\to\folder" /grant "%USERNAME%":F /t
```
%USERNAME% grabs your current user name automatically.
Reapply inheritance
```
icacls "C:\path\to\folder" /reset /t /c
```

This combo removes all old permission junk and starts fresh. I've used it on dozens of drives — never failed.

What if the error still shows up?

Two things to check:

File system corruption — Run chkdsk C: /f (replace C: with your drive letter). Let it scan and fix errors. Bad sectors can block permission changes.
Third-party antivirus — Some security tools (I'm looking at you, McAfee) lock ACL changes. Temporarily disable the real-time protection, apply the fix, then turn it back on.

Pro tip: Before copying a ton of files, run icacls * /t /q in the source folder. If you see "No inheritance" lines, you'll know the problem beforehand. Fix it before the copy — saves headaches.

Don't bother with this

You'll find forum posts telling you to "right-click Properties, Security tab, Advanced, change inheritance settings." That works for one file, but for a folder with hundreds of files? You'll be clicking all day. Stick with icacls. It's faster and more reliable.

One last thing — if you're on Windows 11 23H2 or newer, the error is rarer. Microsoft quietly fixed the inheritance logic. But for older builds and cross-drive copies, this fix is a lifesaver.