Windows Update settings in registry not reflecting in the Local Group Policy

Itayi Adam 20 Reputation points
2025-03-23T21:29:52.2833333+00:00

I want to mass deploy some Windows Update Settings to non-domain joined Windows 11 Computers. I have created a Powershell script with my intended settings.

After running the script I have noticed the Registry now has the new settings but if I go to the Local Group Policy the settings are Not Configured.

For Example

Set-ItemProperty -path $RegPath -Name "ManagePreviewBuids" -Value 1 -Type Dword

If I access Registry it has value 1 . If I go to this setting in Local Group Policy

Computer Configuration\Administrative Templates\Windows Components\Windows\Windows Update For Business\Manage Preview Builds

The value is not configured.

Conversely, changing any setting from the Local Group Policy updates the registry.

Is there any way the registry settings can update the Local Group Policy?

Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2025-03-24T05:56:51.58+00:00

    Hello Itayi Adam,
    Thank you for posting in Q&A forum.

    Here is some information for your reference.

    How Group Policy Works:

    1.Administrative Template settings are implemented via the Group Policy engine and then “compiled” into the registry.pol file (located under C:\Windows\System32\GroupPolicy\Machine for the computer configuration or located under C:\Windows\System32\GroupPolicy\User for the user configuration).  

    2.When you use gpedit.msc to change a setting, it writes the policy configuration (and its enabled/disabled state) into that policy store file, not just to the registry key.  

    3.When Windows applies Group Policy, it merges the settings from the registry.pol file into the registry. That’s why a policy change from gpedit results in a registry change. However, the reverse is not true. Changing the registry value manually (or via a PowerShell script) does not update the registry.pol file. Even though the registry shows the updated value, the Group Policy Editor still sees the setting as “Not Configured” because its source (registry.pol) hasn’t been updated.

    For non-domain joined computers, if your goal is simply to have the desired behavior (e.g., enabling Manage Preview Builds), simply updating the registry might be enough for Windows to use the new values. However, if you want the Local Group Policy Editor to reflect that the policy setting is “Configured” (which might be important for documentation or auditing purposes), you’ll need to actually update the local Group Policy store rather than just the corresponding registry values.

    Unfortunately, there’s no supported way to simply “notify” Group Policy that you’ve manually changed the registry so that it retroactively marks the setting as configured. The policy “configured” status is determined by the source data in the policy store files.

    I hope the information above is helpful.

    If you have any questions or concerns, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Darrell Gorter 2,731 Reputation points
    2025-03-23T21:55:37.33+00:00

    Hello,

    That would be expected. The Group policy editor doesn't read the registry. When you apply Policy it simply makes the registry change based on what is in the .pol files for that policy.

    Manually changing the registry settings does not go back to create policy setting.

    Darrell

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.