Open in the explorer

Prevent Office from being updated to a specific version

Type
Computer
GPO path
Computer Configuration › Policies › Administrative Templates › Microsoft Office 2016 (Machine) › Updates
Supported on
At least Windows Server 2008 R2 or Windows 7
ADMX file
office16.admx
Internal name
office16/L_UpdateBlockVersion

Explanation

This policy setting allows you to prevent Office from being updated to a specific version, and instead have Office be updated to a different version that you specify.

If you enable this policy setting, you need to specify both the version to block and the version to update Office to. You list the version to block first and separate the two versions with a colon. You can specify more than one version to block by separating the entries with a vertical bar.

For example, if you want to block versions 16.0.10326.10000 and 16.0.10326.20000 and have Office updated to version 16.0.10328.10000 instead, you would enter 16.0.10326.10000:16.0.10328.10000|16.0.10326.20000:16.0.10328.10000.

If the blocked version is already installed, Office will be updated to the other version you've specified.

Note: if you make a mistake entering the versions, the update won't be blocked. Also, be sure that the installation files for the version that you want to update Office to are available on the update location.

If you disable or don't configure this policy setting, Office will be updated to whichever more current version is available in the location where Office is configured to get updates from, unless youve specified a version to block by using the Office Deployment Tool.

Note: This policy setting only applies to Office products that are installed by using Click-to-Run. It doesn't apply to Office products that use Windows Installer (MSI).

Registry

HKEY_LOCAL_MACHINE\software\policies\microsoft\office\16.0\common\officeupdate
Value name
not defined in the ADMX

Enable / disable values: not defined in the ADMX (see the options below).

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Enable

# Enable: office16/L_UpdateBlockVersion
$k = 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Block version
Set-ItemProperty -Path $k -Name 'blockversion' -Value '<value>' -Type String

Disable

# Disable: office16/L_UpdateBlockVersion
# No value is written in the "Disabled" state (nothing defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": office16/L_UpdateBlockVersion
$k = 'HKLM:\software\policies\microsoft\office\16.0\common\officeupdate'
Remove-ItemProperty -Path $k -Name 'blockversion' -ErrorAction SilentlyContinue

Options (1)

LabelControlRegistry valueREG typeConstraints / details
Block version:L_UpdateBlockVersionIDText boxtextblockversionREG_SZ

Application

Microsoft 365 Apps / Office (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.