Hi guys. Can you please tell me if it is possible to edit Toolkit.cmd to work with new ISO Windows update? For example win 10 21h2 (19043.1503)
@(\_/)^(\_/) @Supern00b Although I haven't heard otherwise, I really don't think there is any need for concern. I suspect that @MSMG is having a well earned rest and will be along sometime soon to update the ToolKit. In the past, I did make my concern known about @MSMG being the sole developer. Of course it would be tragic if anything happened to him, but another great loss would be the amount of work that has gone into this program. If this knowledge were spread and shared with select and trusted developers, good things could even happen.
You can edit the Toolkit, but you should know what you're doing. Why do you want to edit? Oh btw, this tool will work for the version you stated.
I want to always be ready to edit the image of a new windows update. the document says that it can work with the latest version 1348. quote: v12.0 : + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2/LTSC2021 (v10.0.1904x.1348) Source OS.
Can someone explain how there is still OOBE setup on the first boot if you remove both of the OOBE components? Does this mean that some files are still there and the components aren't removed fully?
Is it possible to directly install the rebuilt Win10 to a new empty HDD partition as a new usable OS without the need to make ISO and create a bootable USB drive?
You need to use autounattend.xml (autounattend file) to install fully automatically with all OOBE screens skipped.
For full compatibility with the new CU, the component removal module (ToolKitHelper.exe) must be updated in case you need to remove components.
Enable_Update_Other_products_MS_with_WU.reg: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending\7971f918-a847-4430-9279-4a52d1efe18d] "ClientApplicationID"="MoUpdateOrchestrator" "RegisterWithAU"=dword:00000001
ClientWebExperience Unfortunately, I know of no way to correctly restore just this one component to the installed system after deleting it from the offline image, without affecting the other deleted components.
Yes, but I can get by just fine with audit mode and registry tweaks, at least while testing or trying out images. But this doesn't answer my question. Why are those screens even present at all if the OOBE packages are removed? Am I correct in assuming that MSMG doesn't remove OOBE packages unless autounattend.xml selected, regardless of the user chose in "remove" menu?
Perhaps someone has fixed the registry file on this vcruntime packages for w10 x64. Replace HKLM\SOFTWARE to HKLM\TK_SOFTWARE
Hello! Just found out about MSMG ToolKit. Loving it so far, thank you for making it. I have a question about " Removing Windows Components Using Package List". What exactly can you put there? What types of packages does it accept? For example, does it do individual packages from the FOD package? Or would it only accept FOD package as a whole? Or not at all? I wanted to remove search and cortana but didn't saw an option in "Remove Windows Components Menu". And another question, can you somehow remove specific files or folder with the MSMG ToolKit? I love that it removes adobe flash player and I'm wondering if I could include some of my own specific stuff.