Forum Discussion
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?
3 Replies
hollyB: as far as I know the OOBE choice is stored for the user profile that gets created, while the logon screen reads the system (welcome screen) settings, which are separate. That would explain why the layout looks right through first sign-in and then reverts at the logon screen after a reboot, and it doesn't need a policy that locks the keyboard.
Worth testing on one device: sign in as a user who has the Swedish layout set, then run Copy-UserInternationalSettingsToSystem -WelcomeScreen $true -NewUser $true from an elevated PowerShell (it's in the International module on Windows 11). It copies that user's region and keyboard settings to the logon screen and to new accounts, and users can still change their own layout afterwards.
If that fixes it, you could run the same command as a one-time script after Autopilot. I'd confirm the parameter names on your Windows build first.
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.
