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.
What VM is recommended to install? What are the conditions or requirements to use? (I'm using Windows 8.1 Professional WMC x64). Thanks.
Yay ... delivered as wished ... what should say besides - THANKS . Will check out some ideas after napp ... but this looks promising. Assume it might be smart to add .NET enable, /CleanUp, /ResetBase and Tokens switch for ProWMC. Apparently as optional features inside the batch processes . BTW: Forgot to mention, perfectly formatted, that way i only need to maintain a single list that could be offered as direct download (like the updates itself). Good to parse that way.
I use VMWare Workstation 11 currently, but you can use vmware player, virtualbox, or many others. I like VMWare because it makes it easy to attach a usb thumb drive to easily transfer files between vm and system.
Hey murphy thanks for your scripts, Just to make sure I'm on the right track. Integration order must be like, 1. Servicing 2. Enabling NetFX 3. 1st Pass + ProWMC-only update 4. NetFX3 updates 5. 2st Pass
One slight change to suggest: Enabling NetFX Servicing 1st Pass + ProWMC-only update NetFX3 updates 2st Pass
Thought that the most updates will do likewise and i saw it failing sometimes if trying to integrate at a later point .
There's very few updates that don't set pending flag, but that's not why I wouldn't recommend it. I would integrate the servicing stack first because it's never grouped with other updates and is generally required to install some updates in a certain order. A bad scenario where setting the pending flag would be if you queued up a bunch of pending updates, but it moves the servicing stack down in priority or something. Then when it comes across an update that the servicing stack update was meant to fix, it isn't installed yet.
OK, good point, so script feature will follow that recommendation and will integrate servicing stack ones first, and add .NET later in the queue . Would guess in that case most of the otheres will already set the flag ... so .NET should be enabled second and then all aother manipulations/integrations ... correct me if i'm wrong here. (you can bark once for yes and twice for no )
hey mate i want to know how to integrate or use MS dart in boot wim or in install wim not sure about it so i asked you Thanx will wait your answer
Yah I would say a good order would be: 1 - servicing stack 2 - features (netfx3, etc) 3 - language pack if any 4 - 2934018 (pre-dec15-2014 isos only) 5 - rollup monthly updates in order by kb number (can do by group such as all the ones in the 2984006 pack) 6 - the non-pack updates 7 - the last-pass updates if any (currently KB3003667) The netfx3 updates don't matter when you update them. I did notice an odd error after integrating them where it asks for the smaller update in the 2962409 rollup pack, specifically KB2980654, but when you try to integrate it, it won't. It gets fixed when you do an online integration with the express version in windows update. Perhaps someone can work up a fix for this issue, such as a cab file with just the components needed.