Hi all. Bit bored and messing about installing Win 8.1 updates to an online system. Not had much luck adding all the updates to an offline install.wim image and keeping it under 4gig. Not had much luck spliting the install.wim and getting it to install. Not tried that sort of "cheating" method with two different USB drives, one in fat32 to kick things of then the main install set at NTFS. Anyway. Starting looking at installing update to an online machine. i have seen a few good scripts about and all seem to work well. Found one i like and may use, sorry cant remember where i got it from. Looked into using DISM also but did not have much luck. Till i tried extracting the .cab files from the downloaded .msu files. This is a pretty quick process. Then DISM likes the .cab files and installs the updates. Just testing it out on the .net35 updates. My question is... Does using DISM to add packages do exactly the same thing as using wusa.exe or is there a difference. Not timed how long it takes for either process to install the updates. any thoughts ?
msu uses dism api to install updates, it's not a separate independent tool DISM can "stage" some updates that are ment for higher upgrade edition (i.e. update for group policy installed on core edition, dism stage this update so it will be installed if edition upgraded to pro) msu (wusa) usually have more checks and can't stage updates, it will give a "not applicable error" but, some updates that have .exe file which executed on live system, must be installed using direct .msu msu (wusa) can't install updates by groups, only one update at a time dism can install multiple updates (packages), so it's faster in 90% of cases, dism is the ultimate install tool
cheers for that info... So basicly, extracting the .cab files from update .msu files and using DISM is a good idea ? I feel the need to do a full test. using Win 8.1 Pro x64 Update 3 image. i have the updates downloaded GENERAL HOTFIX SECURITY NET35 I have these extracted to .cab files ready to go.