The system does not find gpedit.msc. Windows 10: how to fix the situation with the simplest methods?

In modern Windows operating systems, a component such as the Group Policy Editor allows you to make very fine-tuning, limiting or extending the rights of users working on a particular computer terminal to change the settings and settings of the OS. But what to do when the system simply does not find gpedit.msc when trying to call this service? Windows 10 issues an appropriate notification. This situation can be observed in the eighth and seventh modifications.

Error "gpedit.msc not found" (Windows 10): what's the problem?

In most cases, the appearance of such a message has nothing to do with the operability of Windows itself. And then, after all, some users, not having understood the essence of the matter, begin to frantically enter the command sfc / scannow, hoping that the system will restore the missing component.

But why then does this not work? Yes, just because the component itself in certain versions of Windows is simply missing as such. If a message appears that gpedit.msc can not be found, Windows 10, as well as other versions, appears to appear in some entry level modification, such as Home or Education. The developers of the group policy editor have been excluded from these versions. However, it is possible to return it to its place, and quite simply.

The system does not find gpedit.msc. Windows 10: Troubleshooting

So, first you need to find and download the installation distribution of this service or use the already available ones. Pre-log on 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 its own tools. In the first version, you just need to run the installer, after which the installation will occur in automatic mode.

But here it is necessary to take into account one moment. When installing in a 32-bit system, no additional action is required. But if the installation was made in a 64-bit system, from the SysWOW64 directory to the System32 folder (both directories are located in the Windows root directory), you need to copy the following objects:

• The GroupPolicyUsers and GroupPolicy folders;
• The gpedit.msc file.

After that, you can start the service from the console "Run" (Win + R) by entering the appropriate command gpedit.msc.

In the case of installation in a 64-bit system, you can do otherwise. When starting the installer, 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:

• The GroupPolicyUsers folder, 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 modify the rank above (for example, 4.0). Naturally, it's better to install a more recent version to avoid problems in the future.

Instead of an afterword

Thus, with the use of the simplest means and solved the problem that the system does not find gpedit.msc. Windows 10 is not an exception in this respect, so the above solutions can be applied to both the seventh and the eighth modifications. Finally it remains to add that it is necessary to apply the editor's call with the subsequent adjustment of group policies exclusively with the rights of the administrator, since without this the system will not produce such actions.

Separately, we should pay attention to the advisability of adding this component to the 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 limited in rights and without it. But on a home computer or laptop, when there are no other registered users, this service is not needed at all.

In addition, this service is like an understudy of the system registry, if desired or necessary, the necessary parameters can be prescribed there. And one moment. When you make changes to the group policy editor, you will not be able to change the parameters in the registry afterwards. And before installing the service, it is highly recommended to create a system rollback point so that in the event of a failure, you can return to the original state.