What is the Group Policy Editor?
The Local Group Policy Editor is the MMC snap-in that edits the local Group Policy object stored on a single computer. Policies differ from ordinary settings: they are enforced, users cannot change them in Settings or Control Panel, and they persist across sign-ins and restarts. In a domain, administrators set the same kinds of options centrally in Group Policy Objects (GPOs) linked to sites, domains and organizational units, using the Group Policy Management Console (gpmc.msc) rather than gpedit.
Opening it and edition limits
Press Win+R and type gpedit.msc, approving the UAC prompt. The editor is included in Windows Pro, Enterprise and Education but not in Windows Home, which is one of the practical differences between editions. Local Security Policy (secpol.msc) shows only the security settings branch and has the same edition limit.
Layout
The tree has two halves, and each contains Software Settings, Windows Settings and Administrative Templates:
- Computer Configuration applies to the machine no matter who signs in, and is processed at startup. Examples: Windows Update behavior, BitLocker options, password and account lockout policy (Windows Settings > Security Settings > Account Policies), startup and shutdown scripts.
- User Configuration applies to user accounts and is processed at sign-in. Examples: hiding or restricting Control Panel and Settings, blocking the registry editor or Command Prompt, logon and logoff scripts, desktop restrictions.
Most settings sit under Administrative Templates, which are defined by .admx files in C:\Windows\PolicyDefinitions. Each policy is Not Configured, Enabled or Disabled, and its help text explains exactly what each state does. The All Settings node and the filter options help you find a policy when you know its name but not its folder.
Applying and checking policy
gpupdaterefreshes policy, andgpupdate /forcereapplies every setting rather than only the changed ones. Some settings still need a sign-out or restart, and gpupdate will offer one.gpresult /rsummarizes which GPOs applied to the computer and the user, andgpresult /h report.htmlsaves a detailed report. Run it elevated to include the computer half.- Domain-joined computers also refresh policy in the background, by default about every 90 minutes with a random offset.
Local policy vs. domain policy
Policies apply in the order local, site, domain, then organizational unit (often remembered as LSDOU). When two settings conflict, the one applied last wins, so a domain or OU policy overrides a local setting made in gpedit. If a gpedit change does not stick on a domain-joined PC, run gpresult to find the domain GPO that sets the same option.
Troubleshooting cues
- An option is greyed out or Windows says some settings are managed by your organization: a policy is set. Check gpresult and the editor before trying other fixes.
- "Windows cannot find gpedit.msc" on a home PC: the edition is Home; upgrade to Pro or use another method.
- Policy settings are stored in the registry's Policies keys. Change them in the editor rather than by hand, or the policy will simply apply again.
Group Policy Editor on the CompTIA A+ exam
The Group Policy Editor is one of the Windows tools in Core 2 (220-1202) objective 1.4, and its absence from Home is one of the edition differences in objective 1.3. Know the gpedit.msc command, Computer Configuration versus User Configuration, and the gpupdate /force and gpresult /r commands. Cues: enforce a password or lockout rule on a standalone Pro PC, think gpedit or secpol; a policy change is not taking effect, think gpupdate /force, then gpresult; gpedit is missing, think Windows Home.