Wednesday, 5 August 2015

Updating the Official Windows 8.1 ISO Releases


Ok as slipstreaming goes its a pain with 8 and 8.1 due to the "Servicing Stack" updates mostly, so i have taken a totally different path to how i normally integrate updates into windows source disks and usb's for windows 8.1.

Firstly lets remember there is sometimes MORE updates for one type than another

EXAMPLE:
the x64 version has an update for windows that the x86 doesn't have (and vice versa)
it can also happen that there is an update for pro (thats not needed by home)

Having these updates in the same folder (IE, running a batch on home and there are also pro only updates in the folder) won't be a problem, DISM & Windows Installer will just skip it often with the basic message  "this update is not applicable for this version of windows"   ;)

Option ONE:  semi high tech
Integration wise, if you have 7 or how ever many versions of windows 8.1 (inside ONE WIM file) you have to unpack them & mount them, place the updates within a folder (you make) called  WINDOWS_UPDATES  for an x86 wim, place all the x86 updates in that, for an x64 wim place all the x64 updates in it.

Note that size wise, when you compile one or more x86 images (or x64) into ONE wim
only 1 copy of a file is actually stored (so 7 versions won't end up taking the space of 7 copies of every update) you will ONLY end up with 1 copy of each update file.. yet if you export 1 wim, it'll export with the updates, because you merged them all with updates inside (so adding updates to all wim files is important ;)

With the WINDOWS_UPDATES folder copied to the ROOT of each wim (after install the folder and msu files will be in the systems root regardless of their chosen drive letter or lable) you then have choices on how they'll be run....

A) manually by running the bat file you make (in the folder with the MSU files)
i called mine   0ImportantUpdatesX64.bat  (0 is so its first file in the folder)

Contents of BAT file are as follows
(make sure word wrap is off when making this in notepad)
and make sure its saved as a BAT.. not a TXT..
 0ImportantUpdatesX64.bat    not    0ImportantUpdatesX64.bat.txt
(name it x86 for the x86 folder, just in case things get more automated in your coding)

@ECHO OFF
setlocal
set PATHTOFIXES=%SystemDrive%\WINDOWS_UPDATES
FOR %%i IN ("%PATHTOFIXES%\*.msu") DO START /WAIT "" WUSA.EXE "%%i" /quiet /norestart
B) rather than making the bat file, you could add the code above to the setupcomplete.cmd


Your other option
Option TWO:  seriously low tech

keep a copy of the 2 update folders

EXAMPLE
DRIVE:   \x86\WINDOWS_UPDATES
DRIVE:   \x64\WINDOWS_UPDATES
with the MSU files in each (along with the batfile in each)
and after install, copy the folder to the root, right click & run the bat as admin
(the low teck solution does make it easier to keep an updated folder to hand rather than re-editing wims)

Clearly their are more hightech ways to get the FOLDER to move over using the setupcomplete.cmd but that's a lot more messing around, extra file copying that'll delay other stuff set with the CMD file, install failing if media is damaged and something can't be read.

This isn't the greatest of methods, but tbh copying a folder to the root and runnin a bat file isn't that hard right?


As for the moronic trolling comments i feel will follow this post... like.. what a joke.. why bother.. just use windows update....  ber this in mind.. some people use pre-pay dongles.. or have crap internet connections..  this is about Bandwidth, not just Automation!!

IF YOU DOWNLOAD THE OFFICIAL WINDOWS 8.1 ISO FILES:
these are the current needed updates covering ISO release to AUGUST 2015
(so after doing these.. save any newer ones to the respective x86 and x64 folders)

Important Updates Section (on windows update) for x64


NDP462-KB3151800-x86-x64-AllOS-ENU.exe  <-- Run Manually or setupcomplete it

and then these

Windows8.1-KB2894856-v2-x64.msu
Windows8.1-KB2899189-x64.msu
Windows8.1-KB2973351-x64.msu
Windows8.1-KB2977765-x64.msu
Windows8.1-KB2978041-x64.msu
Windows8.1-KB2978126-x64.msu
Windows8.1-KB2979576-x64.msu
Windows8.1-KB2994290-x64.msu
Windows8.1-KB3004361-x64.msu
Windows8.1-KB3004365-v2-x64.msu
Windows8.1-KB3008242-x64.msu
Windows8.1-KB3011780-x64.msu
Windows8.1-KB3019215-x64.msu
Windows8.1-KB3019978-x64.msu
Windows8.1-KB3021674-x64.msu
Windows8.1-KB3021910-x64.msu
Windows8.1-KB3022777-x64.msu
Windows8.1-KB3023222-x64.msu
Windows8.1-KB3023266-x64.msu
Windows8.1-KB3025417-x64.msu
Windows8.1-KB3030377-x64.msu
Windows8.1-KB3032663-x64.msu
Windows8.1-KB3033889-x64.msu
Windows8.1-KB3035017-x64.msu
Windows8.1-KB3035126-x64.msu
Windows8.1-KB3035132-x64.msu
Windows8.1-KB3037579-x64.msu
Windows8.1-KB3038256-x64.msu
Windows8.1-KB3039066-x64.msu
Windows8.1-KB3042085-v2-x64.msu
Windows8.1-KB3042553-x64.msu
Windows8.1-KB3044374-x64.msu
Windows8.1-KB3045171-x64.msu
Windows8.1-KB3045685-x64.msu
Windows8.1-KB3045755-x64.msu
Windows8.1-KB3045999-x64.msu
Windows8.1-KB3046002-x64.msu
Windows8.1-KB3046359-x64.msu
Windows8.1-KB3055642-x64.msu
Windows8.1-KB3059317-x64.msu
Windows8.1-KB3061468-x64.msu
Windows8.1-KB3061512-x64.msu
Windows8.1-KB3061518-x64.msu
Windows8.1-KB3062760-x64.msu
Windows8.1-KB3065822-x64.msu
Windows8.1-KB3067505-x64.msu
Windows8.1-KB3069392-x64.msu
Windows8.1-KB3070102-x64.msu
Windows8.1-KB3072630-x64.msu
Windows8.1-KB3072633-x64.msu
Windows8.1-KB3074886-x64.msu
Windows8.1-KB3075516-x64.msu
Windows8.1-KB3079777-x64.msu
Windows8.1-KB3079904-x64.msu


Important Updates Section (on windows update) for x86

NDP462-KB3151800-x86-x64-AllOS-ENU.exe  <-- Run Manually or setupcomplete it

and then these
Windows8.1-KB2894856-v2-x86.msu
Windows8.1-KB2899189-x86.msu
Windows8.1-KB2973351-x86.msu
Windows8.1-KB2977765-x86.msu
Windows8.1-KB2978041-x86.msu
Windows8.1-KB2978126-x86.msu
Windows8.1-KB2979576-x86.msu
Windows8.1-KB2994290-x86.msu
Windows8.1-KB3004361-x86.msu
Windows8.1-KB3004365-v2-x86.msu
Windows8.1-KB3008242-x86.msu
Windows8.1-KB3011780-x86.msu
Windows8.1-KB3019215-x86.msu
Windows8.1-KB3019978-x86.msu
Windows8.1-KB3021674-x86.msu
Windows8.1-KB3021910-x86.msu
Windows8.1-KB3022777-x86.msu
Windows8.1-KB3023222-x86.msu
Windows8.1-KB3023266-x86.msu
Windows8.1-KB3025417-x86.msu
Windows8.1-KB3030377-x86.msu
Windows8.1-KB3032663-x86.msu
Windows8.1-KB3033889-x86.msu
Windows8.1-KB3035017-x86.msu
Windows8.1-KB3035126-x86.msu
Windows8.1-KB3035132-x86.msu
Windows8.1-KB3037579-x86.msu
Windows8.1-KB3038256-x86.msu
Windows8.1-KB3039066-x86.msu
Windows8.1-KB3042085-v2-x86.msu
Windows8.1-KB3042553-x86.msu
Windows8.1-KB3044374-x86.msu
Windows8.1-KB3045171-x86.msu
Windows8.1-KB3045685-x86.msu
Windows8.1-KB3045755-x86.msu
Windows8.1-KB3045999-x86.msu
Windows8.1-KB3046002-x86.msu
Windows8.1-KB3055642-x86.msu
Windows8.1-KB3059317-x86.msu
Windows8.1-KB3061468-x86.msu
Windows8.1-KB3061512-x86.msu
Windows8.1-KB3061518-x86.msu
Windows8.1-KB3062760-x86.msu
Windows8.1-KB3065822-x86.msu
Windows8.1-KB3067505-x86.msu
Windows8.1-KB3069392-x86.msu
Windows8.1-KB3070102-x86.msu
Windows8.1-KB3072630-x86.msu
Windows8.1-KB3072633-x86.msu
Windows8.1-KB3074886-x86.msu
Windows8.1-KB3075516-x86.msu
Windows8.1-KB3079777-x86.msu
Windows8.1-KB3079904-x86.msu

There is also 80+ optional updates needed by the so called NEW official iso files
    but they are Optional, not specifically important
(but you can grab them and add them to your folders or wims if you wish to...

Worried about your final WIM size if storing them inside?
when your finished making the final WIM.. Convert it to ESD
(that can knock well over a gig off its size)   ;)


Tbh.. i did manage to modify the Burf Windows update install script so it works on windows 8.1, but it clearly states not to distribute modified versions of it.. and as of yet.. hes not updated it..


No comments:

Post a Comment

Please keep comments clean...

Note: only a member of this blog may post a comment.