Hi there, using Toolkit_v13.5 from the 7z package, the lines you mention to replace in your link seem to start at 9710 and maybe end around 9832 with this version, is that correct? Thanks
@ inTerActionVRI. Thank you for your detailed explanations. I've tried and failed with setupcomplete.cmd (although my command is REG IMPORT "C:\Windows\SendTo.reg" since the file I need to execute is in the Windows folder. I've also researched "RunAsynchronous", which I still don't understand. In addition, I tried using $OEM$\$$\Panther\unattend.xml, which supposedly runs after autounattend.xml inside the <settings pass="oobeSystem"> section. But that didn't work either. So my last hope is building an AutoIt executable for all my tweaks and trying your startup folder suggestion. "Mount\Install\1\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\StartUp\Tweaks.lnk". Thanks.
I used to write a one-line script inside a shortcut, but I didn't like the result. But it's valid. I thought it best to write a script, which had a menu with an option for self-exclusion and an option for in-place installations and another for post-connection installations, opening a powershell script with options for winget. If I don't want to waste time in this step, I close the script, but I don't delete it. This one will run again when I restart. After I'm done, I use the "script's delete in startup" option.
Very interesting, that out of 100s of posts on this form, you seem to be the only one reporting this problem. I would do some troubleshooting, or at least describe in detail what you did to prepare your MSMG set up, before stating that a piece of software that has been sucessfully used for years is "a joke" and "REMOVES NOTHING - literally nothing."
Step by step: Putting my isos to ISO folder: 14393.1358 (custom component removal does not work but I dont care about this specific image tho) 22621.1992 19041.1704 Converting esd source image to wim: 1. Selecting [1] Source 2. Selecting [6] extract source from MCT or custom ESD image In the toolkit command prompt: 1. Selecting [1] Source 2. Selecting [1] Select source from DVD folder 3. Selecting Image Index: 1 x64 Windows 10Pro (it recognizes 22621.1992 as win 10 weird tho) 4. Do you want to mount setup boot image? Yes 5. Do you want to mount recovery image? No ... Mounting image ... 6. Selecting [3] Remove 7. Selecting [1] Remove Windows components 8. Selecting [1] Select Windows components 9. Selecting [1] Internet 10. Enter your choice: [A] All Internet Components ...hitting enter... 11. [X] Go back 12. [X] Go back 13. [2] Start removing windows components immediately outputs this: Finished removing windows components no components removed If it may be related: 22621.1992 not activated 19041.1704 KMS activated
Your ISO does not go in the ISO folder. You extract your ISO to the DVD folder in your MSMG directory, and you can only compile one ISO at a time. You might want to consult my setup guide, here.
No need to mount boot image right? I just skipped mounting the boot image and recovery image, then tried removing - nothing changed. It only works with package list. But gotta need a proper list of package names, how they are called internally, for it to fare. Whats wrong on my end then? What images have you tested it with?
MSMG automatically mounts whatever images you select (i.e. boot, setup and receovery environment). If you are integrating updates or need special drivers, I would recommend mounting all three. You do that after you run the "start.cmd" in the MSMG directory with elevated privileges. I know people generally don't like to RTFM but you really need to take a moment to read the instructions.
I want couple things be cleared up about this tool. 1. If a feature / component is removed this way, is it purged entirely that no trace of it is left in the registry especially under HKLM/SOFTWARE and HKLM/SYSTEM? I.e, are registry hives cleansed properly from the bloat you have removed from the source image? Because for example Windows Defender has 300 reg entries I want them all purged and have to boot into WRE and remove them line by line. One Drive has over 100 keys. Removing vaporware physically is one thing cleaning up the registry is another. This is important. 2. Anybody noticed volatility in the system produced after removal procedure? Glitches, instability and such? 3. What windows versions do you suggest to use the toolkit with? Like what version after 1809 is ideal to test this with? In the changelog are only 7 supported OS. I failed to find most of these on piratebay. Looking for any activated 190XX supported by this toolkit. Any recommendations?
What is your host OS? It looks like Windows 7 - if so, do you have SP1 installed? Secondly I noticed that the path in your host OS is too long. The path on your VirtualBox is shorter, but I choose to use a short as path as possible - for example, C:\10 or C:\11.
The host OS is w10 1607 LTSB. Its in the downloads folder. In virtualbox its on the desktop. I tried putting it in C:\msmg. Same outcome. It never starts the removal, just throws out the message that removal of components is finished and thats the end of it. Seems like ToolKitHelper is never launched.
I just debloated 14393.1358 (1607 LTSB) with MSMG. Results are retarded 1. Defender is gone from gpedit & services but plenty of entries under HKLM\SOFTWARE\Microsoft\PolicyManager\Default\Defender. Also its in Autorecover MOFs which tells the system what managed resources to recover firsthand LOL 2. Error reporting is there. 3. One drive is there. 4. Speech recognition is never touched Speech and Speech_OneCore folders in %SystemRoot% never affected 5. Microsoft-OneCore-Gaming package never removed 6. Microsoft-Windows-Hello gone Media-FaceAnalysis is there All it did was purged Defender and messed with some single packages removing half and leaving the other half intact
@ Zendendest. MSMG Toolkit has its quirks and many users, including me, have pointed them out in detail and the developer has done his best to address them when necessary. But given the issues you have experienced just to get to this point today because you don't want to RTFM, and the lack of other folks experiencing the same problems, I would attribute your "retarded" results to something other than the software, whose direction's you seem unwilling to follow.
I read the last comments from @Zendendest and everything he said, in one of them he says that he didn't find the versions on the PirateBay, well, firstly using versions from the PirateBay is already one of the mistakes, the versions have to be downloaded from the official website, or from UUPDUMP, because it is not known what is in the "versions" of that site, most are modified versions, and this does not work in TK, I am sending this message from Windows 11 Pro 22621.2215, which I used in TK 13.5, but I did not use the image 22621.2215 and yes the initial image 22621.1 that was updated inside the TK and it worked perfectly, I repeat, perfectly, removing everything that I wanted to remove, so the problems reported, are as we say here, BIOS problems, in Portuguese "Bicho Ignorante Operando o System" Ignorant Animal Operating the System, as it is making several errors in its choices of sources with which it intends to use TK. I'm not saying that there aren't problems with TK, there certainly are, because our friend MSMG is human like us and we all make mistakes, but he does his best for us and has the humility to take into account the experiences, comments and suggestions of everyone here, which do the right thing, using reliable base images, I would never use an image obtained from "PirateBay"... Now say "MSMG Toolkit REMOVES NOTHING - literally nothing." and "Results are retarded", I suggest you use the original images, as these results show that you are starting wrong and nothing that starts wrong ends well.
I debloated 19044.1706 and 19045.3208 removed everything bar firewall, remote assistance, remote desktop server, remote registry, work folders, media player, notepad, wordpad, system restore, win subsystem for linux, storage spaces, accessibility tools, sound themes, screen savers 19044.1706: Never booted up stuck at logon screen 19045.3208: Booted up. Most of junkware gone but not all. OneDrive is gone but OneSync service is accessible and running OneSync and CFTmon are all thats left