Skip to main content

How to Open Local Group Policy Editor on Windows

Local Group Policy Editor will let you control a lot of settings that don’t necessarily have a graphical representation without having to modify the Registry.  When used correctly, the Group policy is a powerful tool capable of unlocking and disabling features that are normally inaccessible via the conventional paths.

What is Local Group Policy Editor

The Local Group Policy Editor (gpedit.msc) is essentially a Management Console (MMC) snap-in that acts as a common interface for all Computer Configuration and User Configuration settings. The administrator can use thegpedit.msc tool to create policies that will then be applied to the computer (regardless of who’s accessing it) or only to certain users that log-in with their user’s accounts.

In the event that the administrator uses Computer Configuration to set a policy, the settings will be applied to all users regardless of who is logged on. If the administrators make use of User Configuration to enforce a policy, it will apply to those users (regardless of the computer that they use).
By default, the policies that are enforced with Local Group Policy Editor produce effects with all users unless the administrator specifies otherwise.
Note: Keep in mind that the Local Group Policy Editor is only found on Windows 10 Enterprise, Windows 10 Education, and Windows 10 Pro editions. If you don’t have one of these editions but you still want to use the Local Group Policy Editor, follow this article (here) for steps on installing Local Group Policy Editor (gpedit.msc) on Windows 10 Home.

How to Open Local Policy Editor

Once you are certain that your computer is equipped to open the Local Group Policy Editor, here’s a list of different methods that you can use to open the gpedit.msc tool in Windows 10. Keep in mind that all methods will help you achieve the same exact thing, so follow whichever method seems more convenable to your situation.
Note: Keep in mind that whatever method you end up using, you need to be signed in with an administrator account in order to open and use the Local Group Policy Editor.

Method 1: Open Local Group Policy Editor via a Run Box

This is one of the quickest ways to access the Local Group Policy Editor. To open the gpedit.msc tool from a Run box, press Windows key + R to open up a Run box. Then, type “gpedit.msc” and hit Enter to open the Local Group Policy Editor.
Note: If you get a message saying the “Windows cannot find gpedit.msc”, it’s probably because your Windows 10 version is not equipped to open the Local Group Policy Editor.

Method 2: Open Local Group Policy Editor via the Search bar

Another speedy way to get around opening the gpedit.msc tool is via the search function. Here’s how to do this:
  1. Start by clicking on the Windows start bar (bottom-left corner) or press the Windows key.
  2. Then, type gpedit.msc to make use of the search function. Next, click on Edit group policy and click the Yesbutton at the UAC (User Account Control).

Method 3: Open Local Group Policy Editor via Command Prompt

Another way to go around opening the Local Group Policy Editor is to use Command Prompt to launch the gpedit.msc tool. Here’s how to do this:
  1. Open a Command Prompt window (it doesn’t have to be elevated) – to open a Command Prompt window, either access the start bar (Windows key) and use the search function to search for “cmd” or press Windows key + R to open a Run box, then type “cmd” and press Enter to open a Command Prompt Window.
2. Then in the Command Prompt window, simply type gpedit.msc and press Enter to open the Local Group Policy Editor.

Method 4: Open a Local Group Policy Editor in PowerShell

Another way to open the Local Group Policy Editor (gpedit.msc) tool is via Powershell. The procedure is highly similar to Command Prompt. Here’s how to do it:
  1. Open Powershell by accessing the Windows Start menu, type “powershell” and click on Windows Powershell.
    Note: Additionally, you can open Windows Powershell by opening a Run box (Windows key + R), typing “powershell” and hitting Enter to open Windows Powershell.
  2. In Powershell, type “gpedit.msc” and hit Enter to open the Local Group Policy Editor.

Method 5: Opening the Local Group Policy Editor via Control Panel

Another way to open the gpedit.msc tool is via the old Control Panel menu. As you know, Microsoft is slowly replacing the old Control Panel with the new Settings menu, but that doesn’t mean you can no longer access it. Follow the steps down below to open the Local Group Policy Editor from the Control Panel menu:
  1. Press Windows key + R to open up a new Run box. Then, type “control” and hit Enter to open the old Control Panel menu.
  2. In Control Panel,  click on Administrative tools and then double click on Local Group Policy Editor.Note: Another way to do this is to use the search function in the top-right corner to search for group policy, then click on Edit group policy.

Method 6: Opening the Local Group Policy Editor via Settings

Another way to open the Local Group Policy Editor is via the Settings charm. Here’s a quick guide on how to do this:
  1. Press Windows key + I to open the Settings app of Windows 10.
  2. Then, use the search function of the Settings app to search for “group policy“.
  3. Next, click on Edit group policy to open the Local Group Policy Editor.

Method 7: Open the Local Group Policy Editor manually

The manual way to open the gpedit.msc tool is to manually browse to the location of the Local Group Policy Editor and double-click on the executable. Here’s a quick guide on how to do this:
  1. Open Windows File Explorer and navigate to C:\ Windows \ System32.
  2. Then, either locate gpedit.msc manually or use the search function (top-right corner) to search for it.
  3. Double-click on gpedit.msc to open up the Local Group Policy Editor and click Yes at the UAC prompt.
Note: If you find yourself using the gpedit.msc utility frequently, you can create a shortcut by right-clicking on it and choosing  Send to > Desktop.

Comments

Popular posts from this blog

Fix: System Found Unauthorized Changes on the Firmware, Operating System or UEFI Drivers

Several users are struggling with the  System found unauthorized changes on the firmware error  at every startup or when trying to take their computer out of hibernation mode. Most affected users report that the issue started occurring after they installed some pending Windows updates. The issue is mostly encountered on Windows 7. The system found unauthorized changes on the firmware, operating system or UEFI drivers. Press [OK] to run the next boot device, or enter directly to BIOS Setup if there are no other boot devices installed. What is causing the System found unauthorized changes on the firmware error We investigated this particular issue by looking at various user reports. This error will occur whenever your system is checking the firmware one some computer hardware parts as part of a new security feature. To be precise, the error is occurring because not all Windows versions will support this new security feature. As it turns out, there are sev...

Fix: The Following Error Occurred Attempting to Join the Domain

Several users are getting the ‘ following error occurred attempting to join the domain ‘ error when trying to connect a computer to a home or work domain. Most of the time, the error is accompanied by an explanation message telling the user that it has exceeded the maximum number of computer accounts. The issue is not restricted to computers that connect to a domain for the first time, as it’s often reported to occur with PCs and laptops previously connected to the same domain. The following error occurred attempting to join the domain. Your computer could not be joined to the domain. What is causing the ‘following error occurred attempting to join the domain’ error? We investigated this particular error by looking at various user reports and the troubleshooting guides that they themselves followed to get the issue resolved. Based on what we were able to gather, there are several different scenarios that might trigger this particular error message: SMB1 support is di...

How to Fix Startup Repair Loop on Windows 7

Getting a  boot loop  which doesn’t let you go past the  Startup Repair  in Windows 7 is something that a lot of users have experienced, and it is most likely due to corrupt registry entries. It might be your mistake if you have messed around in the registry and changed a key you shouldn’t have, but it can also happen by itself, as Windows isn’t really immune to that kind of problems. No matter whether it is your fault or not, you will not be able to boot up Windows, as it will be stuck rebooting itself and won’t make it past the  Startup Repair  screen no matter what. However, there is a solution that begins at the Startup Repair screen, and uses the command prompt to fix the problem by backing up your files, and refreshing Windows, so follow the steps below to see how you can get out of the boot loop. Backup your old files and refresh your Windows In order to start the system in start-up repair, you will need either the windows installation ...