Windows 10 Group Policy editor broken?

bochane · Mar 22, 2015

In my testenvironment it look likes the Group Policy editor (type gpedit.msc ) is broken. Here I get all kinds of messages on symbols not being defined or being double defined.....
Is it my (too) small Acer One or is it a bug in the X86 version of build 10041?

Josephur · Mar 23, 2015

You can open the AppXRuntime.adml file in a good editing program such as Notepad++ and see where the XML has an error. There is a duplicate of the AppXRuntimeBlockFileElevationExplanation keys. This is not due to corruption, and is not a major error. It just looks like during the last build a team was working on Group Policy and had unfinished work and forgot a duplicate in there. I wouldn't recommend copying the files from Win8, I would recommend backing up the adlm file and removing the duplicate key entry. If I have time later today I will make a video of just that.

bochane · Jun 7, 2015

Fixed in 10125!

Trouble · Jun 7, 2015

bochane said:
Fixed in 10125!

Fixed in that opening it no longer produces any error messages, but....
It or should I say Windows 10, disregards my settings.
I'm not sure why I or anyone for that matter needs a "Lock Screen" on a desktop computer.

THIS, is the setting that is being ignored.

Windows 10 Group Policy editor broken?

bochane

Excellent Member

Josephur

bochane

Excellent Member

Trouble

Noob Whisperer

Similar threads