Jump to content

Errors Starting gpedit.msc


Recommended Posts

Posted (edited)

For those of you testing Windows 10 Pro...

Do you see errors when starting gpedit.msc (the Local Group Policy Editor)?

If so, the problem appears to be that there are at least some leftover files in the C:\Windows\PolicyDefinitions and C:\Windows\PolicyDefinitions\en-US folders that shouldn't be there.  Taking ownership, granting oneself Full Control permissions, and deleting the files whose dates don't match all the others seems to clear up the error messages, BUT...  Deleting one of them that gives me trouble also breaks system protection (i.e., SFC /SCANNOW reports an error and restores the WindowsStore.admx file that emits the error):

GPEDIT_Errors.png

This looks a lot like Microsoft isn't managing what's in the PolicyDefinitions folders very well via Windows Update, but it's almost hard to believe that they'd be making mistakes that are so blatant.

It sure looks as though they've mixed up the released version of Windows 10 with pre-release builds, since the date on the offending WindowsStore.admx file is March 23, 2016, and it superseded one that had the same date as all the other files (October 30, 2015).  There is NO corresponding update to the WindowsStore.adml localization file in the en-US subfolder.

LocalizationProblem.png

Your thoughts / experiences?  

-Noel

Edited by NoelC

Posted

As mentioned, the workaround leads to a failure of System Protection.

Windows 10:  "not something one can say will still work the next day"

I like it!

-Noel

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...