Office Admin Explorer

Disable Smart Document's use of manifests

Registry value
neverloadmanifests
Group PolicyDisable Smart Document's use of manifests
German versionManifestverwendung durch SmartDocuments deaktivieren
Intune settings catalogDisable Smart Document's use of manifests (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_DisableSmartDocumentsuseofmanifests
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Smart Documents (Word, Excel)
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016\SmartDocuments (Word, Excel)

Registry

ValueData
HKCU\Software\policies\microsoft\office\common\smart tag
neverloadmanifestsEnabled = 1 · Disabled = 0

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\common\smart tag"
foreach ($name in @('neverloadmanifests')) {
    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\common\smart tag"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'neverloadmanifests' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null   # Enabled
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Disable
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\common\smart tag"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'neverloadmanifests' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # Disabled
    '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\common\smart tag"
Remove-ItemProperty -Path $key -Name 'neverloadmanifests' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Disable Smart Document's use of manifests (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_SmartDocumentsWordExcel/L_DisableSmartDocumentsuseofmanifests
Data typeString
Value<enabled/> · <disabled/>

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Disable Smart Document's use of manifests. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting controls whether Office 2016 applications can load an XML expansion pack manifest file with a Smart Document.

An XML expansion pack is the group of files that constitutes a Smart Document in Excel and Word. You package one or more components that provide the logic needed for a Smart Document by using an XML expansion pack. These components can include any type of file, including XML schemas, Extensible Stylesheet Language Transforms (XSLTs), dynamic-link libraries (DLLs), and image files, as well as additional XML files, HTML files, Word files, Excel files, and text files.

The key component to building an XML expansion pack is creating an XML expansion pack manifest file. By creating this file, you specify the locations of all files that make up the XML expansion pack, as well as information that instructs Office 2016 how to set up the files for your Smart Document. The XML expansion pack can also contain information about how to set up some files, such as how to install and register a COM object required by the XML expansion pack.

If you enable this policy setting, Office 2016 applications cannot load XML expansion packs with Smart Documents.

If you disable or do not configure this policy setting, Office 2016 applications can load an XML expansion pack manifest file with a Smart Document.

Same category: Microsoft Office 2016 › Smart Documents (Word, Excel)

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