Online Repair
Verified with Microsoft 365/Office 5568.1000 — updated on September 4, 2026
Supported on: At least Windows Server 2008 R2 or Windows 7
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Office 2016 (Machine)\Updates Description
This policy setting controls whether users can run an online repair for an Office client, such as Microsoft 365 Apps for enterprise, that comes with an Office 365 or Microsoft 365 plan. You can also control whether the online repair only uses a local source and doesn't use the Office Content Delivery Network (CDN) on the Internet. Note: Users must have administrative privileges on the local computer to run an online repair. If you enable or don't configure this policy setting, users can run an online repair from "Programs and Features" or "Add/Remove Programs" in Control Panel. The online repair downloads and reinstalls Office from the Office CDN or from a local source, such a network share, depending on how Office is configured to get updates. If you aren't using the Office CDN, the local source must contain all the required files, including language files, to perform the repair. Select "Use Office CDN (if needed)" if you want to use the Office CDN as an alternative location for the repair if the local source isn't available or doesn't contain all the necessary files. You can also use a local copy of the Office Deployment Tool (setup.exe) for the repair by entering a local path for the Office Deployment Tool. This path can be a network share. If setup.exe can't be found in the local path specified, and "Use Office CDN (if needed)" is selected, then the online repair downloads a copy of setup.exe from the Office CDN. Otherwise, the online repair will fail. The repair maintains all configuration settings, including products, languages, excluded applications, and update settings. If you disable this policy setting, users can't run an online repair, but they can still run a quick repair. Note: This policy setting only applies to subscription versions of Office, such as Microsoft 365 Apps for enterprise, and to subscription versions of Project and Visio.
Registry
software\policies\microsoft\office\16.0\common\officeupdate Value name: onlinerepair
Enabled: onlinerepair = 1
Disabled: onlinerepair = 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. ⓘ
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Online Repair
; State: Enabled
; Supported on: At least Windows Server 2008 R2 or Windows 7
[HKEY_LOCAL_MACHINE\software\policies\microsoft\office\16.0\common\officeupdate]
"onlinerepair"=dword:00000001
"fallbacktocdn"=dword:00000000
"localodtpath"=""More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Online Repair
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
$path = 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'onlinerepair' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'fallbacktocdn' -Value 0 -Type DWord
Set-ItemProperty -Path $path -Name 'localodtpath' -Value '' -Type StringIntune 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: Online Repair
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
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\office\16.0\common\officeupdate' -Name 'onlinerepair' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate' -Name 'fallbacktocdn' -Expected 0 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate' -Name 'localodtpath' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Online Repair
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
$path = 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'onlinerepair' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'fallbacktocdn' -Value 0 -Type DWord
Set-ItemProperty -Path $path -Name 'localodtpath' -Value '' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: Online Repair
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
# 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: Online Repair
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
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\office\16.0\common\officeupdate' -Name 'onlinerepair' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate' -Name 'fallbacktocdn' -Expected 0 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate' -Name 'localodtpath' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Online Repair
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
$path = 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'onlinerepair' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'fallbacktocdn' -Value 0 -Type DWord
Set-ItemProperty -Path $path -Name 'localodtpath' -Value '' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.