Why won’t the “Local Group Policy Editor” open in Windows 10?.

Why won’t the “Local Group Policy Editor” open in Windows 10?

Method 1: Activate GPOs in Windows Home

If “Local Group Policy Editor” does not open in Windows 10 Home, this does not indicate a bug, but rather a limitation in the functionality of your edition of the operating system. The GPO plugin is not available in Windows 10 Home, however, you can activate it with a little trick.

Why won’t the “Local Group Policy Editor” open in Windows 10?
  • Open the usual “Notepad” system and paste the following code into it:

    @echo off
    dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >find-gpedit.txt
    dir /b C:\Windows\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>find-gpedit.txt
    for /f %%i in (‘findstr /i . find-gpedit.txt 2^>nul’) do dism /online /norestart /add-package:”C:\Windows\servicing\Packages\%%i”
    pause

  • Save the file with an arbitrary name, but make sure it has a CMD or BAT extension. To do this, add a point in the resolution itself, and in the “File type” field. expose “All Files (*.*)”.
  • Run the created script as administrator.
  • This will open “Command Prompt”, which will ask you to press any key once the component installation is complete.

    Why won’t the “Local Group Policy Editor” open in Windows 10?

    After that, you can try running “Local Group Policy Editor” with the gpedit.msc command.

    Method 2: Recreate the “Registy.pol” file

    A problem opening gpedit.msc can also be caused by a corrupt “Registy.pol” service file that stores policy settings and administrative templates. In this case, restarting it should help.

    Why won’t the “Local Group Policy Editor” open in Windows 10?
  • Go through “Driver”. in the agreement C:\Windows\System32\GroupPolicy.
  • Change the name of the directory. “Machine” with file “Registy.pol” v “Machine.old” and run “Local Policy Editor”.
  • This will create a new folder in Windows 10 “Machine” with the corrected “Registy.pol” file. The toolkit should start without errors.

    Method 3: PATH variable

    If you don’t run any other standard Windows 10 tools besides gpedit.msc with the same name, it doesn’t hurt to check the state of the PATH variable, which allows programs to run without specifying the full path of their executable files.

    Why won’t the “Local Group Policy Editor” open in Windows 10?
  • Open system properties in the “Advanced” tab. To do this, run the command systempropertiesadvanced on the numpad, by pressing Win + R in the dialog box.
  • Click the “Environment Variables” button in the system properties window.
  • Find it in the “System Variables” block. entry “Path” and double-click on it to open its editing window.
  • Make sure that at least the paths are specified as the value of the variable %SystemRoot% and %SystemRoot%\system32.
  • If they are missing, click on the “Create” edit window, enter the missing path and save the settings by pressing “OK”.
  • Method 4: Restore system files

    It cannot be ruled out that the inability to start gpedit.msc is caused by corrupted system files. To check, run a system scan with the “SFC” utility.

  • Run “PowerShell” from the context menu of the “Start” button or any other way you know of.
  • In the console that appears, run the sfc /scannow command.
  • Wait for the verification procedure to complete. If any corruption is found, the “SFC” utility will repair it by replacing the corrupted files with the original ones from Windows 10 built-in storage. If the methods described above don’t help, try restoring your Windows 10 to the nearest restore point.

    Read more: Go back to a restore point in Windows 10

    Why won’t the “Local Group Policy Editor” open in Windows 10?