24H2 Help on apply KB patch to captured master image in audit mode, the KB cause driver corruption

garlin said:

I don't have a specific insight, but my gut feeling from reading the different install and sysprep stories is the current 24H2 build has a broken Servicing Stack. Normal servicing operations appear to work, but silently fail on deployment. It's like parts of the install are entirely missing when they're clearly present in the deployment image.

Hopefully MS recognizes there's a severe problem and pauses 24H2 rollout until they figure out what's going on.

Click to expand...

Yes, for sure 24H2 have a lot og bug, I'm also in contact with an internal MS people but also him, after that I show you some bugs, don't have the capabilities to upscale the problem...

I can say for sure that the new setup wizard is totally bugged, for at least these things:
it create a Window.old folder empty in C:\
it don't move inside C:\Recovery folder the file that you save in $OEM$\$1\Recovery from installation media
the recovery, full or partial from Windows, it don't work.

You can fix them if you install Windows 24H2 with forcing old wizard.

24H2 Setup is running a different client by default, which performs a clean install as an "upgrade". The problem is none of this has been documented at all during the Insider Preview.

If you know how to mount boot.wim and can modify the mounted image's registry hive, then you can switch back to the old Setup.
W11 24h2 and old installation setup

garlin said:

24H2 Setup is running a different client by default, which performs a clean install as an "upgrade". The problem is none of this has been documented at all during the Insider Preview.

If you know how to mount boot.wim and can modify the mounted image's registry hive, then you can switch back to the old Setup.
W11 24h2 and old installation setup

Click to expand...

Unfortunately I know very well how Microsoft works...
I have a lot of tools, software and other resorce but there isn't the information how to use it.

About the boot.wim, I already customize it and I force the old setup wizard.

I have an update about the post topic and I think to have found the solution, I need to do more check to confirm it.

Mamukata said:

Your way to clone a already confgured system is not the right way becasue Windows already have generate the SSID and if you clone that system you can have problem inside the network.

Click to expand...

Actually, I am not cloning an already configured system. I am configuring the system in AUDIT MODE which is 100% valid. I have never fully installed Windows, I go into audit mode right at the start of OOBE.

Also, the whole duplicate SID issue is now thoroughly debunked.

NEWS!!

today MS have release for OEM new OPK package I hope with lot of FIX.
Download and I'll test it

Mamukata said:

NEWS!!

today MS have release for OEM new OPK package I hope with lot of FIX.
Download and I'll test it

Click to expand...

At the first test nothing is change, boot.wim continue to be bugged.

If you think the problem starts with 24H2's boot.wim, why not transfer your captured image to a 23H ISO and repeat the install? Other than 24H including a new signed bootloader, functionally it's the same thing to have a 23H2 ISO install the 24H2 image.