Fix Windows Autopilot Keyboard Language Not Updating During OOBE

If Windows Autopilot is provisioning correctly but the keyboard language still lands on the wrong layout after OOBE, check the Autopilot keyboard language known issue before you start rebuilding the profile or blaming the image.

Microsoft documents a specific bug here: the Autopilot profile setting that enables automatic keyboard configuration based on the Language (Region) setting might fail to apply during provisioning. In practice, that means the deployment can complete while the keyboard language stays out of sync with the region you selected.

The admin fix is not a custom script workaround first. The documented remediation is to move to a build that contains the fix, specifically KB5072033 or later.

Quick fix checklist

1. Confirm the device is actually using a Windows Autopilot profile with automatic keyboard configuration enabled.
2. Check the selected Language (Region) in the deployment profile.
3. Verify whether the device finished OOBE with the wrong keyboard layout even though provisioning otherwise succeeded.
4. Install KB5072033 or a later update on affected devices.
5. Retest on one pilot machine before widening the rollout.
6. If the issue appears across a batch, treat it as an OS-level provisioning bug, not a per-device image defect.

Root cause

Microsoft’s known-issues page says the keyboard language setting can fail because of a Windows Autopilot profile setting problem, not because the keyboard pack is missing.

The exact failure pattern is:

• you configure automatic keyboard language based on Language (Region),
• provisioning runs,
• but the final keyboard language does not update correctly.

That makes this look like a locale policy issue or an image customization miss, when it is actually a provisioning bug in the Autopilot flow.

Where to check

1. Windows Autopilot profile

Open the Autopilot profile and confirm:

• Language (Region) is set intentionally
• automatic keyboard setup is enabled
• the affected devices were assigned the profile you think they were

2. Device-side confirmation

On the affected PC, verify the final state after OOBE:

• the UI language may be correct
• the keyboard layout may be wrong
• the mismatch often shows up right after first sign-in

3. Microsoft Learn known issue

Microsoft lists this under Windows Autopilot known issues as:

Setting up keyboard automatically doesn't accurately update keyboard language

That wording matters because it distinguishes the problem from generic region or language pack deployment failures.

PowerShell checks

Use PowerShell after enrollment to confirm what the device thinks the active input and locale settings are:

Get-WinUserLanguageList
Get-Culture
Get-WinSystemLocale

If the region and keyboard state disagree, document the mismatch before you make rollout changes.

For a quick input-method snapshot, you can also review the current keyboard layout in the user session and compare it with the deployment profile’s Language (Region) setting.

Why this hits admins hard

This issue usually gets escalated as:

• “Autopilot finished, but the keyboard is wrong”
• “Our multilingual image is broken”
• “The language pack deployed, but the layout didn’t stick”

Those are reasonable guesses, but they are the wrong first branch if the tenant is already on an affected build. Microsoft says the behavior is tied to the Autopilot keyboard automation path itself.

Prevention

• Keep Autopilot devices on current cumulative updates before large regional rollouts.
• Pilot language and keyboard changes on one region first.
• Compare the Autopilot profile language configuration with the post-enrollment keyboard state on every pilot device.
• Treat layout mismatches as an OS provisioning issue until the KB floor is confirmed.

Verification after remediation

After applying KB5072033 or later, rerun Autopilot on a test device and verify:

• the device completes OOBE normally
• the keyboard layout matches the selected language/region
• the issue string no longer reproduces

If you still see the mismatch after the update, collect the Autopilot profile settings and the device’s language list before assuming the OS fix failed.