Group Policy Client Extensions
The script finds package manifests matching the Windows Microsoft-Windows-GroupPolicy-ClientExtensions-Package family in the local servicing package directory.
Windows Configuration Utility
Group Policy Editor
Group Policy Editor is a free PowerShell utility intended for Windows 10/11 Home. It locates the Group Policy Client Tools and Client Extensions packages already present in the local Windows servicing store and adds those packages to the running Windows installation with DISM.
Overview
What the utility actually installs
The script searches %SystemRoot%\servicing\Packages for Windows package manifests whose names begin with the Group Policy Client Extensions and Group Policy Client Tools package families. It then processes those local package manifests with DISM.
Group Policy Client Tools
It also finds package manifests matching the Windows Microsoft-Windows-GroupPolicy-ClientTools-Package family.
Local package inventory
The package names found on the current PC are written to List.txt. The script regenerates this list from the machine's own Windows servicing store when it runs.
DISM package installation
Each package listed in List.txt is passed to Windows DISM using the online image and the corresponding local .mum package manifest.
How It Works
Installation process
- The batch launcher starts PowerShell and requests administrator elevation through UAC.
- PowerShell changes its working directory to the folder containing
GPE.ps1. - The script searches the Windows servicing package directory for Group Policy Client Extensions package manifests.
- It searches the same directory for Group Policy Client Tools package manifests.
- The matching package filenames are written to
List.txt. - Each package is added to the current online Windows installation with DISM.
- When the loop finishes, the script displays a completion message and waits for Enter before closing.
Transparency
What the launcher and PowerShell script do
Administrator elevation
Run Me.bat starts a new PowerShell process with -Verb RunAs, which triggers the Windows UAC prompt.
ExecutionPolicy Bypass
The batch launcher starts PowerShell with -ExecutionPolicy Bypass for this launch so the downloaded local script can run without changing the machine's permanent execution-policy configuration.
No third-party package download
The PowerShell script contains no download command. The packages it adds are taken from the Windows servicing package directory already present on the PC.
No forced restart
DISM is called with /norestart. The script itself does not issue a reboot command.
dism /online /norestart /add-package:"<local Group Policy .mum package>"
Package Files
Why List.txt is included
The ZIP includes a List.txt file, but the PowerShell script rebuilds it when run. That allows it to use the Group Policy package filenames found on the current Windows installation rather than depending only on the versions that happened to be listed when the ZIP was created.
Instructions
Running Group Policy Editor
- Download and extract Group Policy Editor.zip.
- Run Run Me.bat.
- Click Yes when Windows asks for administrator permission.
- Allow the DISM package operations to complete.
- Press Enter when the script displays its completion message.
The included Read Me notes that Windows 11 may display a “Windows protected your PC” SmartScreen message because the script was downloaded. Review the files before choosing “More info” and “Run anyway.”
Scope
Designed for Windows Home editions
The included Read Me describes this utility as a way to get Group Policy Editor on Windows 10/11 Home and notes that Group Policy Editor is already included with Pro or Enterprise editions. Running the utility on editions that already include the feature is therefore unnecessary.
FAQ
Frequently asked questions
Does this download Group Policy Editor from another website?
No. The current script contains no download command. It works with Group Policy package manifests located in the PC's Windows servicing package directory.
Does it require administrator permission?
Yes. The included batch launcher explicitly requests an elevated PowerShell session through UAC.
Does it permanently change PowerShell's execution policy?
The launcher uses -ExecutionPolicy Bypass for the PowerShell processes it starts. It does not contain a command that permanently changes the configured execution-policy setting.
Will the script automatically restart Windows?
No. DISM is run with /norestart, and the script contains no restart command.
Why does it create List.txt?
It uses that file as a temporary list of the Group Policy Client Extensions and Client Tools package manifests found on the current PC before processing them with DISM.
Do I need this on Windows Pro or Enterprise?
The included Read Me says Group Policy Editor already comes with Pro and Enterprise editions, so this utility is intended for Windows Home.