The Remove Windows Component using Package List can be used for two methods of component removal 1) DISM /Removal-Package 2) ToolKitHelper.exe You shouldn't use both the entries for removal, I advised you to use only the ToolKitHelper entries.
let me explain [8] Tools > [1] WIM Manager > [C] Delete for delete editions or [8] Tools > [1] WIM Manager > [D] Export for export your edition to new install1.wim and rename it later
Start menu Display Name | Package Name Take Test | (SecureAssessmentBrowser) Films & TV | (ZuneVideo) Microsoft Pay | (WalletApp/WalletService) My Office Apps | (OfficeHub) NTLite uses a different method to remove components and for remove return components it uses some kind of tagging for each components when they are removed and uses this info to identify the returned components.
I thank you very much, but do I have to do this for every single version to be deleted? it is not possible to enter eg 1-4 eliminating them at the same time?
Right now that feature is not added and also when you delete an index in a wim image then the index values will change, for example if you delete the 4th index then 5th will become 4th, 6th will be 5th and so on. The easiest way is to export the required index to a new file and then replace the original file with the new one.
Thank you sir. So i should add the last 4 enteries (dism template) to the end of the removepkgslist.txt or need not ?
Yeah, @MSMG i think there should be an option here to delete all the other editions except the chose one as well, just to make it easy rather than going through it 6-8times if pro edition is selected the loop iterates 5 times to delete index 1 and then after loops and deletes index 2. when I tried the export option and no to exporting to new name, it didn't seem replace the existing. all editions were still showing up
Thanks. Do you know where can I find Camera Barcode Scanner on NTLite and if it's possible to remove the Windows Firewall on MSMG ToolKit?
First I want to say I definitely appreciate the hard work MSMG has put into this project. It is not in vain. But, I always wonder what people hope to accomplish by stripping all out of Windows. Perhaps many would prefer booting to a simple DOS window, and launching apps using commands? That would be pretty bare-bones now wouldn't it. Sure, I enjoy playing around with this program occasionally, but I would never use the end result as my main drive. It also seems since the advent of the toolkit helper anyone who does use this is relegated to a version of the OS which is not up-to-date. I would prefer to have an alternate version which would work on any present and future versions of Windows I could throw at it. I could do this in the past, and it would work quite well. But since the toolkit helper is now being used I use my own script. I can effectively remove, and integrate what I want, and sit back while the script runs. No menus or anything, just paste the ISO path and do anything I want. Oh, well. Life is life, and sometimes more is less, and less is more. Someday someone will want to remove System32.
With version 1809 it is perfectly possible to remove components and maintain compatibility with Windows Update. This has nothing to do with the toolkit helper but with how Microsoft implements updates in the latest builds.
Hi all, my first post here, i got question: Anyone made list of stuff to remove and sfc/scannow command works without errors? (Windows 10 Pro 1809) Thanks.
As I told you you shouldn't mix both the list, the last 4 entries given is just an example for people using the DISM method. Just use the ToolKit: lines
I am sorry. I should have phrased that better. I am not referring to Windows Update. Also 1809 is almost one year old which is ancient in software development. I would prefer that MSMG's toolkit work with all versions of Windows including the latest Fast IP as it used to.