In my post I was using ShinRamYun247 post about running dism and sfc. So I was referring to the dism cleanup. It was from an earlier post of his where he mentioned he ran both or maybe I'm mistaken.
Code: Dism /Image:x:\Mount /Cleanup-Image /StartComponentCleanup Will cleanup the sxs folder by compressing the superseded files. Code: Dism /Image:x:\Mount /Cleanup-Image /StartComponentCleanup /ResetBase Will cleanup the sxs folder by removing the superseded files (only when resetbase is enabled in the registry on the host).
Maybe you're talking about Dism /Cleanup-Image /RestoreHealth. If you are not specifying a source with healthy files using the /Source parameter then it is best to use Dism /Cleanup-Image /ScanHealth to avoid error messages that will only confuse you.
In the ToolKit menu due to lack of menu choices I haven't further divided them into more categories, yes if custom menu choices are added then the groups can be made. But in ToolKitHelper.exe the menu is divided into categories as below Internet Multimedia Privacy Remoting System SystemApps WindowsApps The current version of ToolKitHelper.exe won't show these menus for non-en-US/en-GB images since I did forgot to remove the if condition to check the language.
Sorry I should have been more clear it's DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase that I was talking about. I am aware that it has to be enabled first. Is it necessary to run that after an install in order to verify a successful 'MSMG modification" and install or is it enough to just run sfc /scannow and see that there are no errors?
Agree; the updates fly like gpu drivers and can be installed over the first night for those who require. There is no sense trying to keep up with all that. Cutting the fat off releases is where your work shines. Regards
It makes a lot of sense to use non refreshed images and avoid most of the problems people are having. I haven't integrated CU's at all and never have problems unless the problems are caused by me. I just use 17763.1 whether its pro home or ltsc.
This command is not required after installation. ScanHealth can also run on a mounted wim image. The only command that can not be done offline is sfc /scannow or sfc /verifyonly if you do not want it to repair the files.
Sorry, Right now the ToolKit has only been updated to integrate features/packs for v1903. Still I haven't added the v1903 component removal, don't worry it won't take more time like before since many components may need minor changes since I have modified the code to adapt to future builds.
If anyone is interested in my testing results here they are. I'm modifying an LTSC en_us x64 image with version 9.2. All system apps are removed (of course no windows apps are shown), all advanced components are removed except Internet Explorer (which can cause issues on my system if I remove). I integrate one driver (Intel Management Interface), one feature (direct x 9.0c), and in the apply tweaks section i choose 1,2,4 and 5. Thats all I do. I encounter no errors, installation goes smoothly and sfc /scannow shows no errors. After using windows update, installing a crap load of programs and making a ton of customizations and tweaks sfc /scannow still shows no errors. BTW this is on a separate ssd not vrtual.
No I always use an untouched image nothing integrated (17763.1) One thing I did notice is that if I add win32calc from features section sfc fixes that so I just don't add that feature.
That's weird, I got many errors removing some apps/components. Maybe because I was using v177763.104 and not v177763.1 or because I was using it on a virtual machine and not a real drive. I don't see why you would need to remove them all, unless you wanted to test it out that way. I think some components should be kept just in case, but that's my opinion. Anyways I will do more testing on v177763.1 on a real drive this time.