How to Reset Folder Permissions in Windows 11

To reset folder permissions in Windows 11, first check whether the folder should inherit access from its parent. You can enable inheritance through Properties > Security > Advanced. For a fuller reset that removes custom permission entries, use icacls after saving the existing permissions.

The important detail is what Windows will inherit. A reset does not recover a folder’s historical settings; it applies inherited permissions from the folder above it. If the parent has the wrong access rules, resetting its child will not produce the result you want.

This walkthrough uses one ordinary personal folder on an NTFS drive. Keep it separate from Windows system folders, installed applications and folders managed by your employer. Do not apply these commands to the entire C:\ drive or your complete user profile.

Start with the folder above the problem

Suppose the folder you cannot edit is:

D:\Projects\Reports

Here, Reports is the affected folder and D:\Projects is its parent. The paths are examples; substitute the real locations on your PC throughout the instructions.

Right-click the parent folder, select Properties > Security, and check the users and groups listed. Open Advanced for the fuller view, including which entries apply to subfolders and files.

Your normal Windows account, or a group it belongs to, should have the access you actually need. Modify normally covers reading, editing, creating and deleting files. Full control also allows permission changes, so it is not necessary just to edit documents.

I recommend stopping here when the parent itself has unexpected permissions. Fixing a child by copying access rules from the wrong parent can either leave you locked out or give other accounts access they should not have.

Also consider whether the child was deliberately more restricted. A private payroll folder inside a shared projects folder should not automatically inherit access intended for the whole team.

Save the existing permissions before either method

A permission backup records access rules. It does not copy the files themselves. For important readable documents, keep a separate copy too; see how to back up Windows 11 to an external drive.

Open Start, search for Command Prompt, right-click it and select Run as administrator. Use Command Prompt for the commands below because they use its environment-variable syntax.

Save the example folder’s permissions with:

icacls "D:\Projects\Reports" /save "%USERPROFILE%\Reports-permissions-before.acl" /t /c

Replace the folder path, and use an unused backup filename. The backup belongs outside the folder being changed. In this example it is saved in the profile of the account running Command Prompt.

Wait for the command to finish. Check the reported failures, not just whether an .acl file appeared. If any items failed, the backup may be incomplete. Resolve that before using it as your undo plan.

The saved information covers discretionary access permissions, commonly called the DACL. It is not a full backup of ownership, auditing settings or file contents. It also records today’s permissions, including any mistakes already present.

Use File Explorer when inheritance was turned off

This is the smaller change to try when the parent has suitable permissions and the affected folder has stopped inheriting them.

1. Right-click the affected folder and choose Properties.
2. Open Security > Advanced.
3. Select Enable inheritance, if that button appears.
4. Select Apply, then OK to close the dialogs.
5. Try the original action again from your normal Windows account.

If the button says Disable inheritance, inheritance is already enabled. Do not click it as a way of “turning inheritance on.”

Look at the Inherited from column after reopening Advanced Security Settings. It shows the source of inherited entries. Explicit entries, which were assigned directly to the folder, are separate.

Enabling inheritance does not remove all custom entries. A directly assigned permission can remain, so this method is not identical to a complete reset. A folder may also contain children with their own protected permissions.

There is no universal set of permissions that suits every folder, and no general Security-tab “Restore defaults” button that recovers every folder’s original configuration.

Use ICACLS when custom permissions need to be removed

Choose this route only when the parent permissions are appropriate and the affected folder should use inherited access instead of its existing custom rules.

For the folder itself, run:

icacls "D:\Projects\Reports" /reset

To reset the folder and its files and subfolders, use:

icacls "D:\Projects\Reports" /reset /t /c

Choose the scope you need. The recursive version can remove intentionally different permissions throughout that folder tree.

Keep the quotation marks, especially when the path contains spaces. Use the exact folder path rather than a drive root or an unqualified wildcard.

When processing finishes, read the failure count and any paths with errors. A completed command can still leave some items unchanged. Do not treat /c as a way to make errors disappear.

Reopen Properties > Security > Advanced to inspect the result. Then test access from the account that normally uses the folder, rather than relying only on what an elevated administrator window can open.

Undo the change using the saved permissions

For the example backup, restore with:

icacls "D:\Projects" /restore "%USERPROFILE%\Reports-permissions-before.acl" /c

Notice the difference: the restore target is the parent, D:\Projects, while the saved entries refer to Reports and its contents. Do not automatically repeat the full child path used in the save command.

Use the corresponding parent for your own folder and the same backup file saved earlier. Keep the folder structure unchanged until the reset and any restoration are finished. Renamed, moved or newly created items may not match the saved entries.

Review restoration errors and test access again. Restoring the ACL does not recover deleted files or undo a separate ownership change. If permissions were already wrong when saved, restoring that backup returns those saved rules rather than discovering an earlier correct version.

When Windows refuses to change the permissions

“Access is denied” can mean your account lacks permission to edit the access rules. Confirm that Command Prompt was opened with administrator approval and that the path identifies your intended folder.

Ownership is related, but it is a separate setting. Taking ownership can allow an authorised person to edit permissions; it does not automatically mean the resulting access rules are correct.

For personal data transferred from an old Windows installation, an ownership change may be part of recovery. Record the existing owner and confirm which account should control the folder before changing it. The ACL backup above will not undo that ownership change.

Do not make recursive takeown commands a routine prerequisite for every reset. If the permission backup fails or the folder contains access rules you cannot identify, get the folder owner or administrator to help preserve and repair them. Taking over everything first can make the original problem harder to reconstruct.

The folder opens locally but not over the network

A network share has another access layer. Its share permissions and the underlying file permissions must both allow the requested action. A local reset alone does not fix incorrect share permissions or signing in with the wrong network account.

Use setting up shared folders between Windows 11 computers for that configuration. For connections involving Linux or macOS, the Windows 11 SMB sharing guide explains the sharing side.

There is no Security tab on an external drive

Check the drive’s Properties > General > File system. FAT32 and exFAT do not provide the same NTFS-style access-control lists used in this walkthrough.

Formatting is not a permission-reset step and erases the drive’s contents. First identify whether the problem involves the file system, write protection or the software trying to use the files.

Permissions look correct but a file still will not open

Encrypted files can remain inaccessible even when their access rules allow your account. For files protected with EFS, you need an authorised decryption key or recovery method; changing ownership or granting Full control does not supply that key.

A file open in another program, an application’s own restriction or a cloud-sharing setting can also produce an access problem. Do not keep widening local permissions simply because the message contains the word “permission.”

Check the action that originally failed

Open an existing file from the affected account. If editing is intended, create a disposable text file in the folder, save a short change, close it and reopen it. Delete that test file only if deletion is part of the access you intended to restore.

For a shared folder, repeat the check from the other computer using the intended network account. Confirm that accounts meant to have read-only access have not gained editing rights.

Keep the ACL backup until those checks pass. The useful result is the right accounts having the right access, rather than every account receiving Full control.