Registry Key Permissions: Take Ownership & Full Control

This guide shows you how to take ownership of a Windows registry key and assign full permission to your user account. This is needed when you get an “Access Denied” error while trying to modify a key, often because the key is owned by TrustedInstaller or the SYSTEM account. You’ll need a Windows administrator account to complete these steps.

What You’ll Need

A Windows PC (Windows 10 or 11 recommended).
An account with administrator privileges. If you’re not sure, check Settings > Accounts > Your Info — it will say “Administrator” under your name.
The exact path of the registry key you want to modify. You can copy it from the Registry Editor’s address bar.

Step-by-Step

Open Registry Editor. Press Win + R, type regedit, and press Enter. If prompted by User Account Control, click Yes.
Navigate to the key. Use the left sidebar to drill down to the key you need. For example: HKEY_LOCAL_MACHINE\SOFTWARE\MyApp. Click the key to select it.
Open Permissions. Right-click the key (or select it and go to Edit > Permissions). The Permissions dialog opens.
Open Advanced Security Settings. Click the Advanced button at the bottom right. This opens the Advanced Security Settings window for that key.
Change the owner. At the top, next to Owner, click the Change link. In the “Select User or Group” box, type your username (e.g., YourName) or Administrators, then click Check Names to validate, and click OK.
Replace owner on subkeys (optional but recommended). Back in Advanced Security Settings, check the box that says “Replace owner on subcontainers and objects”. This ensures you also own any child keys, which often have the same restriction.
Apply the owner change. Click Apply, then OK to close the Advanced Security window. You’ll return to the Permissions dialog.
Add your user to the permissions list. In the Permissions dialog, click Add to open “Select Users or Groups”. Type your username again, click Check Names, then OK.
Grant full control. In the list at the top, select your user. In the “Permissions for [user]” list at the bottom, check the Full Control box under Allow. This automatically checks all other permissions.
Apply and save. Click Apply, then OK to close the Permissions dialog. You should now be able to modify the key.
Test the change. Try to create a new value or rename an existing one. If it works, you’re done. If you still get an error, you may need to restart Registry Editor or even reboot the PC.

Common Mistakes

Not checking “Replace owner on subcontainers” — you may own the top key but still get denied on its subkeys. Always check that box unless you have a specific reason not to.
Typing the username incorrectly — use the Check Names button to verify the account exists and is spelled correctly.
Changing the wrong key — a typo in the path can lead you to a different key. Double-check the path in the Registry Editor address bar.
Granting permissions to the wrong account — if you’re an admin, you might be tempted to add “Administrators” instead of your user. That works, but if your user is not an admin (e.g., a standard user with admin rights given via UAC), it may not be enough. Add your specific username to be safe.
Forgetting to close and reopen Registry Editor — the permissions are read when you open the editor, so a stale view can still show errors. Close and reopen after changing permissions.

Tips

Export a backup first. Right-click the key, choose Export, and save a .reg file. If something goes wrong, you can double-click that file to restore the original values.
Use “Administrators” group instead of a single user if multiple admin accounts need access. This is cleaner and avoids repeating the process for each user.
Take ownership of the whole branch if the key is part of a larger tree you need to modify. For example, if you’re editing a software key under HKEY_LOCAL_MACHINE\SOFTWARE\Vendor, you might want to own that entire vendor folder.
Restore permissions after you’re done — if you only needed temporary access, consider reverting the owner to TrustedInstaller or SYSTEM to keep the system secure. You can do this by repeating the steps and setting the owner back.
Use the command line for automation — if you do this often, learn the takeown and icacls commands, but the GUI method is safer for beginners.

Troubleshooting

“Unable to set new owner” error — This usually happens if you don’t have the “Take Ownership” privilege or if the key is protected by a system process. Make sure you’re logged in as an administrator and try again. If it persists, boot into Safe Mode and repeat the steps.
Permission changes don’t stick — Some keys are reset by Windows services on startup. If the key is under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion, a service may reapply its own permissions. In that case, you may need to stop the service first or make your changes quickly after boot.
Still getting “Access Denied” after following all steps — Check if the key has a special ACE (Access Control Entry) that denies your user. In the Permissions dialog, click Advanced, then look at the “Deny” entries. If there’s a deny for your user, remove it (you may need to change the owner first).
Registry Editor crashes or freezes — This can happen if you’re working on a large branch. Close other programs, and try again. If it keeps crashing, use regedit /s from a command prompt to apply a .reg file instead of manual editing.
Changes don’t take effect — After modifying permissions, you may need to restart the associated application or service. For example, if you changed a key for a running service, restart that service or reboot the PC.

Frequently Asked Questions

Why do I get “Access Denied” even as administrator?

Administrator accounts don’t automatically have full control over every registry key. Many system keys are owned by TrustedInstaller or SYSTEM, and the admin group has only read access. Taking ownership and adding yourself to the ACL is the standard way to gain write access.

Is it safe to take ownership of any registry key?

No. Only modify keys you understand. Taking ownership of critical system keys (like HKEY_LOCAL_MACHINE\SYSTEM) can destabilize Windows. Always back up the key first and only proceed if you’re confident about the change.

Can I take ownership of a key without using the GUI?

Yes, you can use the takeown and icacls commands in an elevated Command Prompt. For example: takeown /f "HKEY_LOCAL_MACHINE\SOFTWARE\MyApp" /r /d y then icacls "HKEY_LOCAL_MACHINE\SOFTWARE\MyApp" /grant "YourName":F /t. But the GUI method is more intuitive for most users.

What is TrustedInstaller and why does it own keys?

TrustedInstaller is a Windows service account that manages system updates and components. It owns many protected files and registry keys to prevent accidental modification. Taking ownership from TrustedInstaller is sometimes needed to repair or customize Windows, but it should be done with caution.

Will taking ownership break Windows Update?

If you only change a specific key, Windows Update should continue to work. However, if you modify system-owned keys and don’t restore ownership, future updates may fail because the installer expects TrustedInstaller to have control. Always restore the original owner after you finish your changes.

Do I need to restart the PC after changing registry permissions?

Not always. Usually, closing and reopening Registry Editor is enough. But if the key is read by a service or driver at startup, a reboot may be required for the new permissions to take effect.

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 →