It's not fails, Just need to integrate SSU twice before integrate CU. I tried this by simple command line dism.
Even with your logic integrating SSU twice also fails the CU integration using it's update.mum The Toolkit script uses the same command-line DISM to integrate updates. Code: ##################Starting Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 1 Image Architecture : x64 Image Version : 10.0.22621.1.0 ------------------------------------------------------------------------------- ####Processing WHD General Updates Packages#################################### ------------------------------------------------------------------------------- Creating WHD General Updates Temporary folder... Extracting Update Package files to Temporary folder... Finished Extracting Update Package files to Temporary folder... ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Install Image############# ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ ------------------------------------------------------------------------------- Integrating Windows 11 Servicing Stack Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 11 Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.105.1.7 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f0988 Error: 0x800f0988 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at D:\Work\Toolkit\Logs\Dism.txt ------------------------------------------------------------------------------- Generating WHD General Updates Integration Log File... ------------------------------------------------------------------------------- Writing WHD General Updates Integration Log. ------------------------------------------------------------------------------- ####Cleaning Up Temporary files & Folders###################################### ------------------------------------------------------------------------------- Cleaning Up WHD General Updates Temporary folder. ------------------------------------------------------------------------------- ##################Finished Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . .
I did not test. But I also thought it should work by running the command once again in the sequence. But I only thought that because the logic would be compatible with a message presented in the first execution of the command. Will it need to be unmounted (commit/saving source) and mounted again?
Leave SSU it got integrated despite that message, it was the CU failing to integrate. Just found out that the PSFX converted full cab extracted folder got integrated using the Toolkit, so compared the extracted contents between full cab and the PSFX extracted folder then it was missing some folders, the same PSFExtractor command works for W11 21H2 CU. Then checked with psfx2cab_CLI.cmd they have added some new code to make it work for W11 22H2 CU, have modified the Toolkit script to adapt the changes will test and see if it works. And one more thing, the Windows 11 22H2 updates filename now starts with Windows11.0-KBXXXXX and not Windows10.0-KBXXXXX, this change was the thing breaking the integration. Edit: It works now after making changes Code: =============================================================================== MSMG ToolKit - Integrate WHD General Updates to Windows Setup Install Image =============================================================================== ------------------------------------------------------------------------------- ##################Starting Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 1 Image Architecture : x64 Image Version : 10.0.22621.1.0 ------------------------------------------------------------------------------- ####Processing WHD General Updates Packages#################################### ------------------------------------------------------------------------------- Creating WHD General Updates Temporary folder... Extracting Update Package files to Temporary folder... Finished Extracting Update Package files to Temporary folder... ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Install Image############# ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ ------------------------------------------------------------------------------- Integrating Windows 11 Servicing Stack Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 11 Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25140.1000 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.105.1.7 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Generating WHD General Updates Integration Log File... ------------------------------------------------------------------------------- Writing WHD General Updates Integration Log. ------------------------------------------------------------------------------- ####Cleaning Up Temporary files & Folders###################################### ------------------------------------------------------------------------------- Cleaning Up WHD General Updates Temporary folder. ------------------------------------------------------------------------------- ##################Finished Integrating WHD General Updates##################### ######################to Windows Setup Install Image########################### ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . .
"ToolKitHelper_Preview.exe" should I move this to the folder or rename this file to "ToolKitHelper.exe" and overwrite it?
Can't seem to get my ISO to work on VirtualBox. It say "no drivers are found" when I try to install it on a VM. Am I missing something? Selected ISO and all indeces (using en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f) Integrated features (DaRT and DirectX 9 only) Integrated Windows updates on install, recovery and boot (downloaded using WHD, all under 19041 and v21H2 only) Integrated .NET Framework 3.5 Applied and saved changes Created the ISO No errors occurred, AFAIK, from the whole integration process.
Yes, rename this file to "ToolKitHelper.exe" , copy it and place it with the replacement of the old file at the path: Toolkit\Bin\ UPD. I'm sorry, it so happened that we sent our messages at the same time as @MSMG
Did you copied the required Setup DU cab to WHD folder, it is required to update the Setup DVD sources folder to match the updated files added to boot. or You can use the [3] Integrate Windows Setup Media Updates menu to update the Setup DVD sources folder or Extract the DU Setup cab file to <sources> folder and remake the ISO.
Retried the integration earlier, did this one after integrating .NET, and it worked. Thanks a lot. On which part/step do I need to do this, anywhere after integrating updates? EDIT: Noticed that it download "Windows Malicious Software Removal Tool x64 - v5.102 (KB890830)" when I run Windows Update on the VM. Can I just download this from the MS update catalog and plop it down on the same folder as the updates? Or is there an option in the tool to integrate this?
The Microsoft provides Dynamic Update for Windows Setup source DVD, when you add updates to WHD folder, do add this DU for Setup update cab file to it, the Toolkit will extract the cab file to sources folder. For Windows 11 22000 the latest DU for Setup cab file is KB5014675. Windows Malicious Software Removal Tool update comes in exe format, though it can be added to the image but it requires also a reg key to be added to image, this reg key changes for each month so it's not been added to integrate in Toolkit.
It's not fail for integrating CU on my PC, Just SSU .2 or .160 both of them are unstable. I have a proof, See screenshots. Spoiler: .160 Code: C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\160\SSU" Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_160~31bf3856ad364e35~amd64~~22621.160.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_160 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\160\SSU" Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_160~31bf3856ad364e35~amd64~~22621.160.1.0 [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\160\CU" Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.160.1.3 [==========================100.0%==========================] The operation completed successfully. Spoiler: Screenshots .160 Spoiler: .105 Code: C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\105\SSU" Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_2 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\105\SSU" Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~22621.2.1.1 [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32>Dism.exe /Image:"H:\Work\Mount" /Add-Package /PackagePath:"D:\Test\105\CU" Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.105.1.7 [==========================100.0%==========================] The operation completed successfully. Spoiler: Screenshots .105