One of the things that differs Windows 10 Home from Pro and Enterprise editions is the abcense of the Group Policy Editor console (gpedit.msc). So you have to do the majority of fine tuning in Windows Home editions using the Registry Editor, and not the gpedit.msc, which is not so obviously and more risky since it is possible to make a mistake and break the system.
The Group Policy Editor has not been included into home editions (Home and Starter) of the OS since Windows XP, and Windows 10 is no exception.
In this article we’ll show how to install the Group Policy Editor in Windows 10 Home. (This method also works in Windows 7 and Windows 8 / 8.1.)
We’ll need a third-party patch by the enthusiasts, which includes all libraries and files necessary for the Group Policy Editor.
- You can download the installation archive here: gpedit_msc.zip
- Unpack the archive and run setup.exe under the administrator privileges
- If you have a 64-bit Windows 10 version, without closing the setup window (without clicking Finish) go to %WinDir%\Temp and copy the files gpedit.dll, fde.dll, gptext.dll, appmgr.dll, fdeploy.dll and gpedit.msc into %WinDir%\System32 folder
- Then copy the folders GroupPolicy, GroupPolicyUsers, GPBAK and the file gpedit.msc from %WinDir%\SysWOW64 to %WinDir%\System32
- Restart you computer and try to start the Editor console running the command gpedit.msc
If the error “MMC could not create the snap-in” appears, run the file x86.bat or x64.bat (depending on the bitness of the system) from %WinDir%\Temp\gpedit manually
8 comments
Page doesn’t exsist
I’ve fixed error in the link . You can download archive now.
It worked GREAT !! Thanks a lot.
Should I do step for a 64-bit Windows 10 version if i have Win 7 x64?
Yes, this console will work in both OS
i can’t copy, it’s said need administrator permission, what should i do?
try to copy files from cmd running with admin privileges
Before the process would work, I had to go into the Windows folder and manually reset the security on 3 or 4 of the files listed above BEFORE I could replace them. Screw Microsoft for making this difficult AND taking steps to prevent it.