Correct keyboard setting
| Registry value | fcorrectkeyboard_64_1 |
| Group Policy | Correct keyboard setting |
| German version | Tastatureinstellung korrigieren |
| Intune settings catalog | Correct keyboard setting (User) |
| Scope | User · HKCU |
| ADMX | word16.admx · L_Correctkeyboardsetting |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\word\options\assist | |
| fcorrectkeyboard_64_1 | Enabled = 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\16.0\word\options\assist"
foreach ($name in @('fcorrectkeyboard_64_1')) {
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\word\options\assist"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'fcorrectkeyboard_64_1' -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\16.0\word\options\assist"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'fcorrectkeyboard_64_1' -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\16.0\word\options\assist" Remove-ItemProperty -Path $key -Name 'fcorrectkeyboard_64_1' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Correct keyboard setting (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/word16v2~Policy~L_MicrosoftOfficeWord~L_WordOptions~L_Proofing~L_AutoCorrect/L_Correctkeyboardsetting |
| Data type | String |
| Value | <enabled/> · <disabled/> |
Cloud Policy
Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Correct keyboard setting. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting allows you to set the "Correct keyboard setting" option in Word Options | Proofing | "AutoCorrect Options..." | AutoCorrect.
If you enable this policy setting, "Correct keyboard setting" will be set.
If you disable or do not configure this policy setting, "Correct keyboard setting" will not be set.
Same category: Microsoft Word 2016 › Word Options › Proofing › AutoCorrect
- Correct TWo INitial CApitalsftwoinitialcaps_24_1
- Capitalize first letter of sentencefinitialcap_32_1
- Capitalize names of daysfcapdaynames_48_1
- Correct accidental usage of cAPS LOCK keyfcapslock_40_1
- Replace text as you typefcorrecttyping_16_1
All policies in this category · All 295 policies of word16.admx