For personal organization, I rename the updates, downloaded from Microsoft Catalog, like this: Update KB123456789 (Windows 10 x64).msu. Since MSMG Toolkit has errors with long names (this is a huge >>>Windows problem<<<, which I hate, including not supporting : and ?), I renamed the file in KB123456789.msu format. From the beginning, I believed it was a name error and was already thinking of leaving the original name with SHA-1 hash. Thank you very much for helping me. I have been testing the installation for a few days now and it is perfect. I extracted the .msu file from the July update and put the .cab files in the update folder as you said. It worked normally. I installed Windows on Disk A:\, instead of C:\, enabled compression and also enabled CompactOS getting a Windows 10 22H2 Pro x64 installation, updated to July 2023, using less than 5 GB of storage on the SSD.
Only when removing some specific Components. Not for integrating things. Use the specified supported ISO Builds. Read about it in changelog.txt in your Toolkit folder. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2/v22H2 (v10.0.1904x.3208 [KB5028166]) Source OS. EDITED: @tempdrive1 informed that you will get some issue when integrating updates in 19041.1 (maybe some other build.1) through Updates option. Use WHD Updates option.
This issue can affect any Windows build for which the update has newer requirements than what comes with the image you are trying to integrate it into. Basically the WUpdates (selecting [4] Windows Updates) code part in Toolkit.cmd needs to be adjusted to extract SSU from the update you are trying to integrate. And when the integration part takes place using the DISM command, you have to make sure that SSU comes before anything. You must change the code (I have given some indications on how to) as it is destined to fail for the intended integration process. If, for any reason, you need help with it, happy to provide some feedback on it. I have also given a workaround option for that (you extract SSU*.cab into the corresponding Updates subfolder and let the integration process complete for it before putting the intended update in the folder for integration), and it is already confirmed that it works. I also recommend to let users use any naming convention, since DISM will not integrate unsupported updates anyway, and people could accidentally name the wrongly (e.g. downloading x86 update but saved as x64 filename), so this check is only worth so much.
MSMG Toolkit v13.5 - Windows 10 22h2 I tried remove all components. Removing of CloudExperienceHost breaks installation after reboot (setup part). Maybe help using of unattended.xml file. Spoiler: MSMG said: Note: have added some new components for removal, the below components removal also comes with issues which the user needs to deal with. ClientCBS - Will remove the user experience pack, breaks Input App, Windows 11 Start menu and Screen clipping. For Windows 11 v21H2 it will restore the Windows 10 Start menu, Explorer and Taskbar., also can restore some resources files for some system apps. CloudExperienceHost - Requires a full unattended installation without internet connectivity and requires SkipMachineOOBE enabled in unattended xml. If removing this component then do not add OOBE updates to the image. InputApp - Breaks the touch input application, touch keyboard functionality. ShellExperienceHost - Breaks Start Menu and taskbar fly-outs popups for battery calendar, clock, sound, network, action center for Windows 10 v17763-v18363 Breaks Taskbar fly-outs popups for battery calendar, clock, sound, network, action center for Windows 10 v1904x and Windows 11 StartMenuExperienceHost - Breaks Start Menu, for Windows 11, a error dialog will appear on first boot, once the Log-out button in the dialog box is clicked it will logout the OS, then the user needs to login to fix this error. This is due to Windows 11's default show Start menu on logon option, if anyone finds a tweak to disable it, will add to the removal process. UndockedDevKit - Will remove Setting -> System -> About window page. when this component is removed alone without the above components the windows Setup completes properly else it will get stuck with a blank screen at the setup completion stage, then the user needs to reboot once to fix it. So haven't added this component in the Toolkit's removal menu, if the user want to remove it then they can use the list or manual method.
Done similar testing, no issue other than screen stuck at blank screen at the end of setup during installation https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1299#post-1798626
An option I don't use. The other does exactly what you say. Why change one that must have another specific purpose for that one, if the option available under the name of WHD works. Should the other option simply be removed? Should it be blocked from some build? I don't know, I just know what I told you here: The MSMG that will decide. Let's wait then. Are we making a storm in a glass of water? Let's make a juice with this storm. I was even going to say that I had no problems in the test I just did. Spoiler: integrating 19045.3083 feature updates in 19041.1 Code: =============================================================================== MSMG ToolKit - Integrate WHD General Updates to Windows Setup Boot, Install & Recovery Images =============================================================================== ------------------------------------------------------------------------------- ##################Started Integrating WHD General Updates###################### ##############to Windows Setup Boot, Install & Recovery Images################## ------------------------------------------------------------------------------- Image : Boot.wim | Install.wim | WinRE.wim Image Index : 1, 2 | 1,2 | 1 Image Architecture : x64 Image Version : 10.0.19041.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 Boot Image################ ------------------------------------------------------------------------------- =============================[Boot.wim, Index : 1]============================= ------------------------------------------------------------------------------- Integrating Windows 10 Servicing Stack Update... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3385~31bf3856ad364e35~amd64~~19041.3385.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3391.1.11 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 v22H2 Feature Enablement Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.3391 Processing 1 of 1 - Adding package Package_for_KB5015684~31bf3856ad364e35~amd64~~19041.1799.1.2 [==========================100.0%==========================] The operation completed successfully. =============================[Boot.wim, Index : 2]============================= ------------------------------------------------------------------------------- Integrating Windows 10 Servicing Stack Update... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3385~31bf3856ad364e35~amd64~~19041.3385.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3391.1.11 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 v22H2 Feature Enablement Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.3391 Processing 1 of 1 - Adding package Package_for_KB5015684~31bf3856ad364e35~amd64~~19041.1799.1.2 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 Safe OS Dynamic Update... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.3391 Processing 1 of 1 - Adding package Package_for_KB5027389~31bf3856ad364e35~amd64~~19041.3083.1.4 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 Dynamic Update for Sources... ------------------------------------------------------------------------------- Copying Windows 10 Dynamic Update for Sources to <DVD> folder. ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Install Image############# ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ ------------------------------------------------------------------------------- Integrating Windows 10 Servicing Stack Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3385~31bf3856ad364e35~amd64~~19041.3385.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3391.1.11 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 v22H2 Feature Enablement Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.3391 Processing 1 of 1 - Adding package Package_for_KB5015684~31bf3856ad364e35~amd64~~19041.1799.1.2 [==========================100.0%==========================] The operation completed successfully. ===========================[Install.wim, Index : 2]============================ ------------------------------------------------------------------------------- Integrating Windows 10 Servicing Stack Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3385~31bf3856ad364e35~amd64~~19041.3385.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 Cumulative Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3391.1.11 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 v22H2 Feature Enablement Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.3391 Processing 1 of 1 - Adding package Package_for_KB5015684~31bf3856ad364e35~amd64~~19041.1799.1.2 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- ####Integrating WHD General Updates to Windows Setup Recovery Image############ ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Integrating Windows 10 Servicing Stack Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_3385~31bf3856ad364e35~amd64~~19041.3385.1.0 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 Safe OS Dynamic Update... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_KB5027389~31bf3856ad364e35~amd64~~19041.3083.1.4 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Integrating Windows 10 v22H2 Feature Enablement Update Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25905.1000 Image Version: 10.0.19041.3083 Processing 1 of 1 - Adding package Package_for_KB5015684~31bf3856ad364e35~amd64~~19041.1799.1.2 [==========================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 Boot, Install & Recovery Images################# ------------------------------------------------------------------------------- =============================================================================== It is all good for x64 pt-BR ISO. After all, I didn't ask you directly, but I had let it be understood that I thought the problem also occurred for the WHD option. Here: But apparently, something you said earlier I didn't notice and something I told you you didn't notice either. I had already said that this option was an option for another purpose. I just know it's been around for a long time. Maybe it's just for integration of other non-cumulative updates. I'm not going to make any more assumptions. Guys, to integrate the updates, just use the sequence of options: Avoid [1] Integrate Windows Updates. 1. Place the updates files in WHD correct folder for your build. 2. follow the bellow sequence for integrating [2] Integrate --> [4] Windows Updates --> [Y] W A R N I N G --> [2] Integrate WHD Update Pack --> [1] Integrate WHD General Updates --> Choose your option as per the wim images you mounted. 3. after finished Updates integration, follow the bellow sequence for updating the Windows Media Manual Setup. [2] Integrate --> [4] Windows Updates --> [Y] W A R N I N G --> [2] Integrate WHD Update Pack --> [2] Integrate Windows Setup Media Updates[/spoiler]
Yep, there is the function for making the autounattend.xml in Main Menu. [5] unattended Inside the Toolkit.cmd It is a txt file, open it with notepad.
Oh hell no. I use it exclusively Had a play with WHD and it does not offer any updates relevant to my systems. 22 updates and not one of them any good.
As long as they aren't exclusive to the cumulative update ad I've put in the image above. What types of updates do you use in this option?
Hi @MSMG Is it possible to remove below capabilites via MSMG ToolKit? Code: App.StepsRecorder~~~~0.0.1.0 App.Support.QuickAssist~~~~0.0.1.0 DirectX.Configuration.Database~~~~0.0.1.0 Hello.Face.18967~~~~0.0.1.0 Hello.Face.Migration.18967~~~~0.0.1.0 Language.Handwriting~~~en-US~0.0.1.0 Language.Speech~~~en-US~0.0.1.0 Language.TextToSpeech~~~en-US~0.0.1.0 MathRecognizer~~~~0.0.1.0 Microsoft.Windows.PowerShell.ISE~~~~0.0.1.0 Microsoft.Windows.WordPad~~~~0.0.1.0 OneCoreUAP.OneSync~~~~0.0.1.0 OpenSSH.Client~~~~0.0.1.0 Print.Fax.Scan~~~~0.0.1.0 Windows.Client.ShellComponents~~~~0.0.1.0 Kind Regards
Use the DisableFeaturesList.txt Use the content available in the \Bin\Lists\Features_Templates You will use the option Disable Features in Customize Menu.
okay but I don't see any above capabilities in Features_Templates Spoiler: FeaturesList_W10_10.0.1904X.txt Printing-PrintToPDFServices-Features Printing-XPSServices-Features SearchEngine-Client-Package MSRDC-Infrastructure TelnetClient TFTP TIFFIFilter LegacyComponents DirectPlay Printing-Foundation-Features Printing-Foundation-InternetPrinting-Client Printing-Foundation-LPDPrintService Printing-Foundation-LPRPortMonitor SimpleTCP MicrosoftWindowsPowerShellV2Root MicrosoftWindowsPowerShellV2 Windows-Identity-Foundation Client-ProjFS NetFx4-AdvSrvs NetFx4Extended-ASPNET45 WCF-Services45 WCF-HTTP-Activation45 WCF-TCP-Activation45 WCF-Pipe-Activation45 WCF-MSMQ-Activation45 WCF-TCP-PortSharing45 IIS-WebServerRole IIS-WebServer IIS-CommonHttpFeatures IIS-HttpErrors IIS-HttpRedirect IIS-ApplicationDevelopment IIS-NetFxExtensibility IIS-NetFxExtensibility45 IIS-HealthAndDiagnostics IIS-HttpLogging IIS-LoggingLibraries IIS-RequestMonitor IIS-HttpTracing IIS-Security IIS-URLAuthorization IIS-RequestFiltering IIS-IPSecurity IIS-Performance IIS-HttpCompressionDynamic IIS-WebServerManagementTools IIS-ManagementScriptingTools IIS-IIS6ManagementCompatibility IIS-Metabase WAS-WindowsActivationService WAS-ProcessModel WAS-NetFxEnvironment WAS-ConfigurationAPI IIS-HostableWebCore WCF-HTTP-Activation WCF-NonHTTP-Activation IIS-StaticContent IIS-DefaultDocument IIS-DirectoryBrowsing IIS-WebDAV IIS-WebSockets IIS-ApplicationInit IIS-ASPNET IIS-ASPNET45 IIS-ASP IIS-CGI IIS-ISAPIExtensions IIS-ISAPIFilter IIS-ServerSideIncludes IIS-CustomLogging IIS-BasicAuthentication IIS-HttpCompressionStatic IIS-ManagementConsole IIS-ManagementService IIS-WMICompatibility IIS-LegacyScripts IIS-LegacySnapIn IIS-FTPServer IIS-FTPSvc IIS-FTPExtensibility MSMQ-Container MSMQ-DCOMProxy MSMQ-Server MSMQ-ADIntegration MSMQ-HTTP MSMQ-Multicast MSMQ-Triggers IIS-CertProvider IIS-WindowsAuthentication IIS-DigestAuthentication IIS-ClientCertificateMappingAuthentication IIS-IISCertificateMappingAuthentication IIS-ODBCLogging NetFx3 SMB1Protocol-Deprecation MediaPlayback WindowsMediaPlayer DataCenterBridging ServicesForNFS-ClientOnly ClientForNFS-Infrastructure NFS-Administration SmbDirect HostGuardian MultiPoint-Connector MultiPoint-Connector-Services MultiPoint-Tools Internet-Explorer-Optional-amd64 AppServerClient Windows-Defender-Default-Definitions WorkFolders-Client Microsoft-Windows-Subsystem-Linux HypervisorPlatform VirtualMachinePlatform Containers-DisposableClientVM Microsoft-Hyper-V-All Microsoft-Hyper-V Microsoft-Hyper-V-Tools-All Microsoft-Hyper-V-Management-PowerShell Microsoft-Hyper-V-Hypervisor Microsoft-Hyper-V-Services Microsoft-Hyper-V-Management-Clients Client-DeviceLockdown Client-EmbeddedShellLauncher Client-EmbeddedBootExp Client-EmbeddedLogon Client-KeyboardFilter Client-UnifiedWriteFilter DirectoryServices-ADAM-Client Windows-Defender-ApplicationGuard Containers SMB1Protocol SMB1Protocol-Client SMB1Protocol-Server
I didn't check them all but I saw powershell and openssh. I thought I saw the other options on that list. I was mistaken. It was another detail that I once made here. I'm sorry. Another thing that came to mind is that some things are disabled by capabilities that can also be disabled by disable features, I almost took this to be true for every component in the list.
My ISO is 19044.1288. Using [1] Integrate Windows Updates I integrate KB5012599 which takes me to 19044.1645 Using [1] Integrate Windows Updates I then integrate the latest CU. Easy. This is what I get when I use WHD... Maybe not... Won't let me link an image... The list is full of older Windows update from 1607 etc. The only 21H2 update is the enablement package KB5003791
So you integrate KB5012599 because of "Microsoft-Windows-ServicingStack" version="10.0.19041.1613" requirement of later CUs, and comes along with this update. It works, because this update can be integrated into 19044.1288 as it satisfied the requirement, but even in this case, the Servicing Stack update will be added only as the second as part of the integration process, which is enough, however, to proceed further with your strategy (you almost figured it out). You can skip this if you put first the SSU.cab (from the latest update) into the integration folder, because unfortunately it will not be picked first (even though it comes alphabetically before windows10*.cab) just by referring to the whole folder rather than individual files. Of course @inTerActionVRI will say (again) for WHD you do not need this, because SSU will be extracted and integrated first, and thus you can go by the latest CU... This menu option is still confusing to have. If you wish to integrate random updates, which are not part of the current WHD process, well, those updates can still have the Servicing Stack minimum version requirement, so if SSU is not added first one way or another, it is still broken. Just take *all* files, whatever they are (.msu or .cab), extract if needed (.msu), check if there is SSU*.cab, if yes, start with that, and then integrate pretty much randomly. The code is already there, it is just copy-paste at this point. Though it is a very generic approach (as other updates can have certain other requirements), since you are very limited on batch level with regards to update requirement verification as per update.mum, you might as well go by the above. Just my opinion, based on which the WUpdates process is bugged (or poorly implemented or easy to mistake its purpose, whichever of these you prefer), whether you accept it or not.
But this message appears even when using original LTSC 21H2 image. Component removal menu works as intended though.