May I ask why don't you use DISM? I remove almost everything from every list. Would that change the order you follow?
Because this is recommended by @MSMG : to be sticked to the rule to use ONLY ONE method from two. And Toolkit method was always recommended. Simple. I didn't tried both at once. As @MSMG said, you may try, but only on your own risk. (Before his message I thought using both methods at once is "highly restricted", "wrong" or likely a "user fault") --------- Note: Removing of many apps / packages are not proposed by MSMG to stay within safe borders. But I always wish the capabilities of MSMG bundle become expanded with removing system apps without limits, as an "extra" options for advanced users that don't care about SFC checks, but want more debloated OS (in spite of CU are not avalable anymore). To be clear: SFC checks are important: - for original source disrtos (to check M$ quality itself, because they fail with their own images) due to poor QC (Quality Control) - for MSMG bundle with present capabilities SFC checks don't matter (they will obviously fail): - for hardened custom images or purely debloated live OS with system apps removed and w/o functional CU
@ingviowarr I've been deleting almost everything with MSMG Toolkit 10.4 and Windows 19041.264. Used all the lists, and errors were managed more gracefully than current version (and there were few than now). I cleaned with resetbase and didn't even cared to try sfc. Everything I wanted to keep was working without a single problem. Now I can't even remove Edge and get errors on different phases and elements depending on Toolkit/Windows versions combination. I'm about to give up and go back to previous versions. I'll wait for next update to see if it solves these problems and can remove everything it was able to remove before.
@Bokeron This is because the Windows is getting worse and worse. I believe @MSMG doing everything he can to fix this crap.
That's just 20H1/20H2 the most buggy build ever of Windows 10. 1903/1909 and 1809 work very well and without all these problems.
@graver.x I'd love to hear more details too (about DISM method as additional part). And about the sequence of these two methods. Also I much appreciated for your example-list for NTLite trial, notes about Text Input App and many tests over thread have been done by you. Exellent post #17126 ! UPD: Now I'm thinking about LTSC more and more...
You can try the MSDN ISO's but still the problem is due to the CU which causes SFC error when cleanup-image is performed. Will do more test which images are safe (UUP, MSDN, MCT ISO) but I'm sure the ESD is broken as it is a system prepared image with image cleanup done and has more file or folder duplication permission issues.
hi I used a new version 10.7 to remove the component from this version 19041.508.160101.WINBUILD_CLIENTENTERPRISE_VOL_X64FRE_EN-US but after installing windows nothing has been removed Olso this error [5] System [E] Manual Setup (InPlace Upgrade) Wait, Deleting Windows Manual Setup files & folders thanks
At first the DISM method was used since removing the package through it's mum file would also remove any updated files added by the LCU. But starting with Redstone 5 the MS started combining many packages deep into other packages which made it impossible to use DISM to remove the components and also for some packages lost there packages mum files. So the manual method was created and the manual removes in depth than the DISM and also can support shared components compatibility. The only reason I kept the option to remove the components using the DISM was for people who use Windows 7 - Windows 10 RS4. I would say the ToolkitHelper method is cleaner and yes if you are going to use DISM method then don't use the ToolkitHelper as the ToolkitHelper uses file or folder checking to known the component existence and if it doesn't find it then it may report the component has been removed already or may skip certain checks done for shared components compatibility. But if you really want to use both the methods then first use DISM and then the ToolkitHelper method.
The DISM and the ToolkitHelper uses different method to detect the package and so running the ToolKitHelper may not work properly.
At first I wanted to stick with Windows Apps and System Apps removal as it was sufficient for average users but then expanded the list to include privacy components and now it has Internet, Multimedia, Remote and System components (a total of around 103 components). Right now, I'm not in a position to add more components as it requires more time, effort and troubleshooting to work on it which I can't do due to my poor heath and other issues personally I'm going through. In future will add more components when my health and other things become better.