update1: Test with MSMG toolkit 11.2, bug seems fixed. I‘m sure that's a bug of the Toolkit. By using "Integrate Windows Updates" everything works fine. Code: =============================================================================== MSMG ToolKit - Integrate Windows Updates =============================================================================== ------------------------------------------------------------------------------- ####Starting Integrating Windows Updates####################################### ------------------------------------------------------------------------------- Image : Install.wim Image Indexes : 1-1 Image Architecture : x64 Image Version : 10.0.17763.316.0 ------------------------------------------------------------------------------- ####Processing Windows Updates Packages######################################## ------------------------------------------------------------------------------- Creating Windows Updates Packages Temporary folder... Extracting .CAB Package files to Temporary folder... Finished Extracting .CAB Package files to Temporary folder... ------------------------------------------------------------------------------- ####Integrating Windows Updates################################################ ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ Deployment Image Servicing and Management tool Version: 10.0.20279.1 Image Version: 10.0.17763.316 Processing 1 of 1 - Adding package Package_for_KB4598480~31bf3856ad364e35~amd64~~17763.1690.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Generating Windows Updates Integration LOG File... ------------------------------------------------------------------------------- Writing Windows Updates Integration Log file. ------------------------------------------------------------------------------- Cleaning Up Temporary Files & Folders... ------------------------------------------------------------------------------- Cleaning Up Windows Updates Temporary folder. ------------------------------------------------------------------------------- ####Finished Integrating Windows Updates####################################### ------------------------------------------------------------------------------- =============================================================================== Code: =============================================================================== MSMG ToolKit - Integrate Windows Updates =============================================================================== ------------------------------------------------------------------------------- ####Starting Integrating Windows Updates####################################### ------------------------------------------------------------------------------- Image : Install.wim Image Indexes : 1-1 Image Architecture : x64 Image Version : 10.0.17763.316.0 ------------------------------------------------------------------------------- ####Processing Windows Updates Packages######################################## ------------------------------------------------------------------------------- Creating Windows Updates Packages Temporary folder... Extracting .CAB Package files to Temporary folder... Finished Extracting .CAB Package files to Temporary folder... ------------------------------------------------------------------------------- ####Integrating Windows Updates################################################ ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ Deployment Image Servicing and Management tool Version: 10.0.20279.1 Image Version: 10.0.17763.316 Processing 1 of 7 - Adding package Package_for_KB4486153~31bf3856ad364e35~amd64~~10.0.1.3106 [==========================100.0%==========================] Processing 2 of 7 - Adding package Package_for_KB4486155~31bf3856ad364e35~amd64~~10.0.1.2752 [==========================100.0%==========================] Processing 3 of 7 - Adding package Package_for_KB4535680~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] Processing 4 of 7 - Adding package Package_for_KB4577586~31bf3856ad364e35~amd64~~10.0.1.6 [==========================100.0%==========================] Processing 5 of 7 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4300.1 [==========================100.0%==========================] Processing 6 of 7 - Adding package Package_for_KB4589208~31bf3856ad364e35~amd64~~10.0.2.4 [==========================100.0%==========================] Processing 7 of 7 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.1728.1.6 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Generating Windows Updates Integration LOG File... ------------------------------------------------------------------------------- Writing Windows Updates Integration Log file. ------------------------------------------------------------------------------- Cleaning Up Temporary Files & Folders... ------------------------------------------------------------------------------- Cleaning Up Windows Updates Temporary folder. ------------------------------------------------------------------------------- ####Finished Integrating Windows Updates####################################### ------------------------------------------------------------------------------- ===============================================================================
Is there any difference in integrating updates using direct .cab file and extracted the cab folder? Both uses the DISM to integrate the updates, if the Features can be seen through DISM /Get-Features command or through Program and Features->Turn Windows Features on or off, then the integration is proper. Which edition are you using?
Windows LTSC 2019 x64 ZH-CN source: cn_windows_10_enterprise_ltsc_2019_x64_dvd_9c09ff24.iso Well, The 11.2 doesn't have such a bug now, WHD also works fine.
Sir the changes stated in 1st and 2nd point is with respect to windows 10 version 14393 and not for version 17763.1. Correct me if I am wrong. Thank You
- Updated the Microsoft .NET Framework 4.8 Pack (Windows 10/Server 2016/2019) applies to W10 14393 - 17763 both Server/Client. - Updated the Microsoft .NET Framework 4.8 Pack (Windows 7/Server 2008 R2) for Windows 7 Client/Server 2008R2
Good afternoon. When I try to add the Windows 10 Enterprise LTSC 2019 Windows Mixed Reality Pack, the application just closes.
The KB4577586 is a Remove Adobe Flash Player update which is available in .msu format not .exe For which OS are you trying to add this update to?
Ok here's the fix change the below text in the script file and save it :IntWindowsMixedReality to :IntWMR Code: =============================================================================== MSMG ToolKit - Integrate Windows Mixed Reality =============================================================================== ------------------------------------------------------------------------------- ####Starting Integrating Windows Mixed Reality################################# ------------------------------------------------------------------------------- Image : Install.wim Image Index : 8 Image Architecture : x64 Image Version : 10.0.17763.1.0 ------------------------------------------------------------------------------- ####Integrating Windows Mixed Reality########################################## ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 8]============================ Deployment Image Servicing and Management tool Version: 10.0.20279.1 Image Version: 10.0.17763.1 Processing 1 of 1 - Adding package Microsoft-Windows-Holographic-Desktop-FOD-Package~31bf3856ad364e35~amd64~~10.0.17763.1 [===========================99.9%========================= ] The operation completed successfully. ------------------------------------------------------------------------------- ####Finished Integrating Windows Mixed Reality################################# ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . .
I found what makes the bug happened for Integrate Microsoft .NET Framework 3.5. The MSMG toolkit have to work with Microsoft .NET Framework 3.5. in the “DVD\sources\sxs” path otherwise it won't work fine. microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab If I remove all files in the “DVD\sources\sxs” the Integrating will cause error.
When using [2] Integrate -> [3] Windows Features -> [1] Microsoft .NET Framework 3.5 The Toolkit first looks for folder sources\sxs> if present then assigns the path based on the source OS, version. If not present then looks for the path <Packs\NetFX35\w10\10.0.17763> and assigns the path based on the source OS, version. Code: :: Setting Microsoft .NET Framework 3.5 Feature Pack folder path according to Source Image Architecture if exist "%DVD%\sources\sxs" ( if "%SelectedSourceOS%" equ "w81" set "NetFX35=%DVD%\sources\sxs" if "%SelectedSourceOS%" equ "w10" ( if "%ImageBuild%" leq "16299" set "NetFX35=%DVD%\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab" if "%ImageBuild%" geq "17134" set "NetFX35=%DVD%\sources\sxs\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~%PackageArchitecture%~~.cab" ) ) else ( if "%SelectedSourceOS%" equ "w81" set "NetFX35=%NetFX35%\%SelectedSourceOS%\%ImageArchitecture%" if "%SelectedSourceOS%" equ "w10" set "NetFX35=%NetFX35%\%SelectedSourceOS%\10.0.%ImageBuild%\Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~%PackageArchitecture%~~%ImageVersion%.%PackageServicePackBuild%.cab" ) Then it checks for Microsoft .NET Framework 3.5 cab file based on the above selected path, if the cab file is not present then it will complain about the missing files. If the cab file is found then copies the cab file to temporary location and renames the file to work with DISM for Windows 10 Source OS Code: if "%SelectedSourceOS%" equ "w10" if "%ImageBuild%" geq "17763" if "%NetFX35%" neq "%DVD%\sources\sxs\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~%PackageArchitecture%~~.cab" if exist %NetFX35% ( copy /y %NetFX35% "%Temp%\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~%PackageArchitecture%~~.cab" >nul set "NetFX35=%Temp%\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~%PackageArchitecture%~~.cab" ) If using Integrate Windows Hotfix Updates Pack method the Toolkit looks for the .NET Framework 3.5 cab files in <WHD\w10\x64\10.0.17763> folder. Edit: Understood what's the issue is : - If the SxS folder is not present and the Packs\NetFX35 folder contains the cab files it will work. - If the SxS folder is present with .NET 3.5 cab files then it works. - If the SxS folder is empty then it will complain. This is a tricky thing since for Windows 81 the .NET FX 3.5 files are uncompressed in a folder, for Windows 10 v16299 and above the .NET FX 3.5 file is a cab file but differs in filename.
Ok here's a quick fix for the above issue, will add the fix in next release, just modify the below code Code: :: Setting Microsoft .NET Framework 3.5 Feature Pack folder path according to Source Image Architecture if exist "%DVD%\sources\sxs" ( if "%SelectedSourceOS%" equ "w81" set "NetFX35=%DVD%\sources\sxs" if "%SelectedSourceOS%" equ "w10" ( if "%ImageBuild%" leq "16299" set "NetFX35=%DVD%\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab" if "%ImageBuild%" geq "17134" set "NetFX35=%DVD%\sources\sxs\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~%PackageArchitecture%~~.cab" ) ) else ( if "%SelectedSourceOS%" equ "w81" set "NetFX35=%NetFX35%\%SelectedSourceOS%\%ImageArchitecture%" if "%SelectedSourceOS%" equ "w10" set "NetFX35=%NetFX35%\%SelectedSourceOS%\10.0.%ImageBuild%\Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~%PackageArchitecture%~~%ImageVersion%.%PackageServicePackBuild%.cab" ) to Code: :: Setting Microsoft .NET Framework 3.5 Feature Pack folder path according to Source Image Architecture if "%SelectedSourceOS%" equ "w81" ( if exist "%DVD%\sources\sxs" ( set "NetFX35=%DVD%\sources\sxs" ) else ( set "NetFX35=%NetFX35%\%SelectedSourceOS%\%ImageArchitecture%" ) ) if "%SelectedSourceOS%" equ "w10" ( if exist "%DVD%\sources\sxs\*.cab" ( if "%ImageBuild%" leq "16299" set "NetFX35=%DVD%\sources\sxs\microsoft-windows-netfx3-ondemand-package.cab" if "%ImageBuild%" geq "17134" set "NetFX35=%DVD%\sources\sxs\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~%PackageArchitecture%~~.cab" ) else ( if "%SelectedSourceOS%" equ "w10" set "NetFX35=%NetFX35%\%SelectedSourceOS%\10.0.%ImageBuild%\Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~%PackageArchitecture%~~%ImageVersion%.%PackageServicePackBuild%.cab" ) )
Yes. you´re right. .msu. windows10.0-kb4577586-x64_c9bb49df325c20ddc147137b3f769fa44d800dde.msu Windows 10 19042.782 In which folder do I copy it?
Copy all updates to <WHD\w10\x64\10.0.19041> FYI The current version of Toolkit doesn't support removing Windows Components for 19042.782 build, supported build is only 19042.745
I´m searching for Microsoft Windows Recovery Environment (Dart) and Language Pack in spanish to integrate to my ISO. I found the download links some time ago, but now, I cannot find it anymore.