That makes sense, it would be in preparation for the Windows 8 service pack update (aka Windows 8.1 ) in a couple of months. Oops! Missed Ricktendo64's post earlier. In that case, I agree with him lol.
Hello, Is there possibility to use WindowHotfixDownloader in order to add the Windows 8.1 hotfixs to the Windows 8.1 iso ? Thanks
Repo updated Added: Spoiler KB890830-v5.4 (Additional/Malicious Software Removal Tool) KB2743978 KB2842111 KB2849027 KB2853587 KB2861168-x64 (Additional/Hyper-V) KB2861935-v2 KB2862077 KB2870248 KB2870699 KB2871085 KB2871280-v3 KB2871389 KB2871438 (Additional/RSAT) KB2871777 (Additional/Not Integratable to Offline Image) KB2876126 KB2876213 KB2876315 KB2876407 KB2876415 KB2877114 KB2877237 KB2880289 Windows8.1-KB2880289 (Win8.1 only) Removed: Spoiler KB890830-v5.3 (Additional/Malicious Software Removal Tool) (superseded by KB890830-v5.4) KB2781406-v2 (superseded by KB2876315) KB2782419 (superseded by KB2871389) KB2790920 (superseded by KB2871389 & KB2876315) KB2795997 (Additional/RSAT) (superseded by KB2871438) KB2821663 (superseded by KB2842111) KB2821895 (Additional/Not Integratable to Offline Image) (superseded by KB2871777) KB2823956-x64 (Additional/Hyper-V) (superseded by KB2861935-v2) KB2836899-v2 (superseded by KB2876415) KB2848304 (superseded by KB2842111) KB2857645 (superseded by KB2880289) KB2862772 (superseded by KB2870699) KB2868623 (superseded by KB2876415) KB2871343-v2 (superseded by KB2876415)
@PointZero KB2879488 also superseded by KB2870699 and KB2876126, KB2849027, KB2862077.. all (Additional/RSAT)
abbodi1406, thanks for your expertise and great help in reviewing things. I always seem to miss the RSAT category. I'll leave KB2862077 in the main folder, to stay consistent with komm's repo. I'll also leave KB2871777 in "Not Integratable to Offline Image" for the same reason. (But it can be integrated, if one knows what they're doing.) Thanks to komm for the heads-up on KB2877211. (He'll have a new KUC for Win8 out tomorrow.) Repo Updated Added: KB2877211 Removed: KB2879488 (superseded by KB2870699) Moved: KB2876126 from main folder to Additional/RSAT KB2849027 from main folder to Additional/RSAT
abbodi1406, komm said the reason KB2862077 isn't in the RSAT category is that it's also for TerminalServices. Thanks to komm for info on the following changes. Repo Updated Added: KB2849027-v2 (Additional/RSAT) Removed: KB2849027 (Additional/RSAT) (superseded by KB2849027-v2) Moved: KB2838664 from main folder to Additional/RSAT
I have been using WindowsHotfixDownloader to gather the updates for my monthly update.cmd i run. Is there a preferable order to install the hotfixes to an offline image, or does it matter at all? I generally add the new ones, run a search for superceded updates, and then install these msu dirs in this order to a wim with no previous hotfixes. For maximum compatibility and space, i try to leave a few hotfix dirs out, like Rsat. I have an all in one wim with every edition and arch for Win7\8\8.1 it updates, including WMC and the bases have .Net3 integrated. I guess my question is should i change my order of integration dirs, and is there any important hotfixes im leaving out. win8 Additional\NET35 Main Updates\WU_Satisfy Main Updates Additional\Integrate to installation media Additional\Camera Codec Pack Additional\KB947821.System.Update.Readiness.Tool win7 Additional\IE10\Prerequisites Additional\IE10 Main Updates\WU_Satisfy Main Updates Additional\IE10\Updates
Thanks to komm for KB2885592 (for Win8.1). It updates Windows-DesktopWindowManager-uDWM.Resources to 6.3.9600.16390. Repo Updated Added: Windows8.1-KB2885592 (Win8.1 only) ----------- halikus, only two minor changes to suggest for updates: since you include WMC, you might want to add KB2746119 (in the "Windows Media Center" folder). And "KB947821.System.Update.Readiness.Tool" could be eliminated from Win8.
Thanks PointZero, i wasn't sure if the order mattered or not. Something i have noticed that i'm not sure if people are generally aware of yet, is the ability for Win8 setup to install from esd files. I've seen it briefly mentioned in a few threads, but not much info besides the command to use. Windows 7 setup will not work, but Win 8\8.1 will use install.wim first if present, and if not, look for install.esd. I made the following 37 index install.wim that has 6 indexes with msu hotfixes installed (the indexes with a date), and all the rest are vanilla with Dart and.net3 integrated. Code: Deployment Image Servicing and Management tool Version: 6.3.9600.16384 Details for image : E:\Sources\Projects\UPDATES\install.wim Index : 1 Name : Windows 7 Ultimate (x86) (09-2013) Description : Windows 7 Ultimate (x86) (09-2013) Size : 10,463,065,760 bytes Index : 2 Name : Windows 7 Ultimate (x64) (09-2013) Description : Windows 7 Ultimate (x64) (09-2013) Size : 15,582,545,763 bytes Index : 3 Name : Windows 7 Ultimate SP1 x86 Description : Windows 7 Ultimate SP1 x86 Size : 8,610,128,720 bytes Index : 4 Name : Windows 7 Ultimate SP1 x64 Description : Windows 7 Ultimate SP1 x64 Size : 12,285,492,779 bytes Index : 5 Name : Windows 8.1 Professional (x86) (09-2013) Description : Windows 8.1 Professional (x86) (09-2013) Size : 8,798,425,206 bytes Index : 6 Name : Windows 8.1 Professional (x64) (09-2013) Description : Windows 8.1 Professional (x64) (09-2013) Size : 12,955,354,017 bytes Index : 7 Name : Windows 8.1 Professional (x86) Description : Windows 8.1 Professional (x86) Size : 8,798,425,206 bytes Index : 8 Name : Windows 8.1 Professional (x64) Description : Windows 8.1 Professional (x64) Size : 12,955,354,017 bytes Index : 9 Name : Windows 8 Professional (x86) (09-2013) Description : Windows 8 Professional (x86) (09-2013) Size : 12,439,195,208 bytes Index : 10 Name : Windows 8 Professional (x64) (09-2013) Description : Windows 8 Professional (x64) (09-2013) Size : 20,064,015,218 bytes Index : 11 Name : Windows 8 Professional (x86) Description : Windows 8 Professional (x86) Size : 8,665,067,919 bytes Index : 12 Name : Windows 8 Professional (x64) Description : Windows 8 Professional (x64) Size : 13,040,724,375 bytes Index : 13 Name : Windows 7 Professional SP1 x86 Description : Windows 7 Professional SP1 x86 Size : 8,450,188,760 bytes Index : 14 Name : Windows 7 Professional SP1 x64 Description : Windows 7 Professional SP1 x64 Size : 12,122,886,417 bytes Index : 15 Name : Windows 8.1 ProfessionalWMC (x86) Description : Windows 8.1 ProfessionalWMC (x86) Size : 8,951,825,498 bytes Index : 16 Name : Windows 8.1 ProfessionalWMC (x64) Description : Windows 8.1 ProfessionalWMC (x64) Size : 13,094,060,524 bytes Index : 17 Name : Windows 8 ProfessionalWMC (x86) Description : Windows 8 ProfessionalWMC (x86) Size : 8,870,660,423 bytes Index : 18 Name : Windows 8 ProfessionalWMC (x64) Description : Windows 8 ProfessionalWMC (x64) Size : 13,259,355,688 bytes Index : 19 Name : Windows 8.1 Enterprise (x86) Description : Windows 8.1 Enterprise (x86) Size : 8,752,974,054 bytes Index : 20 Name : Windows 8.1 Enterprise (x64) Description : Windows 8.1 Enterprise (x64) Size : 12,905,485,153 bytes Index : 21 Name : Windows 8 Enterprise (x86) Description : Windows 8 Enterprise (x86) Size : 8,673,654,887 bytes Index : 22 Name : Windows 8 Enterprise (x64) Description : Windows 8 Enterprise (x64) Size : 13,052,237,620 bytes Index : 23 Name : Windows 7 Enterprise SP1 x86 Description : Windows 7 Enterprise SP1 x86 Size : 8,452,146,328 bytes Index : 24 Name : Windows 7 Enterprise SP1 x64 Description : Windows 7 Enterprise SP1 x64 Size : 12,125,530,233 bytes Index : 25 Name : Windows 8.1 Core (x86) Description : Windows 8.1 Core (x86) Size : 8,741,736,635 bytes Index : 26 Name : Windows 8.1 Core (x64) Description : Windows 8.1 Core (x64) Size : 12,864,079,562 bytes Index : 27 Name : Windows 8 Core (x86) Description : Windows 8 Core (x86) Size : 8,725,532,941 bytes Index : 28 Name : Windows 8 Core (x64) Description : Windows 8 Core (x64) Size : 13,082,742,480 bytes Index : 29 Name : Windows 8.1 SingleCoreLanguage (x86) Description : Windows 8.1 SingleCoreLanguage (x86) Size : 8,761,055,211 bytes Index : 30 Name : Windows 8.1 SingleCoreLanguage (x64) Description : Windows 8.1 SingleCoreLanguage (x64) Size : 12,877,390,773 bytes Index : 31 Name : Windows 8 CoreSingleLanguage (x86) Description : Windows 8 CoreSingleLanguage (x86) Size : 8,748,393,532 bytes Index : 32 Name : Windows 8 CoreSingleLanguage (x64) Description : Windows 8 CoreSingleLanguage (x64) Size : 13,088,007,959 bytes Index : 33 Name : Windows 7 Home Premium SP1 x86 Description : Windows 7 Home Premium SP1 x86 Size : 8,569,006,173 bytes Index : 34 Name : Windows 7 Home Premium SP1 x64 Description : Windows 7 Home Premium SP1 x64 Size : 12,222,587,449 bytes Index : 35 Name : Windows 7 Home Basic SP1 x86 Description : Windows 7 Home Basic SP1 x86 Size : 8,127,590,116 bytes Index : 36 Name : Windows 7 Home Basic SP1 x64 Description : Windows 7 Home Basic SP1 x64 Size : 11,710,161,360 bytes Index : 37 Name : Windows 7 Starter SP1 x86 Description : Windows 7 Starter SP1 x86 Size : 8,074,968,070 bytes I used this to make it: (index 1 -37) %Dism% /Export-Image /SourceImageFile:install2.wim /SourceIndex:1 /DestinationImageFile:install.wim /Compress:maximum The size of install.wim is 16.0 GB (17,262,561,553 bytes) When i export the same indexes into an install.esd with: (index 1 -37) %Dism% /Export-Image /SourceImageFile:install2.wim /SourceIndex:1 /DestinationImageFile:install.esd /Compress:recovery The size of install.esd is 10.6 GB (11,479,963,514 bytes) This can save alot of space if it's a factor in your setup after adding hotfixes. Heres the individual OS's. Just the 11 vanilla Win 7 indexes in a wim = 3.57 GB (3,843,552,661 bytes) Just the 11 vanilla Win 7 indexes in a esd = 2.63 GB (2,829,242,066 bytes) Just the 10 vanilla Win 8 indexes in a wim = 4.00 GB (4,295,424,049 bytes) Just the 10 vanilla Win 8 indexes in a esd = 3.06 GB (3,292,677,424 bytes) Just the 10 vanilla Win 8.1 indexes in a wim = 4.31 GB (4,637,330,963 bytes) Just the 10 vanilla Win 8.1 indexes in a esd = 3.43 GB (3,692,867,286 bytes) The pros with this method : -25% better compression size. The cons with this method are : -Won't work with Win7 setup files. (boot.wim or setup.exe) so no upgrades for Win7 from an .esd. A Win8 boot.wim installs Win7 fine from .esd. -Must be running 8\8.1 to make .esd files. -If found, an install.wim will take president. -It takes (on my PC) 75% LONGER to export the indexes to .esd vs using a .wim. -Any installation methods you use where you direct the setup.exe to install.wim must also support install.esd -(As far as i know) There is no way to mount, list indexes, or do anything else to an .esd file once created. Its encrypted.
With WinToolkit did the integration of the Win8-x64 updates, with 1.03 GB size. Only that, once completed, the image size was with 5.09 GB (uncompressed). Is that correct? Why this occurs, if the original image has 3.34 GB (uncompressed) and 1.03 GB only updates? Shouldn't have the final size around 4.37 GB? Appreciate any help
Define "uncompressed"? nevertheless, integrating packages or servicing the mounted wim always result in some redundant size for the temporary files so it's always recommended to "rebulid" the wim file at the end to get rid of this extra size, thats done by exporting the contained images to a new wim file: Code: dism /Export-Image /SourceImageFile:install.wim /SourceIndex:1 /DestinationImageFile:install2.wim /Compress:max repeat that for every index in the original wim, export them all to the same new install2.wim file then delete the old wim and rename the new: Code: DEL /S /F /Q install.wim REN install2.wim install.wim