No I mean the one inside LCU, can I somehow see inside LCU cab file and see what setup.exe version I'll get if I apply this update into a boot.wim? To save time
I have no clue and that info i never needed to know either Maybe @abbodi1406 can tell. Just make sure that after integrating all updates these setup.exe files are matching: Code: boot.wim\2\sources\setup.exe & Code: ISO:\Sources\setup.exe
for the latest LCU(.906) and latest DU(setup.exe inside DU is .900), those won't match, can you confirm?
Can you spot what I'm doing wrong? Code: >dism /mount-image /imagefile:boot.wim /index:2 /mountdir:a Deployment Image Servicing and Management tool Version: 10.0.19041.844 Mounting image [==========================100.0%==========================] The operation completed successfully. >dism /image:a /add-package /packagepath:ssu.cab Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.867 Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.903.1.4 [==========================100.0%==========================] The operation completed successfully. >dism /image:a /add-package /packagepath:lcu.cab Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.867 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.906.1.13 [==========================100.0%==========================] The operation completed successfully. >dism /image:a /get-packages Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.906 Packages listing: Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.906.1.13 State : Installed Release Type : Update Install Time : 2021/04/01 10:31 PM Package Identity : Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.903.1.4 State : Installed Release Type : Security Update Install Time : 2021/04/01 10:21 PM setup.exe is still .789
@abbodi1406 recently explained what is needed to be done on UUP based images, iirc you need to update boot.wim index 2 sources folder with the DU for Sources setup.exe (and iso:\sources). Is this a UUP based ISO or an official one?
Only an idea. Try an earlier official image as base, because the later ones are apparently sysprepped images of the early ones and there are chances that they got damaged somehow in the process. This would be in the finer details and not obvious for regular upgrade use.
For (in-place) upgrade - repair 19041/19042/19043, the esd builds are the most successful (this scenario is more thoroughly tested by ms), I've done it dozens of times and the integrated up-to-date uup ones have often failed to repair the issue I was having/causing For new installs / fiddling with the iso, the uup builds will obviously save a lot of time, not much difference from mvs ones that are also made automatically from uup, but with ms in-house tools
I still have to see a failed upgrade using either method. Actually I never tested the esd upgrade although it is in my future plans. What about the Server SKU if you think that the MVS ISO is created from UUP? Is there any equivalent UUP for Server/LTSC SKU?
.906 all good now I hate win 10 when MS runs 60% of the OS thru there servers now my start menu came back took 3 days and thanks to OldMX for his script on the antivirus update problem