Windows Reset File Permissions

If only one folder or drive fails, reset NTFS permissions on that scope first. If access broke after a reset, check ownership, inheritance, and the user profile before changing anything system-wide. A bad fix can lock you out of data or hide a larger Windows profile or disk problem. Start with the smallest affected folder, and if the affected path is a user-data folder on C:\, target that subtree rather than the drive root.

NTFS permissions come from parent-folder inheritance, allow and deny entries, ownership, and the default security descriptors Windows applies to common folders. After a reset, one of those pieces is often wrong, while the others still look normal. That is why the same access denied message can come from different causes.

What this error usually means

Use an elevated Command Prompt or Windows Terminal before any ACL repair. On Windows 10, right-click Start and open Command Prompt (Admin) or Windows PowerShell (Admin). On Windows 11, open Windows Terminal (Admin) from the Start menu or the Power User menu.

Likely causes

• Owner mismatch after a reset — the account can see the folder but does not own it.
• Broken inheritance from parent folders — the folder stopped inheriting the ACL it should have received.
• Deny entries or damaged ACLs, one explicit deny can block access even when allow entries exist.
• Profile corruption, encryption, or security software, permissions look normal, but access still fails for another reason.

File permissions decision table

Suppose Documents opens but a single 2 GB project folder returns Access denied. That points to a folder-scoped ACL problem, not a whole-drive failure. Suppose every path under your profile fails, but C:\Windows and C:\Program Files still open; that points more toward profile damage than a blanket permission reset.

How do I reset file permissions on Windows 10?

On Windows 10, repair only the affected folder tree, not the whole disk. Open an elevated Command Prompt, take ownership if needed, then use icacls to reset or reapply inheritance on that one path. Verify the owner and inherited entries afterward.

Windows 10 still uses the same NTFS permission model as newer builds. The difference is the entry point: Command Prompt or PowerShell from Start, then the folder’s Properties > Security tab if you want the GUI path. The command line is faster for nested folders.

Fix owner mismatch

If ownership changed during a reset, takeown is the first step. icacls can repair permissions after ownership is fixed, but it cannot solve a bad owner by itself.

1. Open Command Prompt as administrator.
2. Run takeown /f "D:\Folder" /r /d y for a folder tree, or replace the path with a single file if needed.
3. Run icacls "D:\Folder" /grant %username%:(OI)(CI)F /t /c.
4. Open Properties > Security > Advanced and confirm the owner is your account.
5. Open one file inside the folder to confirm access.

When icacls alone is enough

If ownership is already correct and the issue is a broken ACL or inheritance, use icacls alone. Its reset capability is built for recursive folder targeting, which makes it suitable for one library or one profile subtree when you do not need to change ownership.

1. Open an elevated Command Prompt or Windows Terminal.
2. Run icacls "D:\Folder" /reset /t /c to restore inherited defaults on that folder tree.
3. If inheritance is the real issue, re-enable it in the folder’s Security tab or run icacls "D:\Folder" /inheritance:e /t /c, then recheck the inherited entries.
4. Right-click the folder, choose Properties, then check Security > Advanced.
5. Confirm that child items now match the parent permissions.

Can I reset file permissions for a single folder only?

Yes. That is the safest scope for most post-reset permission problems. Target one folder, one library, or one profile subtree, and leave the rest of the disk untouched. Avoid any command that points at the drive root unless the whole tree is truly affected.

Use the folder’s Security tab for a visual check. In Advanced Security, look for inheritance controls and use Effective Access to test the user account against that one path. That check helps separate a bad ACL from a problem in the profile itself.

Fix a broken folder or library

The GUI path is often enough when the problem is confined to one folder. Re-enable inheritance first, then reapply defaults only to that folder tree.

1. Right-click the folder and open Properties.
2. Open the Security tab, then select Advanced.
3. Choose Enable inheritance if it is off.
4. If needed, use Replace all child object permission entries in the Advanced Security dialog.
5. Check Effective Access for your account.

A common first-timer mistake is running a broad reset on a library that only lost inheritance. If the Pictures folder is the only broken location, the safest repair is folder-scoped. A recursive reset on C:\ can touch far more than the problem item.

What should I do if permissions are broken on C:\ after a reset?

Treat the C:\ drive root as high risk. Fix only the specific folder under C:\ that is failing, and avoid the root itself unless you are dealing with a clearly scoped user-data folder. Windows system folders have protected descriptors that should not be blasted with a blanket reset.

If the problem lives under a path such as C:\Users\YourName\Documents, scope the command to that folder, not to all of C:\. Then restart or sign out if the change does not appear immediately. A restart often refreshes cached security tokens.

Use scoped commands on C:\

1. Open an elevated Command Prompt or Windows Terminal.
2. Run takeown /f "C:\Users\YourName\Documents" /r /d y only for the affected subtree.
3. Run icacls "C:\Users\YourName\Documents" /reset /t /c.
4. Do not apply that command to the C:\ root or to protected system folders.
5. Restart, then open the folder again.

Check Windows 11 entry points

Windows 11 uses the same permission model as Windows 10, but the entry points differ. Open Windows Terminal as administrator from Start, or right-click the Start button and choose Terminal (Admin). The commands stay the same.

1. Open Windows Terminal (Admin).
2. Run the same takeown and icacls commands you would use on Windows 10.
3. Use Properties > Security > Advanced to confirm the owner and inheritance state.

Still not working?

If the ACLs look correct and access still fails, stop repeating permission resets. The more likely causes are encryption, a damaged user profile, or security software that is blocking access before NTFS even gets a say. Test the same path from a different account before changing more permissions.

Use a second local administrator account if possible. If that account opens the same folder, the first profile is likely damaged. If neither account can open it, inspect BitLocker, other encryption, or security tools before trying another reset.

1. Sign in with a different account and open the same path.
2. Check manage-bde -status if the drive may be encrypted.
3. Open Windows Security and review protection history or quarantine events.
4. If the folder belongs to a damaged profile, move the data out with a healthy account and create a new profile.
5. If the issue persists across accounts, use vendor support or Windows troubleshooting before another ACL pass.

Prevention: before editing permissions, copy the affected data to another drive or backup location. If you are changing a profile folder, document the exact path first so you can repeat the fix on the same scope if needed.

Frequently asked questions

What command line resets Windows file permissions to default?

icacls "D:\Folder" /reset /t /c is the standard command for restoring inherited defaults on a folder tree. If ownership is wrong, run takeown first. Use a specific path, not the drive root, unless you are repairing a narrowly defined data folder.

How do I restore Windows file permissions after a reset?

Open the folder’s Security tab, select Advanced, and re-enable inheritance if it is disabled. For command line repair, run icacls "D:\Folder" /inheritance:e /t /c. Then check Effective Access for your account to confirm the folder now inherits the expected entries.

Will resetting permissions fix access denied errors after Windows reset?

Sometimes, but not always. If the issue is an ownership or inheritance break, takeown and icacls can fix it. If the folder is encrypted, the profile is damaged, or security software is blocking access, permissions may already be fine and another repair path is needed.

Does resetting file permissions affect my personal files?

It can, if you target the wrong folder or include system-protected paths. A folder-scoped reset changes ACLs on that path and its children, so back up first and keep the command pointed at the exact folder that is failing. Avoid broad resets on C:\ and Windows system directories.