Allow native XMLHTTP support
Verified with Windows 11 25H2 — updated on July 23, 2026
Supported on: At least Internet Explorer 7.0
Path in the GPO console
Computer Configuration\Administrative Templates\Windows Components\Internet Explorer\Security Features\AJAX User Configuration\Administrative Templates\Windows Components\Internet Explorer\Security Features\AJAX Description
This policy setting allows the user to run natively implemented, scriptable XMLHTTP. If you enable this policy setting, the user can run natively implemented, scriptable XMLHTTP. If you disable this policy setting, the user cannot run natively implemented, scriptable XMLHTTP. If you do not configure this policy setting, the user can choose to run natively implemented, scriptable XMLHTTP.
Registry
HKLM
Software\Policies\Microsoft\Internet Explorer\Main HKCU
Software\Policies\Microsoft\Internet Explorer\Main Value name: XMLHTTP
Enabled: XMLHTTP = 1
Disabled: XMLHTTP = 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: Allow native XMLHTTP support
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: At least Internet Explorer 7.0
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Internet Explorer\Main]
"XMLHTTP"=dword:00000001More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Allow native XMLHTTP support
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 7.0
$path = 'HKLM:\Software\Policies\Microsoft\Internet Explorer\Main'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'XMLHTTP' -Value 1 -Type DWordIntune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune.Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Allow native XMLHTTP support
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 7.0
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\Internet Explorer\Main' -Name 'XMLHTTP' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Allow native XMLHTTP support
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 7.0
$path = 'HKLM:\Software\Policies\Microsoft\Internet Explorer\Main'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'XMLHTTP' -Value 1 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: Allow native XMLHTTP support
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 7.0
# 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: Allow native XMLHTTP support
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 7.0
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\Internet Explorer\Main' -Name 'XMLHTTP' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Allow native XMLHTTP support
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 7.0
$path = 'HKLM:\Software\Policies\Microsoft\Internet Explorer\Main'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'XMLHTTP' -Value 1 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.