W11 24h2 Ctrl+Shift+F3 audit mode doesn't work?
Posted by egosumumbravir@reddit | sysadmin | View on Reddit | 16 comments
Well it's time to roll the custom W11 images and get started on user testing for a September deployment.
Nah, it's fine, it's a small site so we'll be good. That's not the weird thing.
Generate current ISO images with uupdump. Load image into VMWare Workstation and install to create master images. So far so good. Same way I've been doing this since WinXP days (well, except for the uupdump source but that's be the default since 10 was young).
Reach the OOBE beginning, Press Ctrl+Shift+F3 , expecting to get a reboot and audit mode ... nothing.
Try Ctrl+Shift+F3 again, still nothing.
OK so lets work through the OOBE and trigger audit mode from the desktop which does work. Weird.
Wipe the VM, reinstall and it's the same thing. Install a different edition and it's the same thing.
Anyone encountered this before?
lordmycal@reddit
Why are you still creating master images? This is old school thinking.
Automated installs are the way to go (e.g. Autopilot). That way the next time some important program needs updating or there is a new build of windows you don't have to reinvent the wheel; you just replace the installer and new machines or machines that need to be reset get the latest versions of everything they are supposed to.
egosumumbravir@reddit (OP)
That's me to a tee. Been rocking this process since the XP days since it fits my use case so well.
lordmycal@reddit
It's a big waste of your time; You have to keep updating the image and recapturing it, whereas you should already have a process for remotely and automatically installing needed software. Just automate installing the OS and let your software install as needed.
GloveLove21@reddit
Are you using on prem ad? Many of us are. Also, how do you deal with preloaded bloatware?
egosumumbravir@reddit (OP)
Which won't work as a contingency when users and devices are offline remote. Like I said, this method fits this particular use case so well.
confushedtechie@reddit
Automated installs donโt work for every scenario especially in engineering and healthcare. Depends on the workload
Ready-Plankton-3709@reddit
I feel like this will be related to them trying to block the "oobe\bypassnro" stuff, I don't think you can escape oobe now with 24H2 and above.
egosumumbravir@reddit (OP)
That's what I wonder. Seems like a brain dead moronic move for scale deployments.
trueppp@reddit
Just use an answer file?
egosumumbravir@reddit (OP)
That'll be coming later. First I need to get in.
trueppp@reddit
unattend.xml or a ppkg let's you bypass OOBE quite easily...
jamesaepp@reddit
I seem to recall people reporting this issue with only one of the newer ISOs, so while it is very annoying, hanlon's razor applies.
egosumumbravir@reddit (OP)
Remind me again how many generations it took to get the little button to left align the start menu? ๐ค
Mr_ToDo@reddit
Alright so I both looked around the net and did my own test
Testing was done with a bog standard ISO from microsoft in Hyper-V. In that everything worked as needed
Looking around the net I found other people with the same issue. It's possible that it only happens with the latest cumulative update rolled into it and only on first boot(as in you reboot and it should be fine)
https://www.reddit.com/r/Windows11/comments/1lls9sz/261004484_pressing_shift_f10_during_oobe_does_not/
Odd behavior but I had been assuming in the start that something in their process was just flagging that to not work. I'm pretty sure you can do that in the unattended rules but that doesn't explain how it worked for you when played with it. At least with a bug in the patch it makes some degree of sense on where it came from
I'd try and manually build an ISO that's more current then what's on their site but I don't want to. Sorry
egosumumbravir@reddit (OP)
Update #2: more screwing around. CTRL-SHIFT-F10 doesn't work. WIN-R doesn't work, SHIFT-F10 doesn't work.
Hit the reset button, let the OOBE startup again.
CTRL-SHIFT-F10 works now!
egosumumbravir@reddit (OP)
Update: just for shits and giggles, I dug out an older uupdump image of the same edition, generated November 2024, still 24h2. Wiped the VM, installed this one.
Ctrl+Shift+F3 works exactly as expected ๐