Hello AnarethoS, just used your script with new Samsung Book4. Everything looks fine, no problem. Win11 24H2 image I have used your script after I have cleaned Win11 with NTLite and Wn11debloat Everything is working and clean. Thanks a lot!! p.s. found easter eggs in script Sysprep.cmd Reccomended -->> Recommended
I redid all my tests (Windows 10 22H2 + Windows 11 24H2) and they worked. Did you use the new xml file from 6.0.1 ? Also, since I know you are playing with VmWare, can you check before running my script (maybe make a snapshot) to see if the Winre..wim file is really on the recovery partition or if it is in c:\recovery\windowsre ? Also, is the size of the Winre.wim small enough to fit on the recovery partition? I had that problem when I did a MUI version of Windows where the winre.wim was now too big to fit on the recovery partition.
For those of you that are trying Windows 10 ... did you use the NEW XML file from the new version or old XML file from previous one? With the latest version there are somme differences between XML (Windows 10, Windows 11 on supported hardware and Windows 11 on unsupported hardware).
Version 6.0.2 is out. The new version don't use WMIC anymore (Sysprep.CMD and WInRE Update). I use Powershell instead. A little bit slower but works everythime while WMIC was working only in sysprep since once Windows 11 24H2 is in "user mode", WMIC got removed. Also, I dow more pre-check for the WINRE.WIM file before starting the sysprep phase. If anything is missing, you will be notified before the sysprep run so you can fix it. Saddly, I can't really code the fix for the different problem (winre.wim file too big, bad partition layout, mismatch betweed resetcong.xml and autounattend.xml, etc.). When the capture is done there is a new warning telling you that the computer will shutdown (push-button) or reboot (capture - full wim). Thanks!