I know KB2889543 is outdated, but this was for W81-w81 GA conversion, so I didn't used the new one, anyway I will make a change. as far as KB2883200, I had read somewhere it will be replaced soon.. anyway lets see..
That's, because the update Package KB2894179 also applies to Boot.wim Image (Index 1 & 2), I have checked with the windows 8.1 pro vol ga iso boot.wim, both the index's contains the update Package KB2894179
The resetbase againt the mounted .wim can only work for two updates (KB2894029,KB2889543).for the other two updates (KB2894179,KB2883200) it throws up an error saying they are in pending status. so I didn't use the resetbase command. Still you can make a small change the script Code: echo. echo. echo.============================================================================= echo. Integrating Windows 8.1 RTM GA Rollup-1 Updates to Install.wim Image echo.============================================================================= echo. echo.Processing Packages, Please wait... expand %GA%\*.msu -F:Win*.cab %GA%\ >nul Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2894029-%Arch%.cab" Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2889543-%Arch%.cab" Dism /Image:%WimMount% /Cleanup-image /StartComponentCleanup /ResetBase Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2894179-%Arch%.cab" Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2883200-%Arch%.cab" That would perform resetbase for first two updates and will save some space
The resetbase againt the mounted .wim can only work for two updates (KB2894029,KB2889543).for the other two updates (KB2894179,KB2883200) it throws up an error saying they are in pending status. so I didn't use the resetbase command. Still you can make a small change the script Code: echo. echo. echo.============================================================================= echo. Integrating Windows 8.1 RTM GA Rollup-1 Updates to Install.wim Image echo.============================================================================= echo. echo.Processing Packages, Please wait... expand %GA%\*.msu -F:Win*.cab %GA%\ >nul Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2894029-%Arch%.cab" Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2889543-%Arch%.cab" Dism /Image:%WimMount% /Cleanup-image /StartComponentCleanup /ResetBase Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2894179-%Arch%.cab" Dism /Add-Package /Image:%WimMount% /PackagePath:"%GA%\Windows8.1-KB2883200-%Arch%.cab" That would perform resetbase for first two updates and will save some space
Ahh... I see... I simply used the files from the oct17 vl versions, removed the ei.cfg, and subbed out the install.wim; so that wouldn't apply to me. It occurs to me that we need some way of identifying which updates will trigger the pending status... I wonder if there's a clue in the xml file from the msu Edit: after cruising through some of the xml files, I'd have to say that it's out of my league. There's just too much information in the 2883200 rollup that I can't tell whats important and what's not. A better approach might be to run regshot and see which files and registry keys get changed while doing the resetbase after installing it. But then there might be problems with hardlinked files and such... Ahh... it's such a clusterf**k...
A simple dism-fu after intergration | pipe results >> .txt file. My guess all updates via Add-Package = 'pending' meaning they will be installed on-the-fly, as opposed to updates in the OS before the .wim was captured.
Not all of them set the pending flag. If I had to guess, I'd say that certain ones require some sort of unique processing method such as UUID or timestamp or something. It'd be really interesting to learn how they actually apply the patches and what exactly goes on; provided I could actually understand it.
Hello guys , do you know if this one works also with W8 OEM version preinstalled ? I mean - change W81 from RTM to GA version with the tool - grab W8 OEM product key from the system ( legal licence ) - Upgrade the system with W8.1 GA version and when asked put OEM Product key or do you have other way to perform this task ? Thanks a lot BRs AnyB
Is it enough to mount the WIM image and apply the updates in the correct order?, Or need to update boot.wim image too?
This is for Retail version Windows 8.1 but as far as oem version I think this should work but not sure coz haven't had a chance to play with oem machines yet. but I think you can make a Windows 8.1 RTM GA with this tool and change the EI.cfg file contents and use the oem key to activate and that should work out, just give a try.
This toolkit was to make a exact copy of the Windows 8.1 GA ISO (without the SHA-1 matching and /resetbase commands) if you are doing clean install it is better to update both the install and boot wim images.
Microsoft has released GA updated iso for only Windows 8.1 pro volume and windows server 2012 r2 volume edition only.. rest of the version have been left out to get updated by windows update..
Hi , thanks for your feedback , please correct me if I'm wrong make a ie.cfg Code: [Channel] OEM [VL] 0 and put it inside source folder am I right ? Brs AnyB
Hi MSMG, works pretty fine for me! Great work! One Question: is it able to integrate NET35 in your toolkit? Thank's a lot