Office Admin Explorer

Language for file conversion

Registry value
fileconversionmode
Group PolicyLanguage for file conversion
German versionSprache für Dateikonvertierung
Intune settings catalogLanguage for file conversion (User)
ScopeUser · HKCU
ADMXvisio16.admx · L_languageforfileconversion4
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Visio 2016\Visio Options\Advanced\Save/Open
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Visio 2016\Visio-Optionen\Erweitert\Speichern/Öffnen

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\visio\application
fileconversionmode0 = Let Visio decide language · 1 = Prompt for language · 2 = Use the following language
fileconversionlanguagetext

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\application"
foreach ($name in @('fileconversionmode', 'fileconversionlanguage')) {
    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\application"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'fileconversionmode' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # options: 0 = Let Visio decide language, 1 = Prompt for language, 2 = Use the following language
    New-ItemProperty -Path $key -Name 'fileconversionlanguage' -PropertyType String -Value '<value>' -Force -ErrorAction Stop | Out-Null   # your value
    '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\application"
Remove-ItemProperty -Path $key -Name 'fileconversionmode', 'fileconversionlanguage' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Language for file conversion (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_Advanced~L_SaveOpen/L_languageforfileconversion4
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 Language for file conversion. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting specifies how Visio determines what language to use when converting to or from an earlier version of Visio.

If you enable this policy setting, you may select from one of these options:

- Let Visio decide language

- Prompt for language

- Use the following language: You must specify the numeric Microsoft Locale ID (LCID) for that language.

If you disable or do not configure this policy setting, Visio decides what language to use.

Same category: Microsoft Visio 2016 › Visio Options › Advanced › Save/Open

All policies in this category · All 98 policies of visio16.admx