What are your Thoughts?



  1. VK
    October 18, 2017 @ 12:43 PM

    Most GPO policies in W10 are now restricted by Product Policy Licenses
    so adding the GPO or equivalent registry value to unsupported Edition will have no effect. I’m pretty sure that Policy Plus will not work because it also uses Windows registry for setting changes and restrictions. Have you tried changing settings with Policy Pro on Windows 10 Home and checked the results?


    • Stan
      February 2, 2019 @ 9:36 PM

      As a matter of fact I have confirmed that policies configured using Policy Plus are working. I ended up here after enabling GPEDIT did not have any effect. I used the enabler script from another article on this website, but none of the configured policies took effect nor did they even get their corresponding registry entries created. Using Policy Plus, however, worked as it should with the policies that were configured. Some policies required a reboot before they took effect, for example turning off Windows Defender antivirus. Disabling right-click context menu for the Start menu and removing the power options from the Start Menu as well as the Windows Security screen (ctrl+alt+del screen) also worked as expected and immediately, without a reboot. Hiding specific pages of the Settings app also worked flawlessly and only required a restart of the app. Some other policies are yet to be confirmed if they are effective and I’m doubtful they are, as you’ve said, some policies are edition-dependent and setting them up on unsupported editions is futile. I’m suspecting automatic Windows Updates are one such policies that are simply ignored in W10 Home, even though no updates were automatically downloaded during my testing, but this may have more to do with setting the connection as metered than disabling automatic updates via Group Policy (Policy Plus). Next, I’m going to allow automatic downloading of updates via metered connection to see IF the Windows Update Group Policies are actually effective or not.