Turn on Script Execution
Verified with Windows 11 25H2 — updated on July 30, 2026
Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
Path in the GPO console
Computer Configuration\Administrative Templates\Windows Components\Windows PowerShell User Configuration\Administrative Templates\Windows Components\Windows PowerShell Description
This policy setting lets you configure the script execution policy, controlling which scripts are allowed to run. If you enable this policy setting, the scripts selected in the drop-down list are allowed to run. The "Allow only signed scripts" policy setting allows scripts to execute only if they are signed by a trusted publisher. The "Allow local scripts and remote signed scripts" policy setting allows any local scrips to run; scripts that originate from the Internet must be signed by a trusted publisher. The "Allow all scripts" policy setting allows all scripts to run. If you disable this policy setting, no scripts are allowed to run. Note: This policy setting exists under both "Computer Configuration" and "User Configuration" in the Local Group Policy Editor. The "Computer Configuration" has precedence over "User Configuration." If you disable or do not configure this policy setting, it reverts to a per-machine preference setting; the default if that is not configured is "No scripts allowed."
Registry
Software\Policies\Microsoft\Windows\PowerShell Software\Policies\Microsoft\Windows\PowerShell Value name: EnableScripts
Enabled: EnableScripts = 1
Disabled: EnableScripts = 0
MDM / Intune (CSP)
./Device/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableScripts ./User/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableScripts Microsoft Learn documentation Mapping data: Microsoft Learn (CC BY 4.0)
Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
Applying both scopes creates an ambiguous configuration (computer takes precedence over user). Only do this intentionally.
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Turn on Script Execution
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\PowerShell]
"EnableScripts"=dword:00000001
"ExecutionPolicy"="AllSigned"More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Turn on Script Execution
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
$path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'EnableScripts' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'ExecutionPolicy' -Value 'AllSigned' -Type StringIntune XML
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/ADMX_PowerShellExecutionPolicy/EnableScripts
Data type: String
Value:
<enabled/>
<data id="ExecutionPolicy" value="AllSigned"/>Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Turn on Script Execution
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell' -Name 'EnableScripts' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell' -Name 'ExecutionPolicy' -Expected 'AllSigned' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Turn on Script Execution
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
$path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'EnableScripts' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'ExecutionPolicy' -Value 'AllSigned' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: Turn on Script Execution
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: Turn on Script Execution
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell' -Name 'EnableScripts' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell' -Name 'ExecutionPolicy' -Expected 'AllSigned' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Turn on Script Execution
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Microsoft Windows 7 or Windows Server 2008 family
$path = 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'EnableScripts' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'ExecutionPolicy' -Value 'AllSigned' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.