>>108074896
>>108074901
Here's an example of your incredibly low IQ making you unable to understand how Group Policy works. This is a policy definition that has no elements - that is, simply setting the policy to Enabled changes the registry value:
<policy name="NoControlPanel" class="User" displayName="$(string.NoControlPanel)" explainText="$(string.NoControlPanel_Help)" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" valueName="NoControlPanel">
<parentCategory ref="windows:ControlPanel" />
<supportedOn ref="windows:SUPPORTED_Win2k" />
</policy>
Note the lack of an <elements> tag. Enabling this policy sets HKCR (as class=User) Software\Microsoft\Windows\CurrentVersion\Policies\Explorer (as per the key attribute) NoControlPanel (as per the valuename attribute). Policies without a datatype are assumed to be Boolean, so this will set HKCR\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer!NoControlPanel=dword:00000001.
Elements, on the other hand, work differently: the registry value(s) are attached to the individual elements, and their state - not whether the policy itself is Enabled - configures them. As such:
<policy name="AllowOnlineTips" class="Machine" displayName="$(string.AllowOnlineTips)" explainText="$(string.AllowOnlineTips_Help)" presentation="$(presentation.AllowOnlineTips)" key="Software\Microsoft\Windows\CurrentVersion\Policies\Explorer">
<parentCategory ref="windows:ControlPanel" />
<supportedOn ref="windows:SUPPORTED_Windows_10_0_RS3" />
<elements>
<boolean id="CheckBox_AllowOnlineTips" valueName="AllowOnlineTips">
<trueValue>
<decimal value="1" />
</trueValue>
<falseValue>
<decimal value="0" />
</falseValue>
</boolean>
</elements>
</policy>
Will only work if the policy is set to Enabled, and the checkbox in the picrel I gave above is unchecked.
I hope your brain damage clears up, anon.