Upon launching the local group policy editor, you may receive a message that the system cannot find a certain file you need. Today we will explain why this happens and how you can fix it in Windows 10.
Three easy methods to fix “gpedit not found” Windows 10
This error is a typical issue for Windows 10 users with Home or Starter versions of the operating system. The explanation is simple – the local policy editor tool is absent in these versions. Nevertheless, people with Professional, Education, or Enterprise version of Windows 10 also get this error from time to time, but in their case, it is usually provoked by malware and viruses or as the result of system failure. No matter the cause of the problem, there are several effective methods to deal with it.
Method #1: installing the patch
For today it is going to be the most popular and the most effective solution. You just need to download and install an unofficial patch that will add needed components to your system. Don’t worry it has no negative effect on your current Windows version. However, we would recommend you to create a system recovery point before you install this patch as all actions written further alter system data.
Follow these steps to complete the process:
1. Download a local group policy editor installer from a trusted source.
2. If it is archived, unpack it with any archiver (WinRAR or 7-Zip, for example).
3. Find the setup.exe file and double-click it.
4. This will initiate the installation wizard, and you will see a welcome window with the description of the program. Click “Next.”
5. The next menu will inform you that everything is ready for installation. Press “Install.”
6. Right after that, the patch and all needed components will be installed on your computer. Wait for the process to end – it should take a few seconds to see a message informing you about successful installation.
Note: from here on you should pay extra attention as your actions will be a bit different depending on the version of the operating system (32-bit or 64-bit). If you have Windows 10 32-bit (x86), then just click “Finish” and start using your newly added group policy editor.
Windows 10 64-bit users will have to do a bit more. They need to leave the final window open (without clicking “Finish”) and complete a few additional manipulations:
1. Press Win+R and type this command – %WinDir%\Temp – in the window that will appear. Hit Enter.
2. You will see a list of file and folders. Find a folder named “gpedit” and open it.
3. Now you need to copy a few files from this folder. We marked them on the screenshot below. These files must be copied to the directory C:\Windows\System32.
4. Now go to the «SysWOW64» folder. It can be found here: C:\Windows\SysWOW64.
5. From this one you will need to copy two folders – “GroupPolicyUsers” and “GroupPolicy” – and the file “gpedit.msc” from the root directory. All of these must be placed into the “System32” folder (C:\Windows\System32).
6. Now you can close everything and reboot your computer. After that, try to press Win+R and execute the gpedit.msc command. Press “OK”.
7. If you did everything right, the group policy editor would be up and running.
No matter the version of your operating system (32-bit/64-bit), it may happen upon opening gpedit after completing all previous steps the tool will open with the MMC error. In this case, you need to go to C:\Windows\Temp\gpedit and find a file “x64.bat” or “x86.bat”. You need to run one of those that correspond to your version of Windows (32-bit = x86/64-bit = x64). All functions integrated into the file will be executed automatically. Now try to start the group policy editor again. It should work without any errors.
Method #2: running a virus/malware scan
As we said before, even users that are not running basic Windows 10 versions (Home or Starter) may have problems with the “gpedit.msc not found” error. In most cases, it is caused by malicious software, which means you will need to install advanced antivirus software – Kaspersky, McAfee, Dr. Web CureIt. Or if you want a lightweight solution, then look at antimalware tools such as Malwarebytes. If you don’t like anything of that – you are free to choose any other tool that gets the job done, which is the most important thing.
After scanning and removing detected threats, you can try to run the group policy editor again. If needed, redo steps detailed in the first method.
Method #3: Windows recovery or reinstalling
In situations when both previous methods don’t yield positive results, you should consider reinstalling your system. There are several ways to install a clean Windows copy on your computer or laptop. Some of them don’t even require additional software. All actions can be performed within Windows with standard tools. Look for the article on our website to learn more about how to install Windows. If you have a recent Windows recovery point, you can also try to “go back in time” to see if it helps.
That’s all the information we have to share with you concerning the “gpedit.msc not found” error. We hope that one of these methods will help to fix the problem and restore the functionality of the group policy editor.