Forum Discussion

hollyB's avatar
hollyB
Copper Contributor
Sep 03, 2026

Keyboard reverting on reboot

I'm having an issue with the keyboard reverting after OOBE.

I'm using an English (UK) Windows 11 25H2 base image (deliberately — I want English display language, with Swedish keyboard/regional settings applied without needing to install a Swedish language pack). Deployment is native Windows Autopilot, no third-party tooling involved.

Autopilot deployment profile: Language (Region) = Swedish (Sweden), Automatically configure keyboard = No.

During OOBE, I manually select Swedish keyboard, and it's correctly applied — it's still Swedish through the first user logon. But after rebooting the keyboard silently reverts to English (UK). This is regardless of if I run pre-provisioning or user-driven.

Is this a known/new behaviour, and how can I fix it?

2 Replies

  • You need English display language with Swedish input keyboard, but the OOBE choice is replaced after the first reboot. The Autopilot profile’s Language (Region) and Automatically configure keyboard options control the OOBE flow; they do not prove a manually chosen per-user input layout will remain enforced after enrollment. First, after reboot, capture Settings > Time & language > Language & region, installed keyboards, region, and Intune configuration profile status. Compare effective policies and scripts for a working and failing device, especially regional, language, shared-device, or remediation settings. Do not add the Swedish language pack unless policy permits it; confirm whether the desired layout is available without it. Use a small test assignment to deploy the approved keyboard setting through Intune rather than relying on OOBE selection, then reboot twice. If no policy is applying, collect Autopilot and MDM diagnostic logs and raise it with Microsoft support as an enrollment-state issue.

    • hollyB's avatar
      hollyB
      Copper Contributor

      Thanks for this Jamony​ . But can I first ask: should the keyboard chosen during OOBE be set as default and used after reboot at logon screen? If so, this is broken. Also I do not want to set the keyboard via policy since users need to be able to change the keyboard.