Office Admin Explorer

Disable VSTO 2003 and 2005 document-level customizations

Registry value
vstolegacy1or2disable
Group PolicyDisable VSTO 2003 and 2005 document-level customizations
German versionAnpassungen von VSTO 2003 und 2005 auf Dokumentebene deaktivieren
ScopeUser · HKCU
ADMXoffice16.admx · L_DisableVSTOLegacy1Or2
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\vsto
vstolegacy1or2disableEnabled = 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\vsto"
foreach ($name in @('vstolegacy1or2disable')) {
    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\vsto"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'vstolegacy1or2disable' -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\vsto"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'vstolegacy1or2disable' -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\vsto"
Remove-ItemProperty -Path $key -Name 'vstolegacy1or2disable' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Not found in the current settings catalog export. Search the catalog for Disable VSTO 2003 and 2005 document-level customizations (Microsoft Office 2016 › Security Settings).

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Disable VSTO 2003 and 2005 document-level customizations. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting allows you to configure the load behavior of Visual Studio Tools for Office (VSTO) 2003 and 2005 document-level customizations.

If you enable this policy setting, VSTO 2003 and 2005 document-level customizations will not be loaded.

If you disable or do not configure this policy setting, VSTO 2003 and 2005 document-level customizations will remain enabled.

Same category: Microsoft Office 2016 › Security Settings

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