In Windows 11 when I try to make a change in the Registry Editor, the changes will not save

Question

I am trying to make a change in " HKEY_LOCAL_MACHINE > Software > Microsoft > Windows > Current Version> Policies > System> EnableLUA " and everytime I change it to 0 it makes me restart the machine but when I open it back up, the value is still at 1 and now zero.

I don't know if it has something to do with our group policy or something but it keeps on happening to everything in the Registy when I try to make an edit.

Answer 1

Hello Jacky,

When you manually modify EnableLUA to 0, you are changing the local state, but the domain controller holds the "source of truth." Upon reboot, the machine pulls the GPO, sees that the policy is defined as Enabled (value 1), and forcibly overwrites your local edit. This confirms your suspicion that Group Policy is the culprit.

To confirm exactly which policy is reverting your change, you should trace the "Winning GPO." Open an elevated Command Prompt or PowerShell as an administrator and run the command gpresult /h C:\temp\gpreport.html. Open that HTML file in a browser and scroll down to the "Settings" section. You are looking for the path Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. Under this section, locate the policy named User Account Control: Run all administrators in Admin Approval Mode. This specific policy maps directly to the EnableLUA registry key. If this is set to "Enabled" in the report, it will list the name of the GPO responsible for that setting (e.g., "Default Domain Policy" or a specific "Security Baseline GPO").

As long as that GPO is linked to the Organizational Unit (OU) containing your computer object, any local registry change you make to that key will be futile. The EnableLUA key is critical for security baselines, and disabling it breaks modern Windows Store apps and reduces system security, so it is almost always enforced in enterprise environments. To make the change persistent, you cannot use the Registry Editor locally, you must either move the computer to an OU where this policy is not applied or requesting a modification to the upstream Group Policy Object itself. If you are the administrator, you should modify the GPO directly; if you are not, you are fighting a losing battle against domain enforcement.

I hope you've found something useful here. Should you have more questions, feel free to leave a message. If my answer helps you get more insight into the issue, it's appreciated to accept the answer. Have a nice day!

VP

Answer 2

If your changes in the Registry Editor are not being saved, it could be due to several reasons, particularly related to Group Policy settings or permissions. Here are some potential solutions:

1. Group Policy Restrictions: If your computer is part of a domain or managed by an organization, Group Policy may be enforcing settings that prevent changes to the registry. You can check the Group Policy settings using the Local Group Policy Editor (gpedit.msc) to see if there are any policies that restrict registry editing.
2. Permissions: Ensure that you have the necessary permissions to modify the registry. You may need to run the Registry Editor as an administrator. Right-click on the Registry Editor icon and select "Run as administrator".
3. Security Software: Some security software may prevent changes to the registry. Check if any such software is installed and consider temporarily disabling it to see if it resolves the issue.
4. Registry Editor Policies: There are specific policies that can disable access to the Registry Editor. If the policy "DisableRegedit" is enabled, it will prevent you from making changes. You can check this policy in the Group Policy settings or through the registry itself.
5. Rebooting: After making changes, ensure that you reboot your machine to apply the changes. However, if the changes revert back after a reboot, it indicates that some policy or software is overriding your settings.

If none of these solutions work, you may need to consult with your IT department if you are in a managed environment, as they may have specific configurations in place that are preventing these changes.