To install the Local Group Policy Editor in Windows 10 Home edition, open a command prompt as administrator and run two one-line commands in sequence:
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
Also these commands can be used to install gpedit.msc console in Windows 11 Home.
For convenience, you can save this code to a text file gpedit-install.bat and run it as administrator. Wait a while until DISM installs the packages from the Windows 10 component store.
In my case, the ClientTools and ClientExtensions packages were installed in Windows 10 Home:
Microsoft-Windows-GroupPolicy-ClientTools-Package~…~amd64~~….mum
Microsoft-Windows-GroupPolicy-ClientTools-Package~…~amd64~en-US~….mum
Microsoft-Windows-GroupPolicy-ClientExtensions-Package~…~amd64~~….mum
Microsoft-Windows-GroupPolicy-ClientExtensions-Package~…~amd64~en-US~….mum
Now try to run the gpedit.msc console.
The Local Group Policy Editor interface should open (no reboot required).
The GPO editor is fully functional even in the Home edition of Windows 10 or Windows 11, and contains all the necessary policy sections that are available in the Pro/Enterprise editions.
- Some GPO settings may not work in Windows 10 Home, because these features are not available in this Windows edition;
- Please note that after changing local policies in the editor, Windows 10 Home users need to restart their computer or perform logoff/logon in order to apply new settings. In Pro and Enterprise editions, most of the changes take effect immediately, or after running the gpupdate /force command;
- Multiple Local Group Policies (MLGPOs) are not supported on Windows Home.