If you integrate .net 3.5 and then integrate the updates you will not be able to do the Cleanup/ResetBase of the image because .net creates pending operations. To integrate the updates in just one step is necessary after integrating .net 3.5 and updates booting the image in a VM in audit mode to do the pending operations after capturing the image and doing the Cleanup/ResetBase.
=============================================================================== MSMG ToolKit - Integrate Microsoft Games =============================================================================== Microsoft Games Pack file "CariocaRummy_pt-BR.tpk" not found... Please Copy Microsoft Games Pack file to <Packs\Games> folder... =============================================================================== =============================================================================== MSMG ToolKit - Integrate WHD General Updates to Windows Setup Boot, Install & Recovery Images =============================================================================== ------------------------------------------------------------------------------- ##################Starting Integrating WHD General Updates##################### ##############to Windows Setup Boot, Install & Recovery Images################# ------------------------------------------------------------------------------- Image : Boot.wim | Install.wim | WinRE.wim Image Indexes : 1, 2 | 1 | 1 Image Architecture : x64 Image Build : 10.0.15063.0 ------------------------------------------------------------------------------- ####Processing WHD General Updates Packages#################################### ------------------------------------------------------------------------------- Creating WHD General Updates Temporary folder... Extracting .CAB Package files to Temporary folder... Finished Extracting .CAB Package files to Temporary folder... ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Boot Image################ ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update to Boot Image ---------------------------------[Index : 1]----------------------------------- Deployment Image Servicing and Management tool Version: 10.0.16190.1000 Image Version: 10.0.15063.0 Processing 1 of 1 - Adding package Package_for_KB4020821~31bf3856ad364e35~amd64~ ~10.0.1.0 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at D:\Msmg\Logs\Dism.txt ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update to Boot Image ---------------------------------[Index : 2]----------------------------------- Deployment Image Servicing and Management tool Version: 10.0.16190.1000 Image Version: 10.0.15063.0 Processing 1 of 1 - Adding package Package_for_KB4020821~31bf3856ad364e35~amd64~ ~10.0.1.0 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at D:\Msmg\Logs\Dism.txt ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Install Image############# ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update to Install Image ---------------------------------[Index : 1]----------------------------------- Deployment Image Servicing and Management tool Version: 10.0.16190.1000 Image Version: 10.0.15063.0 Processing 1 of 1 - Adding package Package_for_KB4020821~31bf3856ad364e35~amd64~ ~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Recovery Image############ ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update to Recovery Image ---------------------------------[Index : 1]----------------------------------- Deployment Image Servicing and Management tool Version: 10.0.16190.1000 Image Version: 10.0.15063.0 Processing 1 of 1 - Adding package Package_for_KB4020821~31bf3856ad364e35~amd64~ ~10.0.1.0 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at D:\Msmg\Logs\Dism.txt ------------------------------------------------------------------------------- ####Generating WHD General Updates Integration Log Files####################### ------------------------------------------------------------------------------- Writing WHD General Updates Integration [Boot.wim, Index : 1] Log... Writing WHD General Updates Integration [Boot.wim, Index : 2] Log... Writing WHD General Updates Integration [Install.wim, Index : 1] Log... Writing WHD General Updates Integration [WinRE.wim, Index : 1] Log... ------------------------------------------------------------------------------- ####Cleaning Up Temporary files & Folders##################################### ------------------------------------------------------------------------------- Cleaning Up WHD General Updates Temporary folder... ------------------------------------------------------------------------------- ##################Finished Integrating WHD General Updates##################### ##############to Windows Setup Boot, Install & Recovery Images################# ------------------------------------------------------------------------------- ===============================================================================
I agree, tell MSMG I am not the author. Although he did link to my usage guide video which has these steps detailed in that video so thanks to him for that. I will update the video soon after @MSMG confirms the question which I asked him.
Just as an FYI, @MSMG, I just performed this process and I still end up with the [DELETED] folder in my INSTALL.WIM.
Yes I know about this issue and using he Quotation marks will fix it but the problem is when assigning the DISM path with DISM parameters based upon the HOST OS, which needs to fixed.
The Usage order for ToolKit has been changed many times due to Windows 10 and it's CU's In my previous reply, I advised to integrate update once more as a last step only to fix the update being offered again through WU. For Windows 7 OS 1) Integrate the Windows Features. 2) Integrate the Language Pack if required. 3) Integrate the Windows Updates. 4) Integrate the Custom Features if required. 5) Remove the Windows Components you don't want. 6) Apply Changes 7) Create the ISO For windows 8 .1 OS 1) Integrate the Windows Features except NET Framework 3.5. 2) Integrate the Language Pack if required. 3) Integrate the Windows Updates. 4) Integrate the Custom Features if required. 5) Remove the Windows Apps you don't want. 6) Remove the Windows Components you don't want. 7) Apply Changes, this will perform the Cleanup 7) Re-Mount the Source 8) Integrate .NET Framework 3.5. 9) Integrate the .NET Framework 3.5 Updates. 10) Apply Changes 11) Create the ISO For windows 10 OS, the order can change based on the CU, if the .NetFX35 updates are offered through WU then we may need to follow this order or you can skip the step #9. 1) Integrate the Windows Features except NET Framework 3.5. 2) Integrate the Language Pack if required. 3) Integrate the Windows Updates. 4) Integrate the Custom Features if required. 5) Remove the Windows Apps you don't want. 6) Remove the Windows Components you don't want. 7) Apply Changes, this will perform the Cleanup 7) Re-Mount the Source 8) Integrate .NET Framework 3.5. 9) Integrate the Cumulative Update to update .NET Framework 3.5. 10) Apply Changes 11) Create the ISO If you totally want to integrate the CU after the OS Installation, at present for RS2, it's working this way and it's not restoring any removed components. One advantage of Installing CU after the OS Installation is that if you create a backup of master image for restore purpose then Installing a new CU later will avoid the Image Cleanup which usually takes a lot of time. But Who knows what will the future CU's will do again we may have change the order as it happened in RS1.
1) Don't use the Games Pack Integration as I have removed the games pack due to a bug in it. 2) Will check out.
In the latter BUILD of Windowqs 10 16193, the MSMG ToolKit script does not go beyond the screen that it requires to advance by pressing letter A. Reading posts explaining how to activate in GPEDIT.MSC however you are unable to enable NETFX35 installation. Is there a way to use Toolkit on this build ?????? Thanks for a Vs feedback. Bye
I'm running RS2. Can't I just apply non Cumulative update & Cumulative update both together in last step or does it have to be done separate.
You can do it anyway if you don't want the Image Cleanup, that is the main thing here which is causing so much issues.