Windows 10: GPEdit Error

After the latest Windows update, Group Policy Editor displays an error when starting. After clicking OK twice, the error clears. This is the second error that has occurred with GPEdit with Windows 10. A similar error occurred after the November update. Is there an easy way to fix this?

JohnD

:)

 

This app has been blocked for your protection, mmc.exe

Solved Namespace error by renaming the applicable files.

gpedit error gone, but mmc.exe blocked error still exists :-(

 

gpedit

Ok got it.

 

See the link below for a workaround

"Resource $(string.RequirePrivateStoreOnly)" Error When Opening Group Policy Editor After installing KB3147458 - The Winhelponline Blog

 

Thanks. You really have to wonder what kind of testing MS is doing before they release these updates.

JohnD

 

You're welcome and seems we are the test for their updates

 

That "fix" was problematic for me. Although it fixed the Group Policy error message, when I ran SFC /SCANNOW it found corruption that it couldn't repair. So I ran DISM /online /cleanup-image /restorehealth and it restored the component store corruption. Then, SFC /SCANNOW was able to fix the corrupted file. After looking in the CBS log, the file that it "repaired" was the WindowsStore.admx that I modified using that link. So, I think for now, I'd prefer to live with the gpedit.msc error message.

 

Or simply uninstall the update and hide it, pending resolution..
https://support.microsoft.com/en-us/kb/3073930

(But don't hold your breath...)

 

Just copy back the old WindowsStore.admx. It will be necessary change permissions of the file. First set the new owner (right click the file -> properties -> security -> advanced -> change owner). Then edit the permissions for the administrator (full control). Delete the file and copy the old one. Remember to set Trustedinstaller as the owner of this old file (to do this add "nt service\Trustedinstaller" and set it's permissions to full control).

The file is in the folder c:\Windows\Policy Definitions.

 

It seems to have been fixed in today's update for me, I don't get the error anymore.

 

I agree. Now fixed.

JohnD