Sysprep problem with 24H2

Hi everyone!

Some of you may know me fro the tools I make to created recovery partition for Windows 7/8/10/11.

24H2 make me pull my hair!

I use a CMD batch file to do a lots of job, before AND after Sysprep.

Problem is, with 24H2, Sysprep is killing all instance of CMD.EXE, witch kill my script.

Anyone one as an idea on how to prevent that?

The only other solution for me would be to have to run multiple script, manually, one after each to run the pre-sysprep, the sysprep and the post-sysprep phase

Thanks!

 

Oh! Good call. Didn't looked it if was Trusted Installer or the Real CMD though. I doubled-clicket on the CMD file form in AUDIT mode ...

 

Well ... another problem.
1) Install
2) Audit mode
3) Sysprep
4) Reboot
5) OOBE
6) First login Yeah!)
7) Reboot .... repair mode!

I have to run BCDBOOT to fix that ... anyone have issue like that?

24H2 has many bugs I found compared to 23H2 around sysprep and all that stuff.

 

Bingo!
I changed the default app and my script completed.

So now I have to find a way to change that settings through registry.

Copying CMD to CMD2 still launch in terminal which is the problem.

 

Here is the REG settings found on another forum just in case someone what to know!

Code:

Windows Console Host
REG ADD "HKCU\Console\%%Startup" /v DelegationConsole /t REG_SZ /d "{B23D10C0-E52E-411E-9D5B-C09FDF709C7D}" /f
REG ADD "HKCU\Console\%%Startup" /v DelegationTerminal /t REG_SZ /d "{B23D10C0-E52E-411E-9D5B-C09FDF709C7D}" /f
For NEW Console host as default, add this additional key (For LEGACY set the value from 1 to 0)
REG ADD "HKCU\Console" /v ForceV2 /t REG_DWORD /d 1 /f

Let Windows Decide
REG ADD "HKCU\Console\%%Startup" /v DelegationConsole /t REG_SZ /d "{00000000-0000-0000-0000-000000000000}" /f
REG ADD "HKCU\Console\%%Startup" /v DelegationTerminal /t REG_SZ /d "{00000000-0000-0000-0000-000000000000}" /f

Windows Terminal
REG ADD "HKCU\Console\%%Startup" /v DelegationConsole /t REG_SZ /d "{2EACA947-7F5F-4CFA-BA87-8F7FBEEFBE69}" /f
REG ADD "HKCU\Console\%%Startup" /v DelegationTerminal /t REG_SZ /d "{E12CFF52-A866-4C77-9A90-F570A7AA2C6B}" /f

I will use my installer script to make the change to the administrator accound. Anyway, it will be destroyed during the sysprep phase and the setting will be lost, so that's good!

 

The tools I make are for "home technician" (or small store) that would like to create recovery partition ala Dell/HP style. I don't want to enfore the removal of Windows Terminal for their end user.

In the firt part of my tools (the part that copy all the requiered files on the computer while in audit mode) ... I decided to put the registry keys. They are only for the current user (administrator) and that account is deleted during the sysprep phase so it has to effect on the end user later on.

 

Thanks!

 

Now, on the other end, I have a weird bug with 24H2 build 1742.

Original EN-US ISO
1) Default install on a clean computer
2) On OOBE, switch to AUDIT mode using CTRL+SHIFT+F3
3) In AUDIT mode ... reseal the image (oobe, generalize, reboot)
4) Go through the OOBE process (I use the BypassNRO script to not create a M$ accout)
5) It should complete and go to the desktop..

but on next reboot ... it goes into repair mode!

Now downloader a more recent build number from UUPDUMP to check if it is still there ....

 

Same problem with latest buld from UUPDUMP ...

Found that on another forum ...

Code:

Found the same issue but I have a workaround. There is an issue with the BCD configuration.

After the Sysprep, I've added these 2 lines in the script WINDIR%\Setup\Scripts\SetupComplete.cmd :


bcdedit -set {current} osdevice partition=C:
bcdedit -set {current} device partition=C:

Seems to work. Still, there is a real bug with 24H2 and Sysprep ...