This is a bug in the windows 11 ARM build, To fix that you need to do as follow
- Press 'fn+shift+f10'
- Press 'option+tab'
- Then you will see a UAC window, move to that window by pressing 'option+tab' and then press 'yes' button
Then CMD will be opened
I'm at the network selection screen in my setup and for some reason, Shift-F10 appears to do nothing. Did they patch that out?
This is a bug in the windows 11 ARM build, To fix that you need to do as follow
- Press 'fn+shift+f10'
- Press 'option+tab'
- Then you will see a UAC window, move to that window by pressing 'option+tab' and then press 'yes' button
Then CMD will be opened
Hi Robert,
Just checking in with you, were you able to use that shortcut to get into Command Prompt?
If you still cannot get into Command Prompt, when you boot form the USB, select 'Repair This Compute, and Command Prompt should be available from the Recovery Environment.
Videos
You can overcome this limitation by also passing in Fn, so in your case you'd press Shift+Fn+F10.
I tried all possible all possible combination of Shift+Fn+F10, but nothing worked.
Then i clicked on that Accessibility icon and enabled on-screen keyboard and then selected Shift+Fn+F10 again and it opened the cmd prompt this time, but it does not come into focus, to do that you can then use option+tab on your physical keyboard.
So basically with the MediaCreationTool I could re-install the windows, after I put the key it detected the correct windows version.
I hit the same problem, however turning off the ethernet cable I was able to bypass the screens.
Thanks once again!
I still don't understand why MS is forcing the connection to internet.
Hi there,
This is Tamal trying to help you with the issue.
Yes, you can go you with the fresh installation. You may not need reactivate windows upon installation as the process is automated. You can still use your windows 7 key during installation or proceed with choosing I don't have a key option.
I think your reset was not complete or might be initial installation was done as a domain joined computer. You have tried all the good things and those should have worked, but as that is not happening better go with the fresh installation after creating an installation media.
How do I set up a local account now?
Latest and fastest way I found to bypass Windows 11 OOBE, no need to run ipconfig /release or setup a Microsoft account.
EDIT:
Even with the latest Windows 11 updates THIS METHOD IS STILL THE BEST!!
Watch this in action: https://youtu.be/MXrYXH-ueIQ
Use a command prompt to create a local account during OOBE and then skip it completely:
-
SHIFT + F10 (or SHIFT + FN + F10 on some Dell PC's)
-
net.exe user 'username' 'password' /add *I recommend entering a password but it is optional*
-
net.exe localgroup Administrators 'username' /add
-
cd oobe
-
msoobe.exe && shutdown.exe -r
This feature is currently only available to those who add LCU (Latest Cumulative Update) to their ISO.
This was first discovered in Insider Preview Build 27881 (Canary Channel), and at the time, it was thought to be a bug. However, it's now present in Public Release build 26100 (also known as 24H2), and I believe it's not a bug but a feature.