Windows Admin

Open Group Policy Editor on Windows Pro

Access Local Group Policy when you need machine-wide settings beyond Settings app.

9 min read Intermediate Updated 9 Jun 2026

Step-by-step guide

Work through each section in order. Stop when your issue is resolved — you do not need every step for every situation.

Warning

Group Policy changes apply machine-wide and can lock you out of features if misconfigured. Export policy before editing. Windows Home does not include gpedit.msc — use Settings or registry with extreme care instead.

What you will achieve

Open Local Group Policy Editor on Windows Pro or Enterprise, navigate policy trees confidently, and know Home-edition alternatives when gpedit is unavailable.

1) Confirm your edition

  1. Press Win + R, type winver — look for Pro, Enterprise, or Education.
  2. Home and Home Single Language lack Local Group Policy Editor — skip to section 5.

2) Launch Group Policy Editor

  1. Press Win + R, type gpedit.msc, press Enter.
  2. Or search Start for Edit group policy.
  3. Two main branches appear: Computer Configuration (all users) and User Configuration (current user).

3) Navigate and apply a policy

  1. Expand Computer Configuration → Administrative Templates (most security and update policies live here).
  2. Double-click a policy to read Help text — explains scope and reboot requirements.
  3. Set Enabled, Disabled, or Not Configured (inherit default).
  4. Run gpupdate /force in Admin Command Prompt to apply immediately, or reboot if the policy requires it.

4) Back up before changes

Export current policy from an elevated Command Prompt:

mkdir C:\GPBackup
LGPO.exe /b C:\GPBackup /n "Before changes"

LGPO.exe is in the Microsoft Security Compliance Toolkit. Simpler approach: document each policy path and set Not Configured to undo. For one policy, note the previous state in a text file before toggling.

5) Home edition alternatives

Windows Home cannot run gpedit.msc natively. Options:

  • Use equivalent Settings pages where they exist (Update pause, privacy, sign-in).
  • Apply per-user settings via Registry Editor (regedit) only when Microsoft documents the matching key — wrong keys break profiles.
  • Upgrade to Pro if you legitimately need enterprise policy control on a personal machine.

Third-party “enable gpedit on Home” scripts are unsupported and sometimes install malware — avoid them.

6) Find applied policies quickly

In gpedit, use Administrative Templates → All Settings sorted by State to list Enabled and Disabled policies only. In Command Prompt, gpresult /h gp-report.html generates an HTML report of Computer and User policy results — open in a browser to see which settings are active on the machine right now.

Related guides

gpedit group policy windows pro