In modern Windows operating systems, such a component as the Group Policy Editor allows for very fine-tuning, limiting or expanding the rights of users working on a specific computer terminal to change OS parameters and settings. But what to do when when trying to call this service the system simply does not find gpedit.msc? Windows 10 issues a notification. This situation can be observed in the eighth and seventh modifications.
Error "gpedit.msc not found" (Windows 10): what is the problem?
In most cases, the appearance of such a message has nothing to do with the performance of Windows itself. And then after all, some users, not understanding the essence of the issue, start frantically entering the sfc / scannow command, hoping that the system itself will restore the missing component.
But why then does it not give a result? Yes, only because the component itself in certain versions of Windows is simply missing as such. If a message appears stating that gpedit.msc cannot be found, Windows 10, as well as other versions, is likely to be presented in some kind of entry-level modification like Home or Education. Developers Group Policy Editor excluded from these versions. However, you can return it to its place, and quite simply.
The system does not find gpedit.msc. Windows 10: Fixes
So, first you need to find and download the installation distribution for this service, or use an existing one. You must first log in to user accounts and disable the UAC service. This is done in the control section by moving the notification slider to the lowest position. To solve the problem that the system does not find gpedit.msc, Windows 10 suggests using the service installation from a third-party source or using its own tools. In the first option, you just need to run the installer, after which the installation will occur in automatic mode.
But here you need to take into account one point. When installing in a 32-bit system, no additional steps are required. But if the installation was performed on a system with 64-bit architecture, from the SysWOW64 directory to the System32 folder (both directories are located in the Windows root directory), you need to copy the following objects:
- GroupPolicyUsers and GroupPolicy folders
- gpedit.msc file.
After that, you can start the service from the Run console (Win + R) by entering the corresponding gpedit.msc command.
In case of installation in a 64-bit system, you can do otherwise. When the installer starts, we reach the end of the process, but do not press the finish button. At this point, you need to copy the following objects to the System32 folder from the SysWOW64 directory:
- Folders GroupPolicyUsers, GPBAK, GroupPolicy;
- files gpedit.msc, appmgr.dll, fde.dll, gpedit.dl, gptext.dll and fdeploy.dll.
In both cases, for the service to work correctly, you will need to install the .NET Framework 3.5 or modifications of a higher rank (for example, 4.0). Naturally, it is better to install a more recent version to prevent future problems.
Instead of an afterword
Thus, using the simplest means, the problem is solved that the system does not find gpedit.msc. Windows 10 is no exception in this regard, so the above solutions can be applied to the seventh and eighth modifications. Finally, it remains to add that it is necessary to apply the editor’s call with the subsequent setting of group policies exclusively with administrator rights, since without this the system will not allow such actions.
We should also pay attention to the advisability of adding this component to entry-level systems. If this is a computer terminal, say, in an educational institution, the installation of the editor can still be understood, although users can be restricted in their rights without it. But on a home computer or laptop, when there are no other users registered in the system, this service is not needed at all.
In addition, this service is like a backup of the registry, if desired or necessary, the necessary parameters can be set there. And one moment. When making changes to the Group Policy Editor, subsequently changing the necessary parameters in the registry will fail. And before installing the service, it is strongly recommended that you create a system rollback point so that in the event of a failure you can return to its original state.