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?

I got a new computer with Windows 11. I want to use a local account on it. When it gets to the "Let's connect you to a network" screen, I can't bypass it. I've also tried the Shift + F10 key, I tried to launch command prompt, etc.

Is there another trick or am I stuck?

I got a new computer with Windows 11. I want to use a local account on it. When it gets to the "Let's connect you to a network" screen, I can't bypass it. I've also tried the Shift + F10 key, I tried to launch command prompt, etc.

Is there another trick or am I stuck?

Most people usually use this to open cmd in oobe, and then skip the networking requirements of windows 11.I'm using a laptop and this shortcut doesn't seem to work, will it work if I use an external keyboard?

I think there is another possibility that this shortcut key is invalid in the 22h2 version.

Am I doing something wrong or did windows 11 just make changes to the hotkey. I have tried searching myself but I cant find any explanation as to why this happens.

Trying to create a local account and I cannot access the command prompt during setup. Tried the usual command keys and nothing works. This is not an s mode computer. It has a core i5 processor. The brand is a Dell Inspiron laptop and the keyboard is Canadian multilingual standard. Somebody please help.

I have to set up a lot of machines daily and its really annoying not being able to set up a local account as the first user.

I will try and be as succinct, but detailed as possible.

We are using SCCM OSD to deploy a very basic Windows 11 OS so that we can then use Autopilot. All the TS does is format the drive, lay down the OS, install a driver pack, install the SCCM client (which is required) and creates a post TS scheduled task that runs on first boot. The scheduled task uninstalls the SCCM client.

When the target Win11 OS is running in OOBE we need to get to a command prompt, but shift F10 does not work.

I have proved that shift F10 works when the Win11 OS wim is deployed via a standalone USB (this is not an SCCM standalone build) So it's not the OS wim.

I have proved that shift f10 works if I install the Win11 OS via TS but exclude the SCCM client. Yes, the TS does fail, (80004005) but at this point all I am more concerned about proving that the SCCM client is the contributing factor. Which it appears to be.

I have tried injecting a custom unattend.xml with this config in the OOBESystem phase, but that didn't help either:

<DisableCMD>false</DisableCMD>

I do not believe that WinPE boot image / F8 / Command Support is relevant in this context.

I've checked the CCMSetup switches and I don't see anything pertaining to Shift F10 / cmd / command window enablement.

I now seem to be stuck with having to install the very thing that is causing my issue, and so I would appreciate your thoughts on how I get this working.

Thanks

Background

I have been hard at work redesigning our SOE for Windows 11 - cleaning up a lot of tech debt from an Intune/Autopilot environment that was haphazardly setup 5 years ago & then never maintained.
While I was about to lock in our SOE, I found that pressing Shift+F10 during the OOBE (Edit: Technician Setup, Device Preperation) was now giving me a UAC prompt for a Username & Password - quite curious. I have been using 24h2 since I started this work in March, and never experienced this before. Something had changed.

Troubleshooting

At first I thought the issue was with LAPS - as I had recently finished configuring it. I thought the policy was interfering with the default administrator account.
But opening a non-elevated command prompt (Win+R > CMD) and running "net user" didn't show the WLAPSAdmin account as present. HMMM.

Through the course of this, I found out that Autopilot uses the "DefaultUser0" account, which is a member of the Administrators Group. I couldn't find any online posts that talked about default credentials for this account - and simply entering the username with no password at the UAC prompt was unsuccessful.
I gave up on that, which fortunately lead me to...

The Solution

I started googling the specific message in the UAC prompt ("user oobe create elevated object server") and stumbled across a 6 year old blog post by Gerry Hampson. That led me down a rabbit hole of trying to track down the setting he mentioned ("Local Policies Security Options > Administrator elevation prompt behaviour") - which was not familiar to me & I have spent the last 4 months neck deep in every facet of Intune configurations.
Diving into our environment, I found that the security team had configured the option while they were troubleshooting Security Baselines - and instead of targeting it at a test group they used the general W11 devices group (grrr..). The offending setting was set to 'Prompt for credentials on the secure desktop'
Modifying the setting as follows fixed it right up:

This was a quite obscure one for a change - Gerry's blog was basically the only thing even talking about it, I found no reddit threads or MS posts that seemed even tangentially related - so I'm hoping that this post helps to widen the net for other people in the same boat as me :)

Hi all. My laptop is a Lenovo Ideapad S145.

Unfortunatelly it does not come with a dedicated windows menu key. Instead of right-clickling I used to press "Shift+F10" to bring a context menu.

The problem is that it doesn't work anymore.

Anyone is having the same issues? Is there any known workaround to solve this?

Hi. So Ive been doing a windows reinstall and I deleted all my old partitions in order to delete all malwarenin my old system. Apparently that also deleted my wifi drivers and I can't connect to any network until I reinstall them. The thing is, I can't do anything to bypass the connect you to network screen. It won't let me do anything and shift - f10 doesn't seem to work. Anyone knows how to solve this? Thanks in advance.