Key points
- When a Reset Is Necessary: When system instability occurs after configuration changes, third-party software has made unwanted Group Policy modifications, or you need to restore a clean baseline before reconfiguring policies.
- Reset via File Explorer: Navigate to “%WinDir%\System32\GroupPolicy” and “%WinDir%\System32\GroupPolicyUsers” in File Explorer and delete the contents of both directories.
- Reset via Command Prompt: Run “RD /S /Q “%WinDir%\System32\GroupPolicy”” and “RD /S /Q “%WinDir%\System32\GroupPolicyUsers”” as administrator.
- Reset via PowerShell: Run “Remove-Item -Recurse -Force “$env:WinDir\System32\GroupPolicy”” and “Remove-Item -Recurse -Force “$env:WinDir\System32\GroupPolicyUsers”” as administrator.
- Reset via Group Policy Editor: Open “gpedit.msc,” locate each modified Group Policy Object, and set it back to “Not Configured.”
- Apply Changes After Any Reset: After resetting Local Group Policy by any method, run “gpupdate /force” to ensure the restored default settings take effect immediately.
This tutorial demonstrates how to reset all Local Group Policy settings back to default in Windows 11. This can help you troubleshoot your system if you’ve been making tweaks using Group Policy and restore your system to its initial state to improve stability.
If you’re having trouble opening the Local Group Policy Editor, watch the video “How to Open the Local Group Policy Editor in Windows 10 and Windows 11” for a visual guide.
Understanding Local Group Policy in Windows 11
Group Policy allows you to centrally manage system and user settings as well as application configurations. It includes policies for managing security, user permissions, network settings, and other system behavior. Group Policy functionality is available in the Pro, Enterprise, and Education versions of Windows 11.
Group Policy Objects (GPOs) are sets of configuration options that affect how the associated Windows feature or application behaves. GPOs are split into Computer Configuration (applying to only the current Windows PC and any user who’s logged into it) and User Configuration (applying to a specific user account and being applied to whichever device they log into for the duration of their session).
Group policies can be set up on a single PC using Local Group Policy or deployed to multiple PCs that are part of a Windows domain:
- Local Group Policy: Local group policies only apply to the PC they’re configured on. Local Group Policy is always overridden by Group Policy in Active Directory.
- Group Policy in Active Directory: Group Policy Objects that are defined in Windows Active Directory (e.g., in an enterprise or education environment) give you centralized control of users and computers connected to a Windows domain. Group policies in Active Directory can be scoped per user or based on organizational units (OUs).
Administrative tasks performed using Group Policy often include the following:
- Automatically connecting network shares and shared printers
- Configuring logon/logoff scripts
- Enforcing internet browser security settings
- Ensuring firewalls and antivirus are enabled
- Blocking certain applications or Windows features (e.g., restricting computer usage to only approved productivity apps, disabling administrative tools)
Group Policy in Windows 11 25H2
If you’re running Windows 11 2025 Update (25H2), note that Microsoft added 42 new policy settings in this release compared to Windows 11 24H2.
Most of these new settings relate to Windows Copilot and the Recall feature, with 13 policies specifically dedicated to AI functionality on Copilot+ PCs. More broadly applicable additions include new options for customizing the Start menu and taskbar as well as a policy to remove preinstalled Microsoft Store applications.
If you reset your Group Policy settings and need to reconfigure any of these, Microsoft publishes the full list in the Group Policy Settings Reference Spreadsheet for Windows 11 25H2, which was last updated in February 2026.
When and why to clear Group Policy settings
Group policies grant a great deal of control over your Windows system, and it may become necessary to revert all changes in case a mistake was made or the system has become unstable after making multiple configuration tweaks. It may also be necessary to reset Group Policy settings to their default if third-party software has made an unwanted change.
Resetting local group policies shouldn’t affect your personal files but may affect programs that rely on Group Policy Objects. Make sure you take a full system backup before making any changes to Group Policy, just in case there are unintended side effects.
How to reset Local Group Policy settings to default
Before you follow any of the steps in this article, make sure you back up your Local Group Policy settings so that you can restore them if something goes wrong.
The most efficient way to revert Local Group Policy to its default state is to delete all of its configuration files. This brief video, “How to Reset All Local Group Policy Settings to Default in Windows,” walks you through each method step by step. This can be done in several different ways.
Using Windows Explorer
- Open File Explorer.
- Navigate to %WinDir%\System32\GroupPolicyand %WinDir%\System32\GroupPolicyUsers.
- Delete the contents of each directory.
You’ll need to be logged in as an administrator to do this.
Using the Command Prompt
Running the following Command Prompt command as an administrator will delete the configurations used to set Local Group Policy, restoring it to its default state:
RD /S /Q “%WinDir%\System32\GroupPolicy”
RD /S /Q “%WinDir%\System32\GroupPolicyUsers”
Using PowerShell
Run the following PowerShell command as an administrator to force the deletion of Local Group Policy configuration files:
Remove-Item -Recurse -Force “$env:WinDir\System32\GroupPolicy”
Remove-Item -Recurse -Force “$env:WinDir\System32\GroupPolicyUsers”
Resetting Local Group Policy using the Group Policy Editor
To manually reset each Group Policy Object you’ve modified, follow these steps:
- Open the Local Group Policy Editor.
- Locate the Group Policy Objects you’ve previously modified.
- Toggle them back to Not Configured.
It’s worth nothing that this method isn’t foolproof as you may not remember which changes you’ve made in the past. To comprehensively reset all policies, we recommend using one of the above methods and then recreating any policies you still require.
Post-reset considerations and troubleshooting tips
After using any of the above methods to restore Local Group Policy to its defaults, make sure to run this command:
gpupdate /force
This is to ensure that the new settings are applied. If some settings still fail to revert, try rebooting your Windows PC.
Improved diagnostics in Windows 11 (2026 updates)
If you’re troubleshooting Group Policy Preferences (GPP) failures after a reset, Windows 11 now provides significantly better diagnostic information. The January 2026 cumulative updates introduced Event ID 4117 in Event Viewer, which replaces the legacy Event ID 4098 error. Where the old event gave you only a generic error code with no context, Event ID 4117 surfaces the specific failure, exact file paths, UNC addresses, and recommended remediation steps, all without needing to enable debug logging first.
Additionally, as of the February 2026 Patch Tuesday update, you can now enable GPP debug logging directly through gpedit.msc without manually copying Administrative Template files. (This feature is currently in preview.)
To check for GPP errors after resetting your Group Policy settings, do the following:
- Open Event Viewer (msc).
- Navigate to Applications and Services Logs > Microsoft > Windows > GroupPolicy > Operational.
- Look for Event ID 4117 entries.
Improved registry.pol error reporting
Windows 11 also received an update to how it handles errors in the registry.pol file, the one responsible for translating Group Policy settings into registry keys.
Previously, corruption or unintended changes to this file were difficult to diagnose. Following the February 2026 Patch Tuesday update, the Windows system event log now surfaces actionable details when a registry.pol issue is detected, including what changed and why the policy failed to apply. This is particularly relevant after a Group Policy reset as it can help you confirm that the reset applied cleanly and identify any residual policy conflicts.
Managing Windows Group Policy in an enterprise environment
Local Group Policy can only be used to manage a single Windows device. A Windows domain with Active Directory is required to fully leverage Group Policy to centrally manage tens or thousands of Windows devices, from workstations to tablets, and work-from-home deployments connected using VPNs.
Windows domains provide tools for identity and access management, device management, and security (including antivirus and firewalls) to ensure that the Windows PCs that you’re responsible for are properly configured and secured. The security and resiliency of enterprise networks can be further enhanced by implementing a remote monitoring and management solution that provides full visibility over your IT assets.
On that note, NinjaOne is a complete end-to-end endpoint management solution with a unified interface for configuring and maintaining Windows PCs (as well as Android, Apple, and Linux devices). NinjaOne also allows you to oversee the current configuration for your entire fleet of devices as well as to deploy and roll back changes to their defaults to minimize downtime and reduce support overheads.
Start your free 14-day trial of NinjaOne today or watch a free demo of the software.
