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?
Hey @MSMG - Wanted to give an FYI that I built my Windows 10 x64 1809 (Redstone 5) image with the latest Toolkit v9.2 and removed all Windows Component. It resulted in the System settings to not function (freezes). Then I investigated and found out that removing "LocationService" broke the "Display" option in system settings. I believe this is the case because when you click "System Settings", it would go to "Display" submenu by default and it freezes/malfunction because "Night Light" feature requires location service. To further test this, I was able to navigate the system settings by searching "About your PC" in the start menu and it would direct me to system settings's "About" subsetting. As soon as I clicked "Display" it would freeze again. I had to end process SystemSettings.exe from task manager to reopen system settings every time it freezes upon clicking display and click "System Settings" from Settings app. I created 2 images to test (1 with removing location service and 1 without removing location service). Wanted to give my experience with removing location service component.
It is an old message... SFC came dirty when done. With ToolKit 9.2, I am able to make ISO's from an original LTSC 17763.1 or 17763.107 as described in my latest post: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-502#post-1512657 Dism came clean with no errors, SFC is not clean but did not reinstall Windows apps.
Apologies all if the following has been raised already. I have Googled and also searched within this thread to no avail. SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-4_MLF_X21-87129.ISO Mounts successfully, WHD update pack applies successfully, then when I attempt to access item [4] Remove I am instead taken to the submenu for item [5] Customise. I've used the toolkit successfully several times already on retail Pro 1809, so I'm pretty sure I'm not missing anything, but please forgive my ignorance if this is expected behaviour or a known issue with the 1803 Enterprise iso. Initially I was mounting only the Enterprise image from the DVD, so I tried mounting ALL instead but the behaviour is the same. I have also tried starting again from scratch with a fresh copy of the toolkit and Windows iso, again same results.
I did forgot to add that code, well here it is. Code: Dism.exe /Apply-Image /ImageFile:Win32Calc.tpk /Index:2 /ApplyDir:<Image-Mount-Path> Dism.exe /Apply-Image /ImageFile:Win32Calc_ru-RU.tpk /Index:2 /ApplyDir:<Image-Mount-Path> Reg.exe import Win32Calc_x64.reg
The drive shouldn't matter, since I do test the Toolkit on both C: and D: and it removal works without any errors. But you said the installation worked, did you removed all Windows Apps and System Apps and tried the installation? Only for LTSC the removal is not working but for non-LTSC it works if either only Apps removed or System Apps and Advanced components are removed but not the whole.
Can't surely say there will be one so soon as I'm still debugging the issue and also tweaking the component database.