Office Admin Explorer

Check OLE objects

Registry value
checkofficeole
Group PolicyCheck OLE objects
German versionOLE-Objekte überprüfen
Intune settings catalogCheck OLE objects (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_CheckOLEObjects
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Security Settings
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016\Sicherheitseinstellungen

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\common\com categories
checkofficeole0 = Do not check · 1 = Override IE kill bit list · 2 = Strict allow list

Not configured = the value does not exist – the application default applies and users may change the setting.

PowerShell

Check the current value (read-only)

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\common\com categories"
foreach ($name in @('checkofficeole')) {
    try   { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
    catch { '{0}: not configured' -f $name }
}

Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.

Enable

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\16.0\common\com categories"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'checkofficeole' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # options: 0 = Do not check, 1 = Override IE kill bit list, 2 = Strict allow list
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Reset to Not configured
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\common\com categories"
Remove-ItemProperty -Path $key -Name 'checkofficeole' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Check OLE objects (User)

Settings catalog → Add settings → search for the name above.

Intune Settings Catalog Viewer ↗

Alternative: custom profile (OMA-URI)
OMA-URI
./User/Vendor/MSFT/Policy/Config/office16v2~Policy~L_MicrosoftOfficeSystem~L_SecuritySettings/L_CheckOLEObjects
Data typeString
Value<enabled/> · <disabled/>

This policy has options: add one <data id="…" value="…"/> per element after <enabled/>. The element IDs are in the ADMX file.

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Check OLE objects. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting determines whether Office checks that an OLE object is properly categorized before loading it.

If you enable this policy setting, you can select one of the following options:

- Do not check: Office loads OLE objects without checking if they are properly categorized.

- Override IE kill bit list: Office uses the category list to override IE kill bit checks. (This is also the default behavior for this policy setting).

- Strict allow list: Office only loads properly categorized OLE objects.

If you disable or do not configure this policy setting, Office uses the category list to override IE kill bit checks.

Same category: Microsoft Office 2016 › Security Settings

All policies in this category · All 945 policies of office16.admx