Shift+F10 not working in new Windwos builds

[Vladimir-Bosnjak]

According to the Atlas docs, during setup you can press Shift+F10 to open CMD and bypass the Microsoft account requirement.

On a recent Windows 11 Pro 24H2 install (Beelink GTi13 Mini-PC), that no longer works. The installer refuses to continue without internet and a Microsoft account.

Steps I tried:

Moved on to a later point during setup, then Shift_F10 worked again, but the commands below sill failed.
Shift+F10 → OOBE\BYPASSNRO → no effect.
Shift+F10 → start ms-cxh:localonly → also didn’t work.
Disabled internet (pulled Ethernet, disabled Wi-Fi) → setup still blocks progress.

Questions:
Is signing in with a Microsoft account first and switching later to a local account safe for Atlas OS installation? I could remove account-related telemetry later?
Are there updated methods for bypassing the Microsoft account requirement on 24H2?

[Ast3risk-ops]

On some devices you need to hold Fn to press the function keys. Double check you did that first.

[Vladimir-Bosnjak]

The Fn modifier only matters if your keyboard is configured to prioritize media keys over F-keys. If Shift+F10 opened a command prompt later in OOBE, then the keypress worked, so the issue is not Fn.

[Ast3risk-ops]

The Fn modifier only matters if your keyboard is configured to prioritize media keys over F-keys. If Shift+F10 opened a command prompt later in OOBE, then the keypress worked, so the issue is not Fn.

If you have windows pro, choose another sign in option (under the email input box) then click Domain Join.

[Vladimir-Bosnjak]

Didn't know the Pro version had Domain join option. First time using Pro. I'll try that.
Edit: Doman option has been removed.

However... solved it nevertheless:
When I first installed Windows 11, I tried using Shift+F10 during OOBE, but that was too late. You have to use it right after selecting the keyboard layout. That is the only point where the localonly command still works.

Shift+F10 can still be used later in OOBE, but only to launch Task Manager from the console. You then have to kill the Microsoft Account app. The setup will return to the language and keyboard layout screen, giving you another chance to run the command at the correct moment.

So my earlier assumption was wrong: Shift+F10 does still work, but the start ms-cxh:localonly command only functions immediately after setting the keyboard layout.

Thank you so much for your help. Most kind of you.