Office Admin Explorer

Configure invalid hashing algorithm

Registry value
invalidhashalg
Group PolicyConfigure invalid hashing algorithm
German versionUngültigen Hashalgorithmus konfigurieren
Intune settings catalogConfigure invalid hashing algorithm (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_SelectDigitalSignatureInvalidHashingAlgorithm
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Security Settings\Digital Signatures
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016\Sicherheitseinstellungen\Digitale Signaturen

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\common\signatures
invalidhashalgmd5 = MD5 · sha1 = SHA1 · sha256 = SHA256 · sha384 = SHA384

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\signatures"
foreach ($name in @('invalidhashalg')) {
    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\signatures"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'invalidhashalg' -PropertyType String -Value 'md5' -Force -ErrorAction Stop | Out-Null   # options: md5 = MD5, sha1 = SHA1, sha256 = SHA256, sha384 = SHA384
    '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\signatures"
Remove-ItemProperty -Path $key -Name 'invalidhashalg' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Configure invalid hashing algorithm (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_DigSig/L_SelectDigitalSignatureInvalidHashingAlgorithm
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 Configure invalid hashing algorithm. 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 whether Office displays a digital signature as invalid when it contains specific hash algorithms.

If you enable this policy setting, you can specify the weakest hash algorithm that Office treats as invalid. If you enable this policy setting, you can specify any of the following algorithms:

- MD5

- SHA1

- SHA256

- SHA384

If you don’t configure this policy setting, Office won’t treat digital signatures as invalid because of the hashing algorithm.

For example, if you set MD5 as the invalid hashing algorithm Office treats MD5 signatures as invalid.

Same category: Microsoft Office 2016 › Security Settings › Digital Signatures

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