I’ve seemingly read just about everything about making a windows 10 unattend file and skipping the OOBE however OOBE is STILL running! Specifically it’s asking for keyboard layout, additional keyboard, account, security questions, and the different services related to your choices near the end. My unattend file is applying some settings but not the one i care most about, skipping the OOBE. I feel like im missing something simple here… Im using SIM 10.0.17134.1, toolkit 6.3.8450.1000, and WDS.
](http://www.w3.org/2001/XMLSchema-instance%22>) ; en-US en-US en-US en-US en-US ](http://www.w3.org/2001/XMLSchema-instance%22>) ; OnError 1 500 Primary true 2 Primary true NTFS System 1 1 NTFS Windows C 2 2 0 true 0 2 xxxxxx-xxxxx-xxxxx-xxxxxx-xxxxx true MCDC mcdc.local xxxxxx wdsacc ](http://www.w3.org/2001/XMLSchema-instance%22>) ; en-US en-US en-US en-US ](http://www.w3.org/2001/XMLSchema-instance%22>) ; true true true true 1 TQBjAGQAYwBhAGQAbQAxAG4AUABhAHMAcwB3AG8AcgBkAA== false Local admin admin Administrators admin Answer from johnburmeister6262 on community.spiceworks.comI work with new computers all the time getting them ready for specific environments... and it is really tedious going through OOBE every time... I know you can hit shift F10 and get a command prompt and do things... and you can run powershell from that command prompt... are there scripts I can run there to answer the OOBE stuff so i can skip it? or a way to apply an unattend.xml file there from the prompts?
Videos
I’ve seemingly read just about everything about making a windows 10 unattend file and skipping the OOBE however OOBE is STILL running! Specifically it’s asking for keyboard layout, additional keyboard, account, security questions, and the different services related to your choices near the end. My unattend file is applying some settings but not the one i care most about, skipping the OOBE. I feel like im missing something simple here… Im using SIM 10.0.17134.1, toolkit 6.3.8450.1000, and WDS.
](http://www.w3.org/2001/XMLSchema-instance%22>) ; en-US en-US en-US en-US en-US ](http://www.w3.org/2001/XMLSchema-instance%22>) ; OnError 1 500 Primary true 2 Primary true NTFS System 1 1 NTFS Windows C 2 2 0 true 0 2 xxxxxx-xxxxx-xxxxx-xxxxxx-xxxxx true MCDC mcdc.local xxxxxx wdsacc ](http://www.w3.org/2001/XMLSchema-instance%22>) ; en-US en-US en-US en-US ](http://www.w3.org/2001/XMLSchema-instance%22>) ; true true true true 1 TQBjAGQAYwBhAGQAbQAxAG4AUABhAHMAcwB3AG8AcgBkAA== false Local admin admin Administrators adminYou could try these files?
Hi, My WDS unattended.xml configuration file: https://pastebin.com/TMHHh6rf Some screenshots of the steps i want to skip: [Album] W10 1809 WDS unattended configuration - cannot skip oobe [W10 1809 WDS unattended configuration - cannot skip oobe] Some other guys seems to have the same problem: And no, i dont want to use MDT (…
Hey not sure if anyone knows this yet or not but me and the boys at our precinct have been doing this for a while might help yalls workflow. Posted a video but put the steps down below.
Click through until you get to the MS sign on page then click one step back.
SHIFT + F10 or Function +SHIFT + F10 to open cmd
Type Start ms-windows-store: press enter
Go as if you are logging into a account then type user and any password can be a single letter. Once it errors out do not click next just exit.
Go back to OOBE and click through as if you were continuing it should error and you can click skip this step.
PARTY BECAUSE YOU BEAT MICROSOFT
A lot of people have been posting here about different ways to get around WiFi setup & s-mode. I have an easy and reliable way to bypass both.
For standard windows bypassnro is the best way to bypass the WiFi. By pressing shift + f10 or fn + shift + f10, this will open command prompt which you can then type in OOBE\BYPASSNRO with no spaces between the backslash. Additionally you CANNOT connect the computer to WiFi first, this will mess it up. If you do happen to do this I find the easiest way to fix it is by opening control panel by typing control in cmd prompt and opening device manager to disable the WiFi module temporarily. Then bypassnro will work 100% of the time.
As for s mode
This works also 100% of the time (for now)
MRI 6.0+ X64 REQUIRED
You will use Regedit to edit the registry but in mri pe instead of windows. Starting off while still in OOBE. First disable secure boot, this will allow the computer to boot to usb devices. MRI WILL NOT BOOT IF YOU DO NOT TURN OFF SECURE BOOT. Then, since the system is still in OOBE and has not been set up bitlocker will also not be active yet which will allow mri to bind. And that is the next step, Bind to Windows though MRI PE. Then open regedit either through run or in the mri toolkit tab. Then locate HKEY_Local_Machine\System(RemoteOS)\CurrentControlSet\Control\CI\Policy Change the value of SkuPolicyRequired to 0
This is very similar to the old way but the biggest difference is in MRI PE the “normal” looking registry keys are MRI’s Registry. The windows registry we care about will say (REMOTE OS) next to the System registry directory.
This saves time vs the old way by only requiring secure boot to be disabled and you can do everything in mri pe without needing to disable driver signature enforcement or going into windows recovery.
TLDR
Disable secure boot
Boot to mri pe and bind to windows
Do registry magic in regedit using the RemoteOS registry keys (see above key)
Re enable secure boot.
Profit
Once you disable secure boot you can use OOBE\BYPASSNRO to bypass the WiFi screen like normal.
This has never failed me, do not listen to people who say bypassnro does not work. It does 100% work still as of 6/2/24.
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.