Visio 5.0 or earlier Binary Drawings, Templates and Stencils
| Registry value | visio50andearlierfiles |
| Group Policy | Visio 5.0 or earlier Binary Drawings, Templates and Stencils |
| German version | Binäre Visio 5.0-Zeichnungen, -Vorlagen und -Schablonen (oder früher) |
| Intune settings catalog | Visio 5.0 or earlier Binary Drawings, Templates and Stencils (User) |
| Scope | User · HKCU |
| ADMX | visio16.admx · L_Visio50AndEarlierFiles |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\visio\security\fileblock | |
| visio50andearlierfiles | 0 = Do not block · 2 = Open/Save blocked |
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\visio\security\fileblock"
foreach ($name in @('visio50andearlierfiles')) {
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\visio\security\fileblock"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'visio50andearlierfiles' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null # options: 0 = Do not block, 2 = Open/Save blocked
'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\visio\security\fileblock" Remove-ItemProperty -Path $key -Name 'visio50andearlierfiles' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Visio 5.0 or earlier Binary Drawings, Templates and Stencils (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/visio16v2~Policy~L_MicrosoftVisio~L_VisioOptions~L_Security~L_TrustCenter~L_FileBlockSettings/L_Visio50AndEarlierFiles |
| Data type | String |
| 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 Visio 5.0 or earlier Binary Drawings, Templates and Stencils. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting allows you to determine whether users can open or save Visio files with the format specified by the title of this policy setting.
If you enable this policy setting, you can specify whether users can open or save files.
The options that can be selected are below. Note: Not all options may be available for this policy setting.
- Do not block: The file type will not be blocked.
- Save blocked: Saving of the file type will be blocked.
- Open/Save blocked: Both opening and saving of the file type will be blocked.
If you disable or do not configure this policy setting, the file type will be blocked.
Same category: Microsoft Visio 2016 › Visio Options › Security › Trust Center › File Block Settings
- Visio 2003-2010 Binary Drawings, Templates and Stencilsvisio2003files
- Visio 2000-2002 Binary Drawings, Templates and Stencilsvisio2000files
All policies in this category · All 98 policies of visio16.admx