Hi
Thanks for your reply.
I'm glad your question has been resolved, and if you encounter any new questions in the future, feel free to open a new thread to ask questions.
Thank you for your support of Microsoft products.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all,
I have been working on creating a customised windows 11 setup media at work - to save time imaging and getting the computers on to InTune. To that end, I have already done several customisations but the one that eludes me is to trigger a batch file/cmd script to load when the OOBE Language selection screen loads up. When I set an asynchronous or synchronous command for OOBE in the autounattend.xml, it loads about 5-10secs before the OOBE screen comes up and thus prevents parts of the script from running correctly (Telling me commands are not recognised, etc when they work fine in OOBE). Does anyone know of a way I can do what I am trying to do?
Thanks in advance.
Kind regards,
Danny
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi
Thanks for your reply.
I'm glad your question has been resolved, and if you encounter any new questions in the future, feel free to open a new thread to ask questions.
Thank you for your support of Microsoft products.
My final solution was to add the scripts into the install image so that we can fire up command prompt using shift+F10 at first page of OOBE and typing the word "Intune" to run a custom script that calls the relevant commands. Works a treat. Also managed to incorporate a pre-usb boot setup script to clean disk 0 using diskpart before the "install location" screen appears. Also managed to reduce the input on 1st stage setup to 1 keypress - confirming where you want it installing 👍👍
Hi
Welcome to Microsoft community.
I understand that you are trying to run a batch file or cmd script during the Windows 11 setup process, specifically when the OOBE (Out-Of-Box Experience) Language selection screen comes up. However, it seems like your script is running slightly before the OOBE screen, causing some commands to not be recognized.
This is a complex issue that might require more in-depth knowledge of your exact setup and script. However, you could consider the following:
timeout /t <seconds> command to add a delay.%WINDIR%\Setup\Scripts\SetupComplete.cmdPlease let me know if you need any further assistance. Thank you.
Best regards
Derrick Qian | Microsoft Community Support Specialist