The order is same for Windows 7/8.1 with just some Additional and Extra components have been made int0 Feature Packs and moved to Integrate Features Menu. And For Windows 10 The order has been changed from past few versions to make it easier to understand and it's like this <Packs\WHD\x64\W10rs1\Cumulative> <Packs\WHD\x64\W10rs1\Dynamic> <Packs\WHD\x64\W10rs1\Flash> <Packs\WHD\x64\W10rs1\MediaFeaturePack> <Packs\WHD\x64\W10rs1\RSAT> <Packs\WHD\x64\W10rs1\ServicingStack> <Packs\WHD\x64\W10rs1\SetupMedia> <Packs\WHD\x64\W10rs1\WinPE> Just copy the corresponding updates to the above folder and use the Integrate WHD General Updates for Integrating Cumulative, Dynamic, Flash, Servicing Stack, Setup Media, WinPE Updates, And Use the Integrate WHD Extra Updates for Media Feature Pack, RSAT Features. In future versions Media Feature Pack, RSAT will be made as Feature Packs and moved to Integrate Feature section like Net FX 4.6.2
Thanks But I have fixed the issues regarding IE11 updates and RSAT integration And, For WMF 5.1 if the .MSU file is used for integration it gets integrated properly but if we use the .CAB files inside it and follow the PkgInstalOrder.txt inside the .MSU file then the integration fails like below Code: =============================================================================== MSMG ToolKit - Integrate Windows Management Framework (WMF) 5.1 =============================================================================== ------------------------------------------------------------------------------- ####Starting Integrating Windows Management Framework (WMF) 5.1################ ------------------------------------------------------------------------------- Source WIM Image : Install.wim Source WIM Index : 1 Source WIM Architecture : x86 Source WIM Build : 6.1.7601.17514 ------------------------------------------------------------------------------- ####Integrating Windows Management Framework (WMF) 5.1######################### ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.14986.1000 Image Version: 6.1.7601.17514 Processing 1 of 1 - Adding package Package_for_KB2872035~31bf3856ad364e35~x86~~6.1.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.14986.1000 Image Version: 6.1.7601.17514 Processing 1 of 1 - Adding package Package_for_KB2872047~31bf3856ad364e35~x86~~6.1.1.0 Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C:\ToolKit\Logs\Dism.txt ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.14986.1000 Image Version: 6.1.7601.17514 Processing 1 of 1 - Adding package Package_for_KB3033929~31bf3856ad364e35~x86~~6.1.1.1 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.14986.1000 Image Version: 6.1.7601.17514 Processing 1 of 1 - Adding package Microsoft-Windows-WinMan-WinIP-Package-TopLevel~31bf3856ad364e35~x86~~7.3.7601.16384 [===========================99.6%========================= ] The operation completed successfully. ------------------------------------------------------------------------------- ####Finished Integrating Windows Management Framework (WMF) 5.1################ ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . . As per abbodi1406 suggestion the KB2872047 is not needed or applicable so I will skip that update while integrating.
I need to integrate .Net3.5 package into the image Win8.1 x64 en-us. But, in the OP, I did not find this package. Only .Net3.5 MUI.
The ToolKit while integrating updates uses WHD Repo, it follows the Install order specified with it and it's like this : Code: :: Windows 8.1 RTM (Build : 6.3.9600.16384) KB3021910 KB2919355 KB3000850 KB2932046 KB2934018 KB2937592 KB2938439 KB2938772 KB3003057 KB3014442 KB3173424 :: Windows 8.1 with Update (IR3 Build : 6.3.9600.17031) KB3021910 KB3173424 KB3000850 KB2934018 KB3003057 KB3014442 :: Windows 8.1 with Update Refresh (IR4 Build : 6.3.9600.17056) KB3021910 KB3173424 KB3000850 KB3003057 KB3014442 :: Windows 8.1 with Update Refresh (IR5 Build : 6.3.9600.17415) KB3021910 KB3173424 And if you are manually integrating the updates by copying the updates to <Updates\<OS>\<Arch>> then it's not the ToolKit but its the DISM which chooses the order of the Integration.
The .Net FX35 MUI was provided for people who uses Windows 8.1 with Multiple languages and it's safe to use for the Single Language too. The .Net FX35 MUI Pack contains both the x86 and x64 files. The ToolKit will search for sxs folder inside the <DVD\sources> folder if its present it will proceed for integration and if the sxs folder is not present then it look for <Packs\NetFX35\w81\x64> folder, if it's present then it will start the integration.
I want to make this a separate post so people can see it, as I know this may interest many who are interested in reducing the install.wim size. When playing with my Windows 8.1 image last night, I read about converting the WIM image to ESD can reduce the file. After doing what I needed to do, my Install.wim file was 2.72 GB. Converting this to ESD reduced this down to 1.80 GB - nice! I wondered if the file size would go back to 2.72 GB if I converted it back to a WIM file, but, surprisingly, I ended up with a 2.26 GB Install.wim. I'm not sure exactly what happened, but both the ESD and reduced WIM ISO images install perfectly. Are there are reasons not to use ESD over WIM? Has anything been lost?
You can rename the by prefixing the update name as 01-Windows8.1-KBXXXXX-x64.msu 02-Windows8.1-KBXXXXX-x64.msu and try out
The resulting size of ESD<->WIM conversion won't always be the same. It doesn't matter whether you use a ESD or WIM Image for Installation, But if you want to service the image again then the image should be in WIM format.
NetFX35 for Win8.1 should be in Mega, last updated Dez. 18... Did you extract that 7z-file into /Packs? Else use original MS-Image of Win81, it contains NetFX3.5 (thats where Toolkit looks first).
Make a screenshot of your Packs/NetFX35/w81/x64 folder. MUI contains full package AND all languages. (My infos are abit outdated, I last integrated NetFX35 in Oct.2016 in Win81, but struct in Archive was the same.) Maybe Toolkit6.4 has a bug (expecting now something different in folder).
Wait for some time today I will be releasing a new version with a many fixes and also with the corrected and simplified NETFX35 Pack for W10 and also other packs too.
Updated the ToolKit to v6.5 Haven't checked the script with Server Core Editions, So If anyone are using it then just try out and let me know if there are any bugs in the ToolKit. Changelog v6.5 + Updated ToolKit's Bin Folder with WimLibImagex Latest Binaries. + Added Fix for Server Core Edition Detection (Thanks to MDL Member Kenafri). + Fixed a Bug in the Feature "Integrate .NET Framework 3.5", Where the ToolKit Failed to Find the .NET Framework 3.5 Source Files Inside the Pack Folder. + Updated the Microsoft .NET Framework 3.5 Pack with Proper Version and Simpler Naming for Windows 10 Source OS. + Fixed a Bug in the Feature "Integrate Internet Explorer 11 Updates", Where the Internet Explorer 11 Update was not Extracted Correctly. + Added a Feature "Integrate Windows Management Framework (WMF) 5.1". + Added Windows Management Framework 5.1 Pack for MSMG ToolKit for Windows 7/Server 2008 R2/ThinPC/Windows 8.1/Server 2012 R2 Source OS. - Removed the Feature "Integrate Windows Management Framework 3.0, 4.0 & 5.0". - Removed the Windows Management Framework 3.0, 4.0 & 5.0 Pack for MSMG ToolKit. + Updated the Feature "Integrate WHD Updates" to Reflect the WHD Hotfix Repository Update List. + Updated the Feature "Remove Windows Components" to Remove "dmwappushsvc" Service When Microsoft Telemetry Services Components Are Removed for Windows 10 Source OS. + Updated the Feature "Remove Windows Components" to Remove Microsoft OneDrive Component for Windows 10 Redstone 2 Creators Update Preview Source OS. + Fixed Minor Bugs in the ToolKit (Thanks to MDL Member Kenafri). + Optimized ToolKit Code.
@MSMG Could you find the time to fix the Apps path that gets set incorrectly (win10\win10\)? It happens on x86 only. Cheers.