you forgot - mark before f: Code: expand -f:Windows10.0-KB5003214-x64.cab Windows10.0-KB5003214-x64.msu + check downloaded file sha1 hash
@abbodi1406 Thanks. It was indeed a corrupt file. After downloading from msft update catalog I'm able to extract cab files. Is there any script in BatUtils repo to do the conversion from msu to cab for different windows version?
@VDev msu file is just a cab file, you can extract it with various tools (expand.exe, 7-zip, winrar..)
Slipstream successful! Windows 10 21H1 build 19043.1023 with latest updates. Thanks to the tutorials and information kindly provided and available in this topic. However, I had some issues: At first, it was necessary to integrate KB5003173 individually (separated from the other updates). Strangely, after new installation completed and despite the winver utility correctly displaying version "19043.1023". I noticed that Windows Update was downloading update KB5003214 again. During the execution of the W10UI script, the MsMpEng.exe process of Windows Defender besides consuming a lot of RAM memory and refusing to be disabled, it was causing abnormal errors in DISM during the assembly. After renaming the folder "Program Files\Windows Defender" (via brute-force) to prevent its execution, I managed to finish normally. Thanks!
Thanks I always like 7z or Wintoolkit to extract cab but when I saw couldn't install or corrupted end at the end of file I got scared. Anyway I managed to use Win10UI to integrate 21H1.1023 and its working fine.
I honestly cannot understand this behavior! Even after integrating all latest Windows 10 updates correctly into the installation image built with the help of the W10UI. After one or two days of complete installation, Windows 10 insists on downloading and re-installing KB5003214 (build 19043.1023). I don't know if it's because of the .NET Framework 3.5 I'm not integrating into the image. Because when I activate the option "Enable .NET 3.5 = YES", I can't clean the image, because of the DISM error message: pending.xml file in the WinSXS folder (I've seen another reports here that this can happen).
Because we remove there edge chromium n they try to install it again via wu . thatswhy LCU is offered again.
In fact, I also removed the default version of Edge Chromium to install its latest version. I even suspected that Windows Update Delivery Optimization might be the cause of this behavior. That is, theoretically he would have no reason to download again. Trying to look here at the Windows Update log files here to identify the possible trigger. Regards!
That's not an error, it's expected behavior, enabling dotnetfx35 simply sets the pending flag causing no cleanup can run till the pending flag is gone, that will happen after installing the image. This is the reason W10UI first integrates the updates, next runs the selected cleanup option and next enables the feature and then reintegrates the LCU and NDP35-48 (or NDP472 on 1809 when NDP48 is not integrated). The LCU maintains/installs Edge Chromium for a little while now, W10UI has options to avoid that happening.
