Thanks for the info. There was another older non-netfx Win8.1 hotfix that did this also. KB999994 switches windows-mspaint to LDR branch (.20496). But, yes- not many updates with LDR. Win7 had a lot of them.
Good observation. That update always seemed weird, based on its KB# and that there's no KB page. Now that I see it has the same binary (thanks) and since it was an early release (Dec '13), I do agree with you that it was probably a test update. But regardless, KB999994 does switch that component (windows-mspaint) to LDR branch. That means future updates will also need to contain LDR to install. GDR-only updates won't install for it. Same for 2977302 and 2925384-v4, since they're LDR only. (And the 6-7 other GDR+LDR updates, if forced to install LDR.)
999994 is a test hotfix for sure it updates different components for Win7 (dns client) and Win8 / 8.1 but same binaries doesn't always means that there are no changes the component manifest also has registry settings and other things
No difference between the two versions the change can be made by either moving the file yourself or delete it and re-download it
is there a list of updates that can/should be applied to boot.wim or winre.wim ? - i have a made list by looking to "appliesTo" section in the pkgproperties.txt file which is inside the .msu files. - i have updated boot.wim file with these .msu files which has "Windows 8.1 WinPE" string in pkgproperties.txt file. But boot.wim file size doubled.
Just integrate to both indexes the same baseline updates, in this case: - These KB's must be installed in the following order: 1. KB2989647 2. KB2966870 3. KB2959977 4. KB2934018 ed. Then optimize your wim files as Stripakulina says in the following post...
As an example: Code: Dism /mount-wim /wimfile:D:\win8\wim\boot.wim /index:1 /mountdir:D:\win8\mount Dism /Image:D:\win8\mount /Cleanup-Image /StartComponentCleanup /ResetBase Dism /unmount-wim /mountdir:D:\win8\mount /commit Dism /mount-wim /wimfile:D:\win8\wim\boot.wim /index:2 /mountdir:D:\win8\mount Dism /Image:D:\win8\mount /Cleanup-Image /StartComponentCleanup /ResetBase Dism /unmount-wim /mountdir:D:\win8\mount /commit Dism /Export-Image /SourceImageFile:D:\win8\wim\boot.wim /SourceIndex:1 /DestinationImageFile:D:\win8\iso\sources\boot.wim /compress:maximum Dism /Export-Image /SourceImageFile:D:\win8\wim\boot.wim /SourceIndex:2 /DestinationImageFile:D:\win8\iso\sources\boot.wim /compress:maximum Your optimized boot.wim is ready.
Have anybody a plan to apply the dism-cleanup on image that allready have integrated all updates? If i try this i get error message about pending operations, how i can convert into "installed" ? Would be very happy if one know a solution. Greez
Afaik only way to do would be to apply WIM and boot into Audit-Mode, sysprep/generalize/shutdown and recapture as WIM .
Thank you for quick answer, yea have some read and experimented with. But i don't understand how it works, how start into audit, how use sysprep and how to recapturing? Can you please a quick report what i have to do? Can i recapture from to capturing systems or i need a boot-stick, how?
When installing Windows there's a moment where you create a new user (with password) ... press Ctrl+Shift+F3. System will reboot and create temporary admin account. I let it normally settle a while then reboot the system. At every StartUp in Audit-Mode the Sysprep dialog will pop up, choose OOBE (should iirc be chosen by default), check the generalize option and 'shutdown' from the dropdown menus and start the process. If all goes well System will shutdown after a while. Tricky part is to recapture from PE environment ... i use a Win8.1SE ISO in a VM to capture to an usb pen attached to it. Can be also done from PE of a Win 8.1 Install media using dism, only needs to determine the syspreped Windows drive letter and a place to store. Code: dism /Capture-Image /ImageFile:"j:\install.wim" /CaptureDir:"D:\" /Name:"Windows 8.1 Pro" /Description:"Windows 8.1 Pro" /CheckIntegrity /Verify