which toolkit works flawlessly with enterprise ltsb 1607 build 14393 for removing all components with no sfc /scannow?
It depends. Not all operations will cause SFC issues. OneDrive removal will. It's just a matter of reading and make a "safe" list of what can be removed without causing SFC errors. It's always better to disable more and remove less. Cheers.
Actually when removing the Internet Explorer, the ToolKit creates this key [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\LowRegistry\Audio\PolicyConfig\PropertyStore]
Apply the Win32Calc pack and import registry Code: Dism.exe /Apply-Image /ImageFile:Win32Calc.tpk /Index:2 /ApplyDir:<Image-Mount-Path> Reg.exe import Win32Calc_x64.reg
That's because the in v8.8.7 the ToolKit uses the DISM to remove the components which will cause SFC error when the DISM removes more than required.
@MSMG I have a strange (good news). Sorry, it is long story.. I continue to make some tests in real conditions: ( Removing; Adding and installing windows on HDD or SSD) Since ToolKit came version 9.2 , I had some issues and errors when removing components. Toolkit was installed on my D: partition, Leaving Windows Host LTSC x64 on C: All operations where made on D: partitions and I got errors. 10 days ago I remove Toolkit from d: and put it to c:\Toolkit Since then, I have been able to made new Iso files without any errors from 9.2 Toolkit using Windows Pro 17763.1 or 17763.107 or Windows 10 1809 LTSC - all 64 Bits - I integrate Latest SSU and just latest Feb CU . Then I remove almost all windows components , keeping Asimov Telemetry Hyper V and some useful components. After installation and activation I let Windows install drivers and latest march CU + Dot.Net CU. Nothing came back when I look into systemApps ' folder. I made a "dism /online /cleanup-image /checkhealth", then "dism /online /cleanup-image /scanhealth" and came clean. (Did not use /resetbase) Can it be in relation with the use of the partition or whatever cause to see x64 builds working well ?
Good to know, as I wasn't clear in my previous post: being cautious I didn't completely "remove" IE, rather I disabled it via Dism. I guess "disabling instead of removing" approach backfired. ¯\_(ツ)_/¯
Since there is no MSMG Toolkit right now for LTSC I'm disabling things I can't remove with dism. I have no use for anything IE or Edge so I remove the IE11 packaqe in offline mode with the following; Code: dism /image:<mount point> /remove-package /packageName:Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.17763.1 Has not given me any trouble removing it that way. Though it's not completely gone, there's still some remants of IE within the filesystem. There is just so much of that kind of crap I wish I could eliminate. Even with LTSC there's still a ton of unneeded packages and UWP stuff within the filesystem.
@MSMG In 9.1 or 9.0 toolkit previous version to the current version, what component was the main factor to receiving errors on the 2019 LTSC base / refresh iso when doing sfc /scannow? or at least what components can be removed in the 9.1 tool kit so that there will be no error in the /sfc scannow?