When I tried to edit the registry as instructed on an instruction site to customize Windows or fix a bug, I got messages like "Cannot write error" and "Access denied" and couldn't proceed...
Have you ever experienced this? This is a very troublesome problem that can occur even when you are operating with administrator privileges. To ensure system stability, Windows tightly protects particularly important registry keys with a special account called "TrustedInstaller."
This article details the exact steps to safely bypass that ironclad defense and grant your own account registry permissions (ownership) to enable the edits you want.
Benefits of changing registry permissions
The biggest advantage of changing registry permissions is that they are usually protected and cannot be changed.Customize deeper Windows settingsThe idea is to become like this.
This allows for advanced adjustments such as:
- Speeding up Explorer: Disables the standard compressed (zip) folder function to make the program run more smoothly.
- System Repair: Fixes corrupted Windows Security related keys and restores them to normal.
As you can see, changing permissions can be a powerful tool for improving your PC's performance and troubleshooting.
[Most important] Disadvantages and important points to note
However, this powerful weapon is alsoVery big riskThis involves:
Keys protected by permissions are alwaysSomething that is vital and essential to the operation of the systemIf you accidentally edit or delete these keys, in the worst case scenario,Windows won't startIt may lead to irreversible situations.
Therefore, before changing the access permissions, please prepare the following:you have toPlease go.
- Backing up the registry: Right-click the key you want to edit and be sure to back it up by selecting "Export."
- システムの復元ポイント作成: Make sure you can restore your entire PC to a safe state before any work was done.
- Acquiring basic knowledgeIf you haven't already, be sure to read the article "Win10 Registry Basics" to understand the basic structure and risks of the registry.
If you operate the registry incorrectly, it may cause problems such as the system being unable to start. Please make a backup in advance using system restore or similar, and proceed at your own risk.
- How to create and restore a system restore point
- How to open and back up the Registry Editor
- Windows 11/10 Registry Basics: Concept, How to Open, and Internal Structure
- How to Take Ownership and Change Permissions in Windows 11 Registry
Pochip
How to change registry permissions
*You must be signed in to Windows 11 with a user account with administrator privileges.
Open Registry Editor, right-click on the key you want to change permissions for, and click Permissions.
For example, if you want to change the permissions of the subkey "Sample1" under the "HKEY_CURRENT_USER\SampleKey" key, right-click on the "Sample1" key and click "Permissions".
The permissions for Sample1 will open, so select "Administrators (*****\Administrators)" under "Group or user names."
If there is no check mark next to "Allow" for "Full Control" under "Permissions," check it and click OK.
"Read" permission: You can only read the values, but you cannot edit them or add or delete keys or values. To put it simply, it's like "reading a rare book" at a library reading desk. You can see the contents of the book (value), but you are not allowed to write (edit), tear pages (delete), or insert new pages (add).
"Full Control" permission: You can read and edit values, and add and delete keys and values. To put it simply, it's like you're the "author" of the book. In addition to reading the contents, you can also rewrite (edit) the text, add new chapters (add keys and values), delete unnecessary pages,All privilegeswill be given to you.
If there are no errors, you can continue to edit the "Sample1" key, but a "Windows Security" warning screen may appear and access may be denied.
In that case, click "Cancel."
Access is denied because ownership belongs to a user with higher privileges than you, or to another user.
Click "Advanced" under "Permissions for Sample1" to change ownership to Administrators (all user accounts with administrator privileges).
*You do not have to be an Administrator; you can use the user name you are currently signed in with.
"Advanced Security Settings for Sample1" will open, so click "Change" to the right of "Owner".
The "Select User or Group" window will open, so click "Advanced".
The "Select User or Group (Advanced)" window will open, so click "Search."
The user name will then be displayed in the search results below. Select "Administrators" and click OK.
The "Select User or Group" dialog box will appear. Confirm that "*****\Administrators" is displayed in "Enter the object names to select (examples)" and click OK.
You will be returned to "Advanced Security Settings for Sample1." Once you have confirmed that the owner has been changed, click OK.
Now that you have access, check "Allow" for "Full Control" under "Permissions" and click OK.
This completes the registry permission changes.
What does "Replace owner on subcontainers and objects" mean?
"Replace Owner on Subcontainers and Objects" is a function that changes the owner of subkeys within a key at the same time when you change the owner.
For example, if the "HKEY_CURRENT_USER\Sample1" key has a subkey "Sample1_1", when changing the owner of the "Sample1" key,Replace Owner on Subcontainers and ObjectsIf you check " and click OK, the owner of the "Sample1_1" key will also be changed at the same time.
To explain it simply:
- In a word: "All the keys inside will belong to the same owner."
- Commentary: This checkbox means that when you change the owner of a parent folder, the owner of all child folders within it will also be changed to the same person. If you do not check this box, only the owner of the parent folder will change, and the child folders within will remain with their original owner.
What does "Replace all child object permission entries with inheritable permission entries from this object" mean?
"Replace all child object permission entries with inheritable permission entries from this object" is a function that simultaneously changes the permissions of subkeys within a key when you change the permissions.
For example, if the "HKEY_CURRENT_USER\Sample1" key has a subkey "Sample1_1", when changing the access permissions of the "Sample1" key,Replace all child object permission entries with inheritable permission entries from this objectIf you check " and click OK, the permissions for the "Sample1_1" key will also be changed in the same way.
If you look at the subkey "Advanced Security Settings for Sample1_1", you will see that "Inheritance Source" is "CURRENT_USER\SampleKey\Sample1".
To explain it simply:
- In a word: "All the keys inside will follow the same rules as the parent"
- Commentary: This is a checkbox that means that when you change the rules (access permissions) of a parent folder, even if the child folders inside have their own rules, they will be overwritten and the exact same rules as the parent will be applied.
Keys with no inheritors are displayed as "None".
FAQ
- Should I revert the permissions once I'm done editing the registry values?
-
Yes. It is best to restore the permissions as much as possible. As explained above, registry keys (values) that require permissions are important keys for the system, so we recommend restoring the permissions to prevent accidental editing or deletion.
- After changing the owner from TrustedInstaller to Administrators, I can't change it back to TrustedInstaller. What should I do?
-
If you want to change the owner back to TrustedInstaller, enter the following code directly into "Enter the object names to select (example)" in "Select Users or Groups" and click OK.
NT Service\TrustedInstaller
- What should I be particularly careful about?
-
It is especially important not to edit or delete values you do not understand. It is common for people to carelessly delete registry values introduced on a certain website and then regret it. Registry values that have not been backed up cannot be restored, and you are responsible for any damage that may occur to Windows.
Pochip
Comment: