Has anyone tried modifying the script to use MMRCs on LTSC 2021 build? Want to try integrating dolby with this tool
Updated the Toolkit to v12.7 Spoiler: Changelog.txt v12.7 + Updated Toolkit's Bin folder with Windows 11 v22H2 Insider Preview WADK (v10.0.25206.1000) Tools. + Updated the Toolkit to support Windows 11 v22H2 (10.0.22622) Moment 1 Insider Preview Source OS. + Updated the Toolkit to support Windows 11 v22H2 (10.0.22623) Moment 2 Insider Preview Source OS. + Updated the Microsoft .NET Framework 4.8 Pack (Windows 7/Server 2008 R2) with .NET 4.8 KB5017036 (4.8.4556.2) (Thanks to MDL Member : abbodi1406). + Updated the Microsoft .NET Core 3.1 Desktop Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Microsoft .NET Core 3.1 Desktop Runtime 3.1.28 Runtime. + Updated the Microsoft .NET 6 Desktop Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Microsoft .NET Desktop Runtime 6.0.9 Runtime. + Updated the Microsoft Visual C++ Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with VC++ 2022 (14.34.31823) Runtime (Thanks to MDL Member : abbodi1406). + Updated the Feature "Integrate WHD Updates" to support integrating Windows 11 v22H2 (10.0.22622) Moment 1 Feature Enablement Package. + Updated the Feature "Integrate WHD Updates" to support integrating Windows 11 v22H2 (10.0.22623) Moment 2 Feature Enablement Package. + Updated the Feature "Remove Windows Component" - Split Edge WebView from Edge Chromium Component for Windows 11 Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809/LTSC2019 (v10.0.17763.1/v10.0.17763.3406 [KB5017315]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1903 (v10.0.18362.1) & v1903/v1909 (v10.0.1836x.2274 [KB5013945]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2 (v10.0.1904x.2006 [KB5017308]), LTSC2021 (v10.0.19044.1288/v10.0.19044.2006 [KB5017308]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.978 [KB5017328]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v22H2 (v10.0.22621.1/v10.0.2262x.521 [KB5017321]) Source OS. + Optimized the Toolkit code (Thanks to MDL Member : inTerActionVRI).
I think about that since the beginning. The options are misleading as they are Just change them to "Do you want to cleanup the installation image (resetbase)?" and "Do you want to cleanup the toolkit temporary folder?" Would make a lot of more sense.
Would this image work? Microsoft Windows 11 [10.0.22621.525], Version 22H2 (Updated September 2022) - Original images from Microsoft MSDN [Ru] You have *.521 in the changes, but in the image with MSDN *.525...
It is recommended to use UUP dump to build 22621.1 and install CU by yourself. This can avoid re-downloading the ISO every time Microsoft updates, and can also generate a specified version of the system at will.
On UUP dump, the website has the message "This build requires using Windows 10, version 2004 or later for the ISO to be properly created. Scripts for other platforms will output a broken ISO" when downloading the 22621.x images. Does this mean that the ToolKit needs to be ran on Windows 10 2004 or later when working with Windows 11 images? I ask because I am currently running 1909.
Not needed. Because the Toolkit uses the Windows 11 v22H2 Insider Preview WADK. And UUP dump is to use the DISM of the current system.
Yes, you can use the .525 source image, checked with this CU and there are no changes related to the removed components.
Trying to update 22622.601 to 22622.730. DaRT integration works. But when I start integrating WHD Updates, the program closes. It´s the second time it happens. Using latest 12.7. When 22622 came out, I was using Toolkit 12.5 (I think), and everything worked fine.
It is more convenient for me to use the image already with an integrated update. I don't download the image with every update. I downloaded the original image with the update, made my own assembly and can be forgotten for a year. Got it. Thanks to.
Extract the ToolKit to the Toolkit_v12.7 folder as usual, then rename this folder to something very short - such as T. Now move the T folder to the root of your C: drive, so the path is C:\1 which contains all the ToolKit files.