Can anyone tell me why the UI of the Local Group Policy Editor doesn't always reflect the settings in the regestry?
If you take a look at the screen shot that I've provided, you'll see the settings say one thing but the UI says another. Even if you restart the system this doesn't change.
Hi, if you read the policy description, it sets the limits within whch a user can change the setting. The policy is not equivalent to what is set in Settings, rather it restricts how that setting may be changed.
In addition, not all changes made directly in the Registry are reflected back in the Windows UI.
Denis
Yes I'm aware of that but I'd still like to know the reason why this is.
- - - Updated - - -
The registry setting shown is the screenshot is the associated policy settings to the LGPE
What you are seeing is normal and as designed.
Group Policy was first introduced in Windows 2000 and grew out of System Policy in NT4 and Windows 98. It is most useful in a large network. It allows a network admin to control settings that can be made on a local computer. One setting in one place can control thousands of computers.
In this case Group Policy is used to control the settings for telemetry.
Not Configured means the user can either set or disable the setting.
Enabled means the setting is forced on.
Disabled means the setting is forced off.
There is no inconsistency.
I'm not talking about consistency. I'm asking why the UI (the GPE menu) isn't showing the corresponding settings. You can change settings in the GPE and the exact same corresponding settings in the registry. BUT if you do it from the registry the UI in the group editor will not show it.
In the screen shot it says Not Configured. But it's actually set to "enabled 1-basic" meaning the basic telemetry is being enforced. The UI is not showing the correct setting.
The purpose of the Group Policy is not an alternate view of the registry. It was never intended to do that and it is not what it does. Group Policy controls what settings can be made in the registry. If Group Policy shows "Not configured" that means the user can set the registry as desired. If it was set to "Enabled" or "Disabled" that will force the setting in the registry.
If Group Policy showed the registry settings that would be a bug, and a very serious one. It would not merely show that the registry was ignoring Group Policy but was actually controlling it. That would be the opposite of what was intended.
The Group Policy editor is working as intended.
I know what the configurations mean.
- - - Updated - - -
Shouldn't the GPE and the registry settings be synced. If a setting is set through the GPE it will show in the registry. If the setting is set through the registry it's still applied but the UI doesn't change. That seems weird to me.
Quote
