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.
Some developers know how to mitigate virus detections, MAS by WindowsAddict for example. We can assume that ToolKitHelper.exe elevates privileges, deletes files, modifies files, modifies registry, removes system component packages (like DISM, or even uses DISM itself, who knows). "Without such commands, however, you could not accomplish what you can with it" - This is the problem, we don't even know what it performs exactly. So this type justification is only assumption. "I assume closed source code could prevent legal issues" - It is very easy to stay underground this days with VPN/proxy/VM/Sandbox/encrypted browser/temp mail/burner accounts + codebase64/telegram encrypted messages for DL links (all methods stacked on itself for best results). So there is no way Microsoft would find anyone by any means. Just don't place direct links on the forum page. "What I would recommend nevertheless is using a(n offline) virtual machine to perform your tasks" - This method is pointless with such type of software, because user is gonna use ISO later on live system anyway that has been modified with ToolKitHelper.exe in VM. So not only VM is affected, but ISO itself.
I see where you are coming from, but your views have flaws themselves, just as mine. Just because the detection is mitigated, it would not make it safer. If you have to use software, that registers your credit card or phone number, it can be back tracked if there is a real need for it for whatever reason (you buy VPN service as I am sure you would not want to go with free version, and some time back when I was checking Telegram, it was also requiring a phone number, which in many areas come with a name and ID assigned). If you deploy a modified image and add security software, it ought to detected malicious system files, thus the damage could be minimized. But I assume you will be using this software anyway. In a sandboxed (virtual machine) environment you would not litter your system at least and you can do a deployment and thorough scan if you need to be certain. A modified binary will be detected as it will not be signed. Alternatively, you could create a pure DISM-based version, all you need to do is to unlock Registry entries to be able to remove any component, and there you have your own solution. It is difficult to tell what benefits there are for using the ToolKit for component removal compared to DISM, at least I have not taken the time to compare the results, given how difficult/complicated it is to compare Registry entries for instance. Let us see whether you get a better reply from someone else.
"Just because the detection is mitigated, it would not make it safer." - I mean my initial suggestion was to minimize virus detection, not concern of safety because I believe Toolkit is safe. The topic went a little bit of the track. "If you have to use software, that registers your credit card or phone number, it can be back tracked" - There are VPN services that offer trial period (same features as for fully paid) and can be created with temp mail, no phone number, credit card or any identity requirements. Also for more extra privacy this VPN burner accounts can be created in VM+sandbox+web proxy+encrypted browser so you are additionally protected. Telegram accounts can be created with burner/virtual phone numbers + you don't need even smartphone for app. You can use VM Android OS + VPN. All illegal telegram group owners are not creating accounts with their own phones/sim cards obviously. You can fake everything this days if you have enough knowledge how to do it and resources. Anyways, Telegram was only example, there are other solutions. "If you deploy a modified image and add security software, it ought to detected malicious system files, thus the damage could be minimized." - ToolKitHelper.exe can be detected but system image files that has been modified/injected with potential malicious code could be undetected by any AV. So this is not a solution. Of course, this is all hypothetical. "In a sandboxed (virtual machine) environment you would not litter your system" - Again, ToolKitHelper.exe is not big issue because of possibility to run it in VM, but the problem is the modified system image, hypothetically. "A modified binary will be detected as it will not be signed." - There could be 100% workaround to this with such high level of system image modification that ToolkitHelper.exe can provide, again hypothetically. "Alternatively, you could create a pure DISM-based version" - Yeah, but ToolkitHelper.exe offers way more than that, it is not even comparable. It would be possible but also would take insane amount of testing and development, for which I am grateful to MSMG. The topic is not about ToolKitHelper.exe being malware, but suggestion to minimize virus detection with code optimization and mitigations, if possible.
Updated my windows today to ltsb 2016 just to see how it would work against 12400f 16gb ram, x3 m2 NVMe 5tb only gtx 1660 didn't want to work bought 1060 and it worked. Didn't debloat anything, no much to debloat anyways, only disabled defender. Dism reset base works no problem. Gpu runs much cooler than in windows 11 and draws only 7w to 11w while idle against windows 11 11w to 30w idle . Task manager says cpu load 0% when nothings running, and only 1.2gb ram used when idle. Probably best windows up the date
I just played Forza Horizon 5 on Steam(it just went free weekend) on Windows 11 22621.1105 If your delete XboxTCUI, it will also delete "C:\Windows\System32\gamingtcui.dll" which is UWP cannot solve itself. I have to copy this dll from untouched iso to get it working