@Paul955 In order to build a fully up-to-date installation of Windows 8.1, you need the Update 1 ISO (18 March 2014) and about 40 updates, depending on edition, selected features etc. Only 20 of those updates are strictly necessary, but it's worth including the others to stop Windows Update from offering them to you. I have found that I can integrate all the updates offline without having to make special arrangements (the order in which they are integrated is no longer important). I put all the updates in one folder, and then use dism to mount 'install.wim' and add the updates : dism /Mount-Image /ImageFile:<imagepath> /Index:1 /MountDir:<mountdir> dism /image:<mountdir> /Add-Package /packagepath:<updatedir> dism /Unmount-Image /MountDir:<mountdir> /commit Most of the trouble which people have experienced seems to be due to KB2939153, which has been superseded this month. I can let you have a list of updates, but it may not match your exact circumstances. I generated my list by doing a clean install of Windows and then using Windows Update to check which ones are required. Start by installing the missing parts of Update 1 KB2919355 (KB2934018 and KB2959977), then the November rollup (KB3000850, KB3003057 and KB3014442), then follow your nose. Note that some updates consists of several files and WU needs several goes to install all the files.
Hi Cedders and Slave77, thanks for you're reply! Unfortunately I cannot get the Windows 8.1 Enterprise with Update 1 ISO, so I first need to install the Update1 KB's (in a specific order). After that I can add the rest of the updates. I doesn't mater in witch order but for my administration I created a folder per Rollup. When I do an offline-add of Update 1 + November Rollup and do a clean install, Windows Updates wants all the other Rollup's. If I add all the Rollup's offline the WIM file becomes very large -> 6,1GB. I would rather not use a external (not Microsoft) tool integrate the updates. Does anyone has the same issue?
I am experimenting using 'install.esd' instead of 'install.wim'. This works very nicely with W8.1/32, but on W8.1/64, installation fails immediately before the first reboot "Getting finished" (sic) with a message that the installation file is corrupt - the equivalent 'install.wim' works fine. Has anyone else seen this problem ?
The problem is the setup program. it doesn't handle the streams correctly when they are over a certain size. My suggestion, use split-wim and make sure the license.rtf files are in the first chunk.
Thanks for the info Cedders! I need the Windows 8.1 with update Enterprise VL version and that is not available on MSDN. I will wait until Wednesday and try to integrate the updates again.
Preliminary baseline image with integrated 3000850 update is very large. Even x86 version is over 6 gigs. I may end up sysprep/capturing post-tuesday if they don't release new images.
you are doing sysprep for each image index? that may take a very long time. i have tried this but each install/update/resetbase/capture took several hours for me, so i gave up.
There's a few shortcuts you can take. For instance, the CoreConnected image can be /set-edition'd to Core, Professional, ProfessionalWMC. So you just capture it once, export to 2nd wim, mount and set-edition, unmount, export, repeat.
Windows Integration Scripts Hello @Murphy78! Thank you so much for all the help and time you have dedicated to this thread and Windows Integration methods. I have learned an incredible amount this year and have you to thank for it!!! We really appreciate you making us AIO Install ISO's for the last few years and I wanted to say thank you for all your hard work I understand and respect your decision to stop releasing new AIO ISO's each month, sometimes you get to the point where you are bored and not learning anymore. Your releases will be missed but it is comforting to know you will still be around at MDL forums. I was wondering if you would be willing to share some examples of the scripts you use to help automate the update integration process using DISM. You had posted an example script back in June or July, but it would be great to learn from the expert about best practices and methods. I will be making my own AIO ISO's for personal use and I know your scripts would be immensely helpful to myself and others if you are willing to post it. Thank you again for everything you have already done! If only Microsoft came anywhere close to the level of quality you provide with your releases . I certainly owe you a beer if you have a PayPal account or something similar
You can take a look at latest WU TOOL release (see my sig). It has an integration part where you can point it to a TXT list with the KBs you want to have integrated and the WIM you want to have prcoessed. Apparently the Updates must be present in the folder (can be any sub-folder). Then it will service a specific or all indices in that WIM. Only needs some time but no further interaction. TXT list should look like: Code: KB2994290 KB3012199 KB3008242 . . .
Dec15-2014 MSDN win8.1 iso updates list for Integration Here's an update list for these new Dec15-2014 isos: x86: Code: x86\SERVICING\Windows8.1-KB3012199-x86.msu x86\1ST-PASS\Windows8.1-KB3013816-x86.msu x86\1ST-PASS\Windows8.1-KB3008923-x86.msu x86\1ST-PASS\Windows8.1-KB3008925-x86.msu x86\1ST-PASS\Windows8.1-KB3018943-x86.msu x86\1ST-PASS\Windows8.1-KB2977765-x86.msu x86\1ST-PASS\Windows8.1-KB2978041-x86.msu x86\1ST-PASS\Windows8.1-KB2978126-x86.msu x86\1ST-PASS\Windows8.1-KB2979576-x86.msu x86\1ST-PASS\Windows8.1-KB2894856-v2-x86.msu x86\1ST-PASS\Windows8.1-KB3002885-x86.msu x86\1ST-PASS\Windows8.1-KB3011780-x86.msu x86\1ST-PASS\Windows8.1-KB3013126-x86.msu x86\1ST-PASS\Windows8.1-KB2976536-x86.msu x86\1ST-PASS\Windows8.1-KB2899189-x86.msu x86\1ST-PASS\Windows8.1-KB2989930-x86.msu x86\1ST-PASS\Windows8.1-KB2990967-x86.msu x86\1ST-PASS\Windows8.1-KB2998174-x86.msu x86\1ST-PASS\Windows8.1-KB3004394-x86.msu x86\1ST-PASS\Windows8.1-KB3013410-x86.msu x86\1ST-PASS\Windows8.1-KB3013769-x86.msu x86\1ST-PASS\Windows8.1-KB2994290-x86.msu x86\1ST-PASS\KB2919355\Windows8.1-KB2959977-x86.msu x86\1ST-PASS\KB2955164\Windows8.1-KB2955164-x86.msu x86\1ST-PASS\KB2955164\Windows8.1-KB2965500-x86.msu x86\1ST-PASS\KB2962409\Windows8.1-KB2962409-x86.msu x86\1ST-PASS\KB2962409\Windows8.1-KB2980654-x86.msu x86\1ST-PASS\KB2975719\Windows8.1-KB2975719-x86.msu x86\1ST-PASS\KB2975719\Windows8.1-KB2979582-x86.msu x86\1ST-PASS\KB2975719\Windows8.1-KB2990532-x86.msu x86\1ST-PASS\KB2975719\Windows8.1-KB2993100-x86.msu x86\1ST-PASS\KB2975719\Windows8.1-KB2993651-x86.msu x86\1ST-PASS\KB2984006\Windows8.1-KB2977174-x86.msu x86\1ST-PASS\KB2984006\Windows8.1-KB2984006-x86.msu x86\1ST-PASS\KB2984006\Windows8.1-KB2994897-x86.msu x86\1ST-PASS\KB2984006\Windows8.1-KB2995004-x86.msu x86\1ST-PASS\KB2984006\Windows8.1-KB2995518-x86.msu x86\1ST-PASS\KB2995388\Windows8.1-KB2995388-x86.msu x86\1ST-PASS\KB2995388\Windows8.1-KB2996799-v2-x86.msu x86\2ND-PASS\Windows8.1-KB3003667-x86.msu x86\NETFX3\Windows8.1-KB2894852-v2-x86.msu x86\NETFX3\Windows8.1-KB2966826-x86.msu x86\NETFX3\Windows8.1-KB2966828-x86.msu x86\NETFX3\Windows8.1-KB2968296-x86.msu x86\NETFX3\Windows8.1-KB2972103-v2-x86.msu x86\NETFX3\Windows8.1-KB2972213-x86.msu x86\NETFX3\Windows8.1-KB2973114-x86.msu x86\NETFX3\Windows8.1-KB2978122-x86.msu x86\NETFX3\Windows8.1-KB2979573-x86.msu x86\PROWMC\Windows8.1-KB2973201-x86.msu x64: Code: x64\SERVICING\Windows8.1-KB3012199-x64.msu x64\1ST-PASS\Windows8.1-KB3013816-x64.msu x64\1ST-PASS\Windows8.1-KB3008925-x64.msu x64\1ST-PASS\Windows8.1-KB3008923-x64.msu x64\1ST-PASS\Windows8.1-KB3018943-x64.msu x64\1ST-PASS\Windows8.1-KB2977765-x64.msu x64\1ST-PASS\Windows8.1-KB2978041-x64.msu x64\1ST-PASS\Windows8.1-KB2978126-x64.msu x64\1ST-PASS\Windows8.1-KB2979576-x64.msu x64\1ST-PASS\Windows8.1-KB2894856-v2-x64.msu x64\1ST-PASS\Windows8.1-KB3002885-x64.msu x64\1ST-PASS\Windows8.1-KB3011780-x64.msu x64\1ST-PASS\Windows8.1-KB3013126-x64.msu x64\1ST-PASS\Windows8.1-KB2976536-x64.msu x64\1ST-PASS\Windows8.1-KB2994290-x64.msu x64\1ST-PASS\Windows8.1-KB3008242-x64.msu x64\1ST-PASS\Windows8.1-KB2899189-x64.msu x64\1ST-PASS\Windows8.1-KB2989930-x64.msu x64\1ST-PASS\Windows8.1-KB2990967-x64.msu x64\1ST-PASS\Windows8.1-KB2998174-x64.msu x64\1ST-PASS\Windows8.1-KB3004394-x64.msu x64\1ST-PASS\Windows8.1-KB3013410-x64.msu x64\1ST-PASS\Windows8.1-KB3013769-x64.msu x64\1ST-PASS\KB2919355\Windows8.1-KB2959977-x64.msu x64\1ST-PASS\KB2955164\Windows8.1-KB2955164-x64.msu x64\1ST-PASS\KB2955164\Windows8.1-KB2965500-x64.msu x64\1ST-PASS\KB2962409\Windows8.1-KB2962409-x64.msu x64\1ST-PASS\KB2962409\Windows8.1-KB2980654-x64.msu x64\1ST-PASS\KB2975719\Windows8.1-KB2975719-x64.msu x64\1ST-PASS\KB2975719\Windows8.1-KB2979582-x64.msu x64\1ST-PASS\KB2975719\Windows8.1-KB2990532-x64.msu x64\1ST-PASS\KB2975719\Windows8.1-KB2993100-x64.msu x64\1ST-PASS\KB2975719\Windows8.1-KB2993651-x64.msu x64\1ST-PASS\KB2984006\Windows8.1-KB2977174-x64.msu x64\1ST-PASS\KB2984006\Windows8.1-KB2984006-x64.msu x64\1ST-PASS\KB2984006\Windows8.1-KB2994897-x64.msu x64\1ST-PASS\KB2984006\Windows8.1-KB2995004-x64.msu x64\1ST-PASS\KB2984006\Windows8.1-KB2995518-x64.msu x64\1ST-PASS\KB2995388\Windows8.1-KB2995388-x64.msu x64\1ST-PASS\KB2995388\Windows8.1-KB2996799-v2-x64.msu x64\2ND-PASS\Windows8.1-KB3003667-x64.msu x64\NETFX3\Windows8.1-KB2894852-v2-x64.msu x64\NETFX3\Windows8.1-KB2966826-x64.msu x64\NETFX3\Windows8.1-KB2966828-x64.msu x64\NETFX3\Windows8.1-KB2968296-x64.msu x64\NETFX3\Windows8.1-KB2972103-v2-x64.msu x64\NETFX3\Windows8.1-KB2972213-x64.msu x64\NETFX3\Windows8.1-KB2973114-x64.msu x64\NETFX3\Windows8.1-KB2978122-x64.msu x64\NETFX3\Windows8.1-KB2979573-x64.msu x64\PROWMC\Windows8.1-KB2973201-x64.msu No longer needed to integrate x86: Code: x86\Pre-Dec-Updates\Windows8.1-KB2920189-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2954879-v2-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2958262-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2961072-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2962140-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2965142-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2967917-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2971203-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2973351-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2976627-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB2978742-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB3003057-x86.msu x86\Pre-Dec-Updates\Windows8.1-KB3008242-x86.msu x86\Pre-Dec-Updates\KB2919355\Windows8.1-KB2934018-x86.msu x86\Pre-Dec-Updates\KB3000850\Windows8.1-KB3000850-x86.msu x86\Pre-Dec-Updates\KB3000850\Windows8.1-KB3003057-x86.msu x86\Pre-Dec-Updates\KB3000850\Windows8.1-KB3014442-x86.msu No longer needed to integrate x64: Code: x64\Pre-Dec-Updates\Windows8.1-KB2920189-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2954879-v2-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2958262-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2961072-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2962140-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2965142-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2967917-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2971203-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2973351-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2976627-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB2978742-x64.msu x64\Pre-Dec-Updates\Windows8.1-KB3003057-x64.msu x64\Pre-Dec-Updates\KB2919355\Windows8.1-KB2934018-x64.msu x64\Pre-Dec-Updates\KB3000850\Windows8.1-KB3000850-x64.msu x64\Pre-Dec-Updates\KB3000850\Windows8.1-KB3003057-x64.msu x64\Pre-Dec-Updates\KB3000850\Windows8.1-KB3014442-x64.msu You can attempt to integrate all the same files to the winre.wim and boot.wim and add the newer setup files from: KB3005608 that abbodi mentioned. It will just not add the ones that are not applicable. Remember to do a resetbase on the images before unmount.