How to Run Local Group Policy Editor in Windows 10 Pro and Home

This tutorial will show you different ways to run Local Group Policy Editor in Windows 10 Pro and Home. Group Policy is a way to configure computer and user settings for devices that are joined to Active Directory Domain Services (AD) as well as local user accounts.

It controls a wide range of parameters and can be used to enforce and change the default settings for the respective users. Local Group Policy is the basic version of Group Policy for non-domain computers. Local Group Policy settings are stored in the following folders:

C: \ Windows \ System32 \ GroupPolicy
C: \ Windows \ System32 \ GroupPolicyUsers

Local Group Policy Editor in Windows 10

When you need to open the Local Group Policy Editor in Windows 10, you can use Command Prompt, Run command, search in the taskbar, Start menu, or by using the Microsoft Management Console (MMC).

Open Local Group Policy Editor from Start Menu

  1. Open the Start menu and type gpedit.msc.
  2. When an entry will appear at the top of the menu, click it to open the policy editor.Open Gpedit Msc From Start Menu
  3. Note: you can use Search on the taskbar and type gpedit.msc right in the search box.

To view all applied policies in the Computer Configuration section, go to Computer Configuration \ Administrative Templates \ All Settings.

To view all applied policies for the current user, navigate to User Configuration \ Administrative Templates \ All Settings.

Open the Local Group Policy Editor using the Run dialog

  1. Press the Win + X keyboard shortcut or right-click on the Start menu.
  2. Select Run from the menu that opens on the screen.Windows 10 Winx Run
  3. Enter gpedit.msc in the Run input box and click the “OK” button.Run Gpedit Msc

Also, one more method here that involves File Explorer.

Open Local Group Policy Editor using File Explorer

  1. Open File Explorer with a shortcut on the taskbar or simply by pressing the Win + E keyboard shortcut.
  2. In the address bar of the File Explorer, type or copy and paste: gpedit.msc. Hit Enter.Run Local Group Policy Editor From File Explorer

Open Local Group Policy Editor from Command Prompt or PowerShell

Open Command Prompt or you can open a new instance of PowerShell. Type gpedit.msc and press Enter.Run Local Group Policy Editor from PowerShell

Open Local Group Policy Editor as a snap-in in the MMC management console

  1. Open the MMC console. (Click the Start button, type mmc and press Enter).Open Mmc From Start Menu
  2. Select Add or Remove Snap-in from the File menu.Add Remove Snap In In Mmc
  3. In the dialog box that opens, double-click “Group Policy Object Editor” and click “Finish” and “OK”.Run Local Group Policy Editor from Mmc

Open Local Group Policy Editor in Windows 10 Home

As you already know, the Local Group Policy Editor app is available on Windows 10 Pro, Enterprise, or Education. Windows 10 Home users do not have access to gpedit.msc due to OS restrictions. Here is a simple and elegant solution that allows you to unlock it without installing any third-party apps.

There is an easy way to enable Local Group Policy Editor in Windows 10 Home by running just one batch file.

Enable Gpedit.msc (Group Policy) in Windows 10 Home

  1. Download the following ZIP archive.
  2. Unpack its contents to any folder. It only contains one file, gpedit_home.cmd
  3. Right click on the file.
  4. Select “Run as administrator” from the context menu.
  5. When prompted for Windows SmartScreen, click More Details, then click the Run Anyway button.

The batch file will run the DISM tool to activate the Local Group Policy Editor. Wait until the batch file completes its work.

Please be aware that some policies will not work in Windows Home. Some policies are hardcoded for Windows Pro versions. Also, if you activate gpedit.msc using the provided batch file, the change in policies for User Configuration will not take effect. They still require a registry tweak.

You can create such a batch file yourself. Before you start, we recommend that you create a system restore point, and you could undo the changes made in the system at any time.

Gpedit Home Bat File

Open a text editor such as Notepad. Copy and paste the following lines:

@echo off
pushd “%~dp0″

dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt
dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt

for /f %%i in (‘findstr /i . List.txt 2^>nul’) do dism /online /norestart /add-package:”%SystemRoot%\servicing\Packages\%%i”

In the “File” menu of the text editor, select “Save As” in the dialog box in the “File name” line, enter – gpedit.bat and click the “Save” button.Enable Gpedit.msc (Group Policy) In Windows 10 Home

Run the batch file. In the User Account Control window, click the “Yes” button. Wait for the DISM utility to make changes and close the window.

The local group policy editor (gpedit.msc) is enabled and now you can start it in any of the ways described above.

Policy Plus

There is a good alternative to the built-in gpedit.msc application called Policy Plus. This is a third party open source application.

Policy Plus is designed to make Group Policy settings available to everyone, regardless of the OS edition.

  • The app works on all editions of Windows, not just Pro and Enterprise
  • Fully complies with the licensing terms
  • View and edit registry-based policies in local GPOs, individual user GPOs, standalone POL files, offline registry user hives, and a live registry
  • Navigate to policies by ID, text, or individual registry entries.
  • View additional technical information about objects (policies, categories, products)
  • Convenient options to change and import policy settings

Bonus tip: Sometimes when you play with Group Policy, it can cause some unexpected behavior. If you tweaked your operating system using Local Group Policy Editor, you might want to reset everything to defaults. Here’s a bit of good news: you can reset all Local Group Policy settings in Windows 10.

Looks like you've read the post to the end. If you enjoyed it, please share it. You would greatly help our blog to grow!

Author: The MFTNEXT Team

The MSFTNEXT project is a small team of authors who love to engage with the latest technology and gadgets. Being passionate Windows bloggers, we are happy to help others fix their system issues.

Leave a Reply

Your email address will not be published.