Fix Access Control Entry Is Corrupt Error on Windows

This guide walks you through resolving the “Access Control Entry is corrupt” error on Windows, which typically appears when you try to open, copy, or delete a file or folder. The fix involves repairing the file’s security descriptor using built-in Windows tools. You’ll need administrator access to your PC and the exact file path of the problematic item.

What You’ll Need

An administrator account on the Windows PC (you’ll need to approve UAC prompts).
The full path to the file or folder that triggers the error (e.g., C:\Users\YourName\Documents\file.txt).
A backup of important data, as some steps modify file security settings.

Step-by-Step

Identify the exact file or folder. When the error appears, note the full path shown in the message or in the error details. If you’re unsure, try to reproduce the error and copy the path from the dialog box.
Open Command Prompt as Administrator. Click the Start button, type cmd, right-click “Command Prompt” and select “Run as administrator.” Confirm the UAC prompt.
Take ownership of the file/folder. In the Command Prompt, type the following and press Enter, replacing "C:\path\to\folder" with your actual path (keep the quotes if the path has spaces):
takeown /f "C:\path\to\folder" /r /d y
The /r applies to all subfolders and files, and /d y automatically answers “Yes” to the prompt. This step may take a while for large folders.
Grant yourself full control. Type the following and press Enter, again replacing the path:
icacls "C:\path\to\folder" /grant "%USERNAME%":(OI)(CI)F /T
The /T applies the change to all subfolders and files. This gives your user account full control over the item.
Try accessing the file again. If the error is gone, you’re done. If not, proceed to the next step.
Reset the security descriptor. In the same Command Prompt, run:
icacls "C:\path\to\folder" /reset /T /C /Q
This resets all security settings to inherited defaults. The /C continues on errors, and /Q suppresses success messages.
Check for disk errors. If the error persists, run a disk check. In the Command Prompt, type chkdsk C: /f (replace C: with the drive letter where the file is). You’ll likely be prompted to schedule it for the next restart. Restart your PC and let the check complete.
Use System File Checker (SFC). If the disk is fine, run sfc /scannow in the same admin Command Prompt. This scans and repairs protected system files. It may take 10-20 minutes.
Restart and test. After SFC finishes, restart your PC and try accessing the file again.

Common Mistakes

Running Command Prompt without admin rights. The commands will fail with “Access denied” or “Requested operation requires elevation.” Always right-click and select “Run as administrator.”
Using the wrong path. A typo in the path will cause “The system cannot find the file specified.” Copy the path from the error message or use Tab to autocomplete in Command Prompt.
Skipping the ownership step. If you don’t take ownership first, icacls may not be able to change permissions, even as admin. Always run takeown first.
Forgetting the /T flag. Without it, changes only apply to the top folder, not the contents, so subfolders may still be corrupt.
Not waiting for chkdsk to finish. Interrupting a disk check can cause additional file system corruption. Let it complete fully.

Tips

If the error occurs on an external drive or USB stick, try connecting it to a different USB port or another computer to rule out a hardware issue.
Back up your data regularly. The takeown and icacls commands modify security settings, and a mistake could lock you out of your own files.
For a single file, you can skip the /r and /T flags to speed up the process. Use them only when dealing with a folder.
If the file is on a network share, ask the network administrator to run the repair on the server side, as local commands may not have the necessary permissions.
Use the /Q (quiet) flag with icacls to reduce output if you’re working with a large folder tree.

Troubleshooting

If the steps above don’t resolve the issue, try these additional approaches:

Error still appears after resetting ACLs. The file may be locked by another process. Restart your PC in Safe Mode (hold Shift while clicking Restart, then choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4) and repeat steps 3-6 in Safe Mode.
“Access is denied” when running takeown. Ensure you’re using an administrator account, not just a standard user. If your account is admin but UAC is set to always notify, you may need to temporarily disable UAC (not recommended) or use the built-in Administrator account (enable it via net user administrator /active:yes in admin Command Prompt, then log into it).
chkdsk reports errors but can’t fix them. Run chkdsk C: /f /r to locate bad sectors and recover readable information. This takes much longer but is more thorough.
File is still corrupt after all repairs. The file itself may be physically damaged. Try copying it to another drive; if that fails, consider data recovery software, but note that the file may be unrecoverable.
Error appears on system files (e.g., in Windows folder). Do not manually change permissions on system files. Instead, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth (in that order) to repair system integrity.

Frequently Asked Questions

What causes the “Access Control Entry is corrupt” error?

It usually means the security descriptor (ACL) for a file or folder is damaged, often due to improper shutdown, disk errors, or a bug in a program that modified permissions.

Will these steps delete my files?

No. The commands only change security settings, not the file contents. However, if the file is already corrupted on disk, it may still be unreadable.

Can I fix this without Command Prompt?

You can try using the GUI by right-clicking the file, selecting Properties > Security tab, and adjusting permissions, but the error often prevents that. Command Prompt is the most reliable method.

How long does the fix take?

The takeown and icacls commands are usually quick for a single file. For a large folder or a full disk check, it can take 30 minutes or more.

Is this safe on an SSD?

Yes, running chkdsk on an SSD is safe, though it may not find the same types of errors as on a hard drive. The takeown and icacls commands are equally safe on both.

What if the error is on a system file?

Do not manually change permissions on system files. Use sfc /scannow and DISM to repair them, as described in the troubleshooting section.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →