Windows 10: Open Local Group Policy Editor in Windows 10

How to: Open Local Group Policy Editor in Windows 10

How to Open the Local Group Policy Editor in Windows 10


The Local Group Policy Editor (gpedit.msc) is a Microsoft Management Console (MMC) snap-in that provides a single user interface through which all the the Computer Configuration and User Configuration settings of Local Group Policy objects can be managed.
Computer Configuration
Administrators can use Computer Configuration to set policies that are applied to computer, regardless of who logs on to the computers. Computer Configuration typically contains sub-items for software settings, Windows settings, and administrative templates.

User Configuration
Administrators can use User Configuration to set policies that apply to users, regardless of which computer they log on to. User Configuration typically contains sub-items for software settings, Windows settings, and administrative templates.
By default, policies set in the Local Group Policy Editor are applied to all users unless you apply user policy settings for all users except administrators.

The Local Group Policy Editor is only available in the Windows 10 Pro, Enterprise, and Education editions.

Local Group Policy Settings Reference:

• Download Group Policy Settings Reference for Windows and Windows Server
• Group Policy Search (Registry path and key)

This tutorial will show you different ways on how to open the Local Group Policy Editor in Windows 10.

You must be signed in as an administrator to be able to use the Local Group Policy Editor.



CONTENTS:

• Option One: Open Local Group Policy Editor in Run
• Option Two: Open Local Group Policy Editor in Search
• Option Three: Open Local Group Policy Editor in Command Prompt
• Option Four: Open Local Group Policy Editor in PowerShell

EXAMPLE: Local Group Policy Editor









OPTION ONE [/i] Open Local Group Policy Editor in Run
1 Open Run Win + R.

2 Type gpedit.msc into Run, and click/tap on OK.









OPTION TWO [/i] Open Local Group Policy Editor in Search
1 Open Search Win + S.

2 Type gpedit.msc or group policy into the search box, and press Enter to open the "Best match" gpedit.msc or Edit group policy.











OPTION THREE [/i] Open Local Group Policy Editor in Command Prompt
1 Open a command prompt.

2 Type gpedit.msc into the command prompt, and press Enter.









OPTION FOUR [/i] Open Local Group Policy Editor in PowerShell
1 Open PowerShell.

2 Type gpedit.msc into PowerShell, and press Enter.





That's it,
Shawn


Related Tutorials

• How to Manually Update Group Policy Settings in Windows 10
• How to See Applied Group Policies in Windows 10
• How to Backup and Restore Local Group Policy Objects in Windows 10
• How to Apply Local Group Policies to Specific User in Windows 10
• How to Apply Local Group Policy to Non-Administrators in Windows 10
• How to Apply Local Group Policy to Administrators in Windows 10
• How to Reset All Local Group Policy Editor Settings to Default in Windows 10

:)

 

OSK no longer working.

Local Group Policy Editor is not available for Windows 10 Home.

Please refer to the link below for the steps on how to enable Local Group Policy Editor for Windows 10 Home.

How to enable Local Group Policy Editor in Windows 10 Home.

Try the troubleshooting steps above again after enabling the Local Group Policy Editor.

We're looking forward to your response.

 

Hide specific Event Viewer error

The window header here reads Local Group Policy Editor, not Group Policy Management Editor, and the APPLICATIONS tree is not shown.

Single user on this Windows 10 Pro PC. Thanks.

 

Hey mate, *Smile

That looks to be from some 3rd party program instead.

 

Nope, I just upgraded from Home to Pro through Settings by changing the product key and this is what I got from Microsoft.

EDIT: Just found something interesting. The MMC only shows up if I run gpedit in System32. If I run it from SysWOW64, it goes to group policy.

 

I noticed the path in your screenshot shows the file on the "E" drive instead of "C" where Windows is normally installed at.

When you had W10 Home, do you remember ever installing anything to enable the Local Group Policy Editor for that edition?

It sounds like the gpedit.msc file be corrupted or been modified if the above is true. You might see if running a SFC /SCANNOW command may repair the file in the System32 folder.

 

sfc /scannow returned the following from E:\WINDOWS\SysWOW64\ which could not be "reprojected"; nothing from System32:

gpedit.dll
fdeploy.dll
fde.dll
gptext.dll

Primitive installers committed for repair

What is the difference in running gpedit.msc from SysWOW64 and System32 other than the path is defined to the System32 folder?

 

Anything running from SysWOW64 would be a 32-bit process, while anything running from System32 would be a 64-bit process. Otherwise, there would be no difference.

*Arrow See if Process is 32-bit or 64-bit in Windows 10 General Tips Tutorials

 

What I don't understand is that I copied gpedit.msc from SysWOW64 to System32 and it still pull up the app shown in #1; how is that possible?

 

I don't recognize the app in your screenshot for this.

When you had W10 Home, do you remember ever installing anything to enable the Local Group Policy Editor for that edition?

 

I added group policy from a 3rd party to Windows 10 Home, but I just uninstalled it from control panel. Would a refresh correct it or would that just be a guess?

 

That could be the cause of this if it didn't uninstall properly.

Refreshing Windows should sort this though.