Spoiler It's better to update just 1 winre.wim and copy it over to alle indexes, otherwise the install.wim size will be unneccessarily big.
Hey how do you know that this is for boot/winre.wim? Enthousiast recons to add it to install.wim. I've read the KB it doesn't mention which wims. I see abbodi1406 hasn't included it in WHD Lists.
Unpack the cab using winrar/7zip and copy the files over to the installmedia (\sources), it's not for install.wim.
but isn't there anybody who REALLY KNOWS howto integrate these Updates ( Service Stack, Dynamic Upd, Cumulative Upd) into an Install-DVD. I've googled this problem with no success! Fowler & Flipp3r & Enthousiast & abbodi1406 e.t.c. , more than 10 different opinions. It would be great if we could add our knowledge to ONE really GOOD and correct solution! If I've a look at the content of this CAB, I cannot find one of these files in \sources that has to be overwritten. Thank you
Because WU doesn't offer it for live os (install.wim) and that because cumulative update already contain the DU comonents (same version or newer) however, sure you can add it to install.wim btw, latest one (KB3142588) is for both indexes of boot.wim, and winre.wim
@A-Bit, For the future monthly update KBs, can I replace update KBs and modified in UpdateWinX.cmd of your script, is it work?
Sorry to bother you, but how can I add KB3142588 to winre.wim using DISM and an offline image? Because in offline mode I can't find it anywhere? (boot.wim and other updates isn't a problem!) Or is this just index 1 of boot.wim? Thanks!
Yes, when updates occur, monthly or otherwise, the x86 and x64 .msu or .cab files would need to be copied or added to the appropriate d:\images\x86 and d:\images\x64 folders. Then, the UpdateWinX.cmd script also would need to be modified. Change the FOR statements in the :install and/or :winre subroutines as required to add and remove the update numbers. Also, the <list_of_update_numbers> specifies the install order. Code: 'for %%i in (<list_of_update_numbers>) do (call :AddPackage %1 %%i %3) Code: :winre for %%i in (3139907 3142588) do (call :AddPackage %1 %%i %3) set dism_opt=/Image:%MountDir% /Cleanup-Image /StartComponentCleanup /ResetBase call :DISM_exe %3 goto :EOF :install if NOT EXIST .\%1-winre.wim ( copy %MountDir%\Windows\System32\Recovery\winre.wim .\%1-winre.wim 1>NUL 2>&1 if EXIST .\%1\winre.wim del /F /A .\%1\winre.wim ) if EXIST .\%1\winre.wim ( copy /Y .\%1\winre.wim %MountDir%\Windows\System32\Recovery 1>NUL 2>&1 ) for %%i in (3139907 3142588 3140768 3144756 2693643) do (call :AddPackage %1 %%i %3) goto :EOF Then in an Administrator: Command Prompt window: Code: For x86 (32-bit): d:\images\UpdateWinX.cmd x86 winre d:\images\UpdateWinX.cmd x86 install For x64 (64-bit): d:\images\UpdateWinX.cmd x64 winre d:\images\UpdateWinX.cmd x64 install The integration process always starts 'clean' with the original x86 and x64 image files (boot.wim, winre.wim, and install.wim) that were copied to the d:\images folder. Always update the install.wim last because: (1) the updated winre.wim file is copied to the mounted install.wim image, and (2) after the install.wim is updated, the esdXwim.cmd script is used to create an updated install.esd
Mount install.wim and go to "Mountfolder:\windows\system32\recovery" here you'll find what you're looking for