Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →To stop a file, folder, or registry key from receiving permissions from its parent, open the object’s advanced security settings and choose Disable inheritance. Windows then asks whether to keep the inherited entries as explicit permissions or remove them. To let the parent control the object again, return to the same dialog and choose Enable inheritance. The choice affects future permission changes, so select it only after checking which accounts currently have access and whether child objects are included.
What inherited permissions are and why the setting matters
Windows stores access-control entries (ACEs) in an object’s access-control list (ACL). A folder can mark an entry as inheritable, allowing that entry to flow to applicable files and subfolders. A registry key can do the same for a subkey. Microsoft describes the purpose plainly: “Inheritance allows administrators to easily assign and manage permissions.” Only entries marked for inheritance pass down; an ordinary explicit entry on the parent does not automatically become a child entry.
As an Amazon Associate I earn from qualifying purchases.
Inheritance is useful when an entire folder tree should follow one access policy. It becomes a problem when one report, project folder, or registry branch needs an exception. Disabling inheritance creates that exception on the selected object. The object keeps its own ACL, while later changes made to the parent stop arriving through inheritance. If you remove the inherited entries instead, those entries disappear from the object’s ACL and you may need to add explicit rules for the people or groups that still require access.
Check the scope before you change anything
- Selected object: Changing inheritance on a file or folder normally changes that object’s security descriptor. It does not automatically rewrite every descendant.
- Descendants: Advanced security settings can also offer an operation that replaces child-object permissions with inheritable entries from the selected folder. That is a separate, broader action.
- Current access: Record which users and groups appear in the Advanced permissions list before removing entries. If you remove all inherited entries, the object may be left with only the explicit entries already present.
- Build-specific labels: The click path and option names below are corroborated by Microsoft Q&A guidance. Windows 11 builds can present slightly different wording, so read the dialog’s scope and confirmation text rather than clicking through by position.
Disable inheritance on a file or folder
Open the advanced permissions dialog
- In File Explorer, right-click the file or folder and select Properties.
- Open the Security tab.
- Select Advanced to open Advanced Security Settings.
- Check the owner, permission entries, and the Inherited from information so you know which rules came from the parent.
- Select Disable inheritance.
Choose what happens to inherited entries
| Choice | What happens now | What happens later | When it fits |
|---|---|---|---|
| Convert inherited permissions into explicit permissions | The inherited entries currently on the object remain in its ACL, but are changed to explicit entries. | Future changes to the parent no longer flow to this object through inheritance. | Use this when the object should retain today’s access while becoming independent of future parent edits. |
| Remove all inherited permissions | Entries inherited from the parent are removed from the object’s ACL. | The object no longer receives those entries from the parent while inheritance is disabled. | Use this only when you intend to build a separate explicit permission set and have checked that required access will not be lost. |
Confirm the option, apply the change, and return to the permissions list. If you converted entries, they should no longer be identified as inherited. If you removed them, verify that the remaining explicit entries cover the accounts that need access. A successful change on a folder does not, by itself, prove that every file below it now has the same ACL.
#1 Best Overall
Enable inheritance again
Restore the parent relationship in File Explorer
- Right-click the file or folder, choose Properties, open Security, and select Advanced.
- In Advanced Security Settings, choose Enable inheritance (the wording may vary slightly by Windows 11 build).
- Apply the change and review the resulting permission entries.
When inheritance is restored, entries marked as inheritable on the parent can apply again. Windows may recompute the object’s inherited entries as part of that operation. Explicit entries that you created while inheritance was disabled are not automatically the same thing as inherited entries; inspect the list after applying the change.
Registry keys use the same concept, with different permissions
A registry subkey is a securable object, so it can inherit ACEs from its parent key. The underlying idea is the same as for a folder, but registry objects expose a different set of permissions and may show different labels. Do not assume that a file permission such as “execute” or a folder-specific option appears identically for a registry key.
Disable inheritance on a registry key
- Press the Windows key, type Registry Editor, and open it. Approve the elevation prompt if Windows requests administrator approval.
- Browse to the key you need to change. Work on the key itself; a value inside the key is not a separate container for inherited permissions.
- Right-click the key, choose Permissions, and select Advanced.
- Choose Disable inheritance.
- When prompted, either convert the current inherited entries to explicit entries or remove the inherited entries. Review the resulting list before closing the dialog.
Microsoft’s detailed inheritance concepts apply to registry keys, while the exact Registry Editor click sequence is documented in Microsoft Q&A guidance rather than a current, dedicated Windows 11 Learn procedure. Treat labels as build-dependent and avoid changing a system key unless you have a recovery plan.
Re-enable inheritance on a registry key
Return to the same Permissions > Advanced dialog and choose Enable inheritance. Review the entries that return from the parent key. Registry permission changes can affect whether Windows components or applications read and write that branch, so make one change at a time and verify the application afterward.
Automate the change with PowerShell
PowerShell’s Get-Acl and Set-Acl work with file-system items and registry-provider paths. The .NET security descriptor method SetAccessRuleProtection takes two Boolean values: the first protects the ACL from inheritance, and the second controls whether inherited entries are preserved as explicit entries when protection is enabled.
Disable inheritance but preserve the current entries
$path = 'C:DataProject'
$acl = Get-Acl -Path $path
$acl.SetAccessRuleProtection($true, $true)
Set-Acl -Path $path -AclObject $aclWith protection set to $true and preservation set to $true, the object keeps the inherited entries that are present at the time of the change, but they become explicit and will not track later parent changes.
Rank #3
Disable inheritance and remove inherited entries
$path = 'C:DataProject'
$acl = Get-Acl -Path $path
$acl.SetAccessRuleProtection($true, $false)
Set-Acl -Path $path -AclObject $aclThe second form removes inherited entries from the protected ACL. Inspect the ACL and add any required explicit rules before relying on the object for shared access.
Free tools Windows power users keep installed
One-click scans. No signup required.
Enable inheritance again
$path = 'C:DataProject'
$acl = Get-Acl -Path $path
$acl.SetAccessRuleProtection($false, $true)
Set-Acl -Path $path -AclObject $aclWhen the first argument is $false, inheritance is allowed again; the parent’s inheritable entries can be applied. The second argument has no practical effect when protection is being turned off, but leaving it explicit makes the intent clear.
Use the registry provider carefully
$path = 'HKLM:SoftwareExample'
$acl = Get-Acl -Path $path
$acl.SetAccessRuleProtection($true, $true)
Set-Acl -Path $path -AclObject $aclUse a registry path that your account can administer, and confirm that the provider returns a registry security descriptor before writing it back. For multiple items, Microsoft recommends considering -WhatIf on the Set-Acl operation to review the intended effect before applying changes. A dry run does not replace checking the scope of child objects or verifying the resulting ACL.
Do not confuse object protection with replacing child permissions
Two controls in Advanced Security Settings are easy to mix up:
- Disable inheritance on this object changes whether the selected file, folder, or key receives entries from its parent.
- Replace child-object permission entries with inheritable entries from this object propagates a replacement set to descendants. The exact label can vary, but the dialog will describe child objects and replacement.
If you only need one folder to stop following its parent, use the first control and leave the child-replacement option alone. If you intentionally need to standardize a whole tree, read the confirmation scope carefully: files and subfolders can lose custom entries that were not present on the selected folder.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesTroubleshoot unexpected results
The object still shows an old parent in “Inherited from”
Moving an item within the same volume can leave its ACL unchanged, including entries that appear to be inherited from the former parent. Microsoft documents that a later permission change can force propagation. If the object should follow its new parent, disable inheritance and then enable it again, or make another deliberate ACL update so Windows refreshes the relationship.
Best Value
Access disappeared after disabling inheritance
You selected the remove option, so the parent’s inherited entries were deleted from the object. Reopen Advanced Security Settings and add the required users or groups as explicit permissions, or re-enable inheritance to allow the parent’s inheritable entries to return. Test with the account that needs access rather than relying only on an administrator account.
The dialog does not match these labels
Windows 11 releases and object types can use different wording. Look for the controls that describe inheritance protection, conversion to explicit permissions, removal of inherited entries, and child-object replacement. Registry keys also have object-specific permission sets, so a file-oriented instruction may not map one-for-one to Registry Editor.
A child file did not change when the parent folder changed
Changing the selected folder’s inheritance does not automatically replace every child ACL. Check the child’s own Advanced permissions and determine whether the parent entry is marked inheritable and whether the child is still inheriting. Use a child-replacement operation only when you intend to overwrite descendant permission entries.
Quick Recap
Which option should you choose?
| Your goal | Action | Result to verify |
|---|---|---|
| Keep today’s access but isolate one object from future parent edits | Disable inheritance and convert inherited entries to explicit permissions. | Former inherited entries remain, but are no longer marked as inherited. |
| Build a completely separate ACL | Disable inheritance and remove inherited entries. | Only intended explicit entries remain; required accounts still have access. |
| Make the object follow its parent again | Enable inheritance. | Applicable inheritable entries from the parent reappear or are recomputed. |
| Standardize permissions throughout a folder tree | Use the child-object replacement operation only after reviewing its stated scope. | Descendants have the intended inherited entries and no needed custom access was overwritten. |
A safe verification checklist
- Confirm whether you changed a file, a folder, a registry key, or descendants as well.
- Check which entries were inherited before the change and whether they were converted or removed.
- Verify access with the users or groups that need it, not just with an account that has administrative authority.
- If the item was moved within the same volume, refresh inheritance deliberately and recheck the parent relationship.
- For scripted or multi-item work, review the intended operation with
-WhatIfwhere supported, then inspect the resulting ACL.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
