How to Install Group Policy Editor (gpedit.msc) for Windows 10 (Home Edition)

Windows 10 Home Edition lacks the amazing Group Policy Editor. Many users are annoyed by that fact, which is why they look for ways to install gpedit.msc on their computers. Here’s how to install it.

Windows 10 Home and Professional editions differ in terms of system functionality, permissions, etc. For example, the Professional version has the Group Policy Editor, as well as advanced networking management settings. These are extremely useful features which are not present in the Home Edition. In this text, we’ll instruct our readers and show them how to use these features on their Windows 10 Home Edition systems.

The Group Policy Editor is one of the most important tools for people who like to micromanage the functionality of the entire system. Since it’s absent in the Home Edition, the users are constantly looking for ways to include it somehow. Fortunately enough, that is possible by installing gpedit.msc (GPEditor). This program was an integral part of every Windows OS including Windows XP, Windows 7, and Windows 8. The Home editions for each of those systems were the only ones that didn’t include it. Later on, Microsoft decided to do the same for Windows 10, which wasn’t surprising at all.

The alternative to using GPEditor includes going through the registry entries in order to modify the permissions. It essentially does the same thing as the gpedit.msc, but it’s a lot riskier. The main reason is that the users can’t revert the settings. In addition, messing around with registry keys and entries is bound to cause some problems in the long run. Therefore, we’ll show you how you can install gpedit.msc on your computer quite easily!

How to Install GPEditor

There’s no need to update to Professional Edition and pay extra money just because you want to use the Group Policy Editor. The users on various forums have found a workaround which brings the same features of the Professional Edition to the Home one.

To install GPEditor, just follow these steps.

  1. Download the editor
  2. The package should contain several .zip files (or just one, depending on the download source). The users can use programs such as WinRar or 7Zip to extract those files. When you extract the files, you’ll get a setup file.

  3. Double-click on the setup file and follow the instructions.
  4. When the installation is complete, the system might prompt the user to install additional software such as Visual C Redistributable Packages. If the users already installed these packages, then they can move on to the next step.

  5. To open the GPEditor, press Windows key + R button on the keyboard.
  6. In the dialogue box, type ‘gpedit.msc’.
  7. People who have a 32-bit Windows system do not need to follow the next steps. The Global Policy Editor should be working properly now. People who have 64 bit Windows systems need to do the following:

  8. Open the File Explorer by pressing the Windows key.
  9. Navigate to the boot drive C:\Windows\SysWOW64

The user should see two folders GroupPolicy and GroupPolicyUsers along with the gpedit.msc file. These files need to be copied over to the Windows system folder (C:\Windows\System32). Once the users do that, they will be able to access the GPEditor by using the commands in the third and the fourth step.

Fixing the Error

There are multiple reports online about an error that keeps appearing despite the fact that all the steps were done properly. The users say that the error ‘MMC could not create the snap-in’ prevents them from using the editor. If you’re experiencing the same issue, do the following:

  1. Open the File Explorer by pressing the Windows key.
  2. Navigate to C:\Windows\Temp\gpedit
  3. The folder needs to be there. If it isn’t, there was probably a mistake during the installation, so it’s better to retrace the steps. The user needs to replace two files in that folder, which is why it’s so important. The files are x86.bat and x64.bat.

  4. Copy the files over.
  5. Confirm by clicking on Yes to replace them.
  6. The following steps are optional, and they should be used in order to check if everything works nicely. Alternatively, the users can use them if there are some errors.

  7. Hold the Windows key + R button.
  8. Type sysdm.cpl in the dialogue box.sysdm.cpl
  9. Press Enter.
  10. Select the Advanced tab.system properties
  11. Click on the Environment Variables button.environment variables
  12. Double-click on the path in the lower window.
  13. Select New.
  14. Type the following command %SystemRoot%\System32\Wbem. Hit Enter.edit environment variables
  15. Click OK to confirm.

Hopefully, all of these steps should have fixed the problem by now. The user should check if everything works. If it doesn’t work, it’s a good idea to go back and redo the steps because there’s a chance that something was left out. If it still doesn’t work, we have one last solution.

What to Do After Copying And Replacing The Files.

We’ve read several user reports on various tech forums where the issue is still persistent and the editor refuses to work. In order to get the gpedit.msc working, try following these steps:

  1. Press the Windows key on the keyboard once.
  2. In the dialogue box, type ‘cmd’.
  3. Right-click on the Command Prompt and click on Run as administrator.
  4. In Command Prompt, type cd/.
  5. Hit Enter.
  6. Now, type cd windows.
  7. Hit Enter.
  8. Type cd temp.
  9. Hit Enter again.
  10. Type cd gpedit.
  11. Hit Enter yet again.

The following steps are for both versions of the system. The 32-bit Windows users should use step 12 and 64-bit Windows users should use step 13.

  • For 32bit Windows, type x86.bat and hit Enter.
  • For 64bit Windows, type x64.bat and hit Enter.

We’re absolutely positive that everything will work now and that the users will be able to access the gpedit.msc without any problems.


Please enter your comment!
Please enter your name here