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
Greetings, To remove Code: AppRep.ChxApp ; CloudExperienceHost ; & SecHealthUI what component should I need to remove from MSMG ToolKit via ToolkitHelper.exe(Method) ?
The problem is probably with the image that you're using then. I only use images built with the scripts downloaded from UUP dump. Out of those images, only 22621.1992 is supported by the current version of ToolKit. Reading the current changelog will tell you which version is supported by the current ToolKit. We are fond of MSMG here as he very generously provides us with a tool for free that he has worked so hard on. I won't deny that I too also made (many) mistakes at the start - much of those might have been avoided by reading the documentation however. But I don't recall calling people names on here, especially those trying to help me.
Have been busy with my farm land and also was not being well past weeks. Have updated and uploaded the Toolkit to v13.6. Windows Apps Integration, now the Apps source folder uses a single folder <Packs\Apps\w10>. Download and copy only the right app file version specified for each Windows version in the HASH.txt and the app dependency files to the <Packs\Apps\w10> folder. Window Updates Integration for Windows 10/11 now integrates the updates in the required sorted order. Windows Components removal now comes with Compatibility Settings menu to protect the components related to Windows OS functionality. Spoiler: Change-log v13.6 + Updated Toolkit's Bin folder with Windows 11 v22H2 Insider Preview WADK (v10.0.25947.1000) Tools. + Added or Updated Appx License XML files for the below Apps to Toolkit's <Bin\AppLicense> folder. Bing Search Dolby Audio Extensions SkyDrive Microsoft Teams for Surface Hub Microsoft Office Excel Microsoft Office PowerPoint Microsoft Office Word Microsoft Outlook For Windows * Merged the Toolkit's <Packs\Apps\w10> and <Packs\Apps\w11> source folders to one <Packs\Apps\w10>. + Updated the Feature "Integrate Windows Updates" to support integration of updates in sorted order for Windows 10 and Windows 11 Source OS. > Moved the Feature "Integrate Windows Inbox Apps" menu to the Toolkit's Integrate Menu. + Updated the Feature "Integrate Windows Inbox Apps" to support integrating the below Apps for Windows 10 and Windows 11 Source OS. Bing Search Dolby Audio Extensions Family Microsoft Defender Dashboard Outlook For Windows Power Automate Quick Assist Teams Windows Defender (SecHealthUI) + Updated the Feature "Integrate Windows Inbox Apps" to support integrating the below Apps for Windows 11 Source OS. 3D Viewer Dev Home Messaging Microsoft Pay Mixed Reality Portal Mobile Plans Office OneNote Paint 3D Print 3D Skype + Updated the Feature "Integrate Windows Inbox Apps" to support newer app dependency packages. + Added Compatibility Settings Menu for the Feature "Remove Windows Component" to protect the removal of components related to Windows OS Functionality. + Fixed a Bug in the Feature "Remove Windows Components", where removing Cortana App was breaking Shell Search in Start Menu, Taskbar, Explorer Search for Windows 10 Client v2004/v20H2/v21H1/v21H2/v22H2, Windows 11 Client v21H2/v22H2 Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809 (v10.0.17763.1/v10.0.17763.4737 [KB5029247]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client Enterprise LTSC 2019 (v10.0.17763.1/v10.0.17763.4737 [KB5029247]) 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/v22H2 (v10.0.1904x.3324 [KB5029244]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client Enterprise LTSC 2021 (v10.0.19044.1288/v10.0.19044.3324 [KB5029244]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.2295 [KB5029253]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v22H2 (v10.0.22621.1/v10.0.2262x.2134 [KB5029263]) Source OS. + Optimized the Toolkit code (Thanks to MDL Member : inTerActionVRI).
client.cbs should be protected, it breaks search on start menu. if its already protected its bugged because i deleted everything without touching compability and it got removed, tested 2 times. [tested on 22621.2134]
I tried msmg toolkit After processing windows up to 22621.2215 work after that all newer windows 22621 cannot be used because of the boot error that occurs at boot sihost.exe "The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application" explorer.exe "unknown disk error" What's the problem
MSMG Thank you for the new version of a wonderful tool. I have a question: components marked with an asterisk can no longer be deleted? For example, I wanted to remove all Internet components: Edge, Edge WebView, Internet Explorer. Or, for example, I don’t need the Windows store - what should I do in this case? Thank you.
Yes, Client.CBS was not checked when all components was selected, have fixed it and uploaded the Toolkit.cmd, do download and copy it to the Toolkit folder.
22621.2215 is not supported, check the changelog. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v22H2 (v10.0.22621.1/v10.0.2262x.2134 [KB5029263]) Source OS.
You need to go to Compatibility menu and select the compatibility option to enable or disable the components protected.