For info if you have this on a computer that has not been removed from the domain.Export the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Group Policy hive then delete it.To refresh the computer policies only, use this command: So that’s all pretty easy, but what if you want to refresh Group Policy remotely? Well what if you are sitting on your computer and you want to run the gpupdate /force command on 5 Windows XP computers in the Accounting department?You could remote desktop into each one and run the command, but that’s a pain, especially if you need to do it for a lot of computers.From a performance standpoint, it doesn't make sense to run the extension to refresh the local computer's registry when nothing has changed.However, there are situations in which a local computer's registry might need to be refreshed, even though the server's GPO list and the local computer's GPO list match.One of the feature I like on Windows 2012 and Windows 2012 R2 is the starter GPO for allowing the Power Shell cmdlet Invoke-GPUpdate to remotely schedule so as to update GPO settings at a time of our choosing.
Delete the "HKCU\Software\Microsoft\Windows\Current Version\Policies" Key. No internet connection is required for this solution, but the link needs to be up, and it needs to have an IP address. If you are still logging into an account that was used while it was on the domain, chances are it hasnt been removed from the domain.To refresh the computer policies, use this command: Note that the /enforce will ensure that all settings in the policy are reapplied, even if nothing has changed since the last time the policy was applied.For all other operating systems including Windows XP, Vista, Windows Server 2003 & 2008, the secedit command has been replaced with the gpupdate command. The machine was in a domain where it got those group policy settings. Fortunately, there is a rather ingenious way to fix this problem. Hopefully this answer will get around to enough sysadmins to fix that. This solution is dependent upon the machine-in-question being dis-joined from the domain.Now it has left the domain but it still receives the settings from the group policy. I set a certain power option but soon it will be reset to another power option which is endorsed by the domain. Delete the "HKLM\Software\Policies\Microsoft" Key (looks like a folder). If it is physically off the domain, and you ARE using a local account to log on, and it still carries the group policy settings, not only would i be very surprised, but something is wrong. If it is NOT dis-joined from the domain via the OS, then this will NOT work.