Group Policy is not only for domains. The local policy store exists on every Pro machine, writes ordinary registry values and can be audited, exported and removed.
Edit the local store in **gpedit.msc**, apply it with **gpupdate /force** and read the effect in **HKLM\SOFTWARE\Policies**. Setting a policy to **Not Configured** removes the value — deleting the key by hand does the same.
**gpresult** shows whether the local store is the only source or whether a domain overrides it. That distinction decides whether your change survives the next refresh.
gpresult /r /scope:computer
gpresult /r /scope:user**gpedit.msc** edits the same store the registry holds. Choose a policy with a visible effect, for example the update behaviour under Windows Components.
gpedit.msc
:: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage end user experienceThe edit is written immediately but applications read it after a policy refresh. Confirming the registry value proves that the policy, not a coincidence, changed the behaviour.
gpupdate /force
Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU' -ErrorAction SilentlyContinueHome has no gpedit. The policy is still a registry value under the Policies branch, so writing it directly produces the identical effect.
New-Item -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU' -Force | Out-Null
New-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU' -Name 'NoAutoUpdate' -PropertyType DWord -Value 1 -Force
gpupdate /forceA HTML report shows which policies are set and where they came from. That is the artefact you hand over when a machine behaves differently from its neighbour.
gpresult /h C:\Temp\gpresult.html /f
Select-String -Path C:\Temp\gpresult.html -Pattern 'Local Group Policy' | Select-Object -First 3
reg query "HKLM\SOFTWARE\Policies" /s > C:\Temp\policies-before.txtSet the policy back to **Not Configured**: that deletes the value and returns the machine to the default. Deleting the key by hand is equivalent but skips the audit trail in gpedit.
Remove-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU' -Name 'NoAutoUpdate' -Force
gpupdate /force
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /sA domain policy or a management tool owns it. Check gpresult for the winning GPO, and remove the value at that level instead.
Home edition, or the optional component was removed. Write the registry value directly or install the policy editor from the optional features.
The app reads the setting at start or only on a schedule. Restart the service or the app after gpupdate before drawing conclusions.
Compare the policies-before.txt dumps from both. The difference is one key, and that is faster than reading two gpedit trees side by side.
Effectively yes. The policy layer writes documented values under HKLM\SOFTWARE\Policies, which is why a registry export can back up and restore the result.
They usually do. Export the Policies branch before a major upgrade if the machine depends on them.
Set the policies back to Not Configured in gpedit or delete the values under HKLM\SOFTWARE\Policies, then run gpupdate /force. The policies-before.txt dump tells you exactly what existed.
Free · no account needed · tracks your progress