I have found something. Used a fresh, first LTSC build without any updates integrated and removal was flawless, no error. I did not do anything else, just went straight to the removal section. I will now test an updated image again to see where is the problem. Will update in the following hours. Edit: Done, found the problem. The issue is with the (pre) integrated updates. @MSMG: The toolkit does not work on images with updates integrated first. Probably you tested with clean images without updates integrated. It was always recommended to integrate updates first and THEN remove components. At this moment, we cannot go that route anymore as it will error out. Edit2: @MSMG the error pops up the very moment when the toolkithelper is looking to modify the offline registry. Most probably, the updates rename something in the registry and that's the reason toolkithelper throws an error when it tries to modify a key or value that no longer exists or has been modified from its original value. That's also the reason that some components get removed without error. The error occurs on registry entries modified by updates. Can you check this? Cheers.
Think you didn't check this post, I have checked with an image with updates integrated and the removal is working, but I didn't tested the OS installation.
@MSMG: I see, re-reading your post, indeed you've tried with the latest updates integrated. Do you integrate with the same toolkit? WHD updates? Is it possible that different ways of integrating cause this error? How do others integrate their updates? I've only come so far as to diagnose it's an issue with the updates. Cheers.
If you remove the Unified Telemetry Client (Asimov), Windows Error Reporting, then when you manually install the update in the cab, the same update hangs again in the update center, despite the fact that the update was installed.
After a failed removal, yes. SFC reports errors. I'm going to do a new build, integrating the updates with the toolkit instead of Abbodi's WUI. Also, I'll leave out the framework CU's to see if it matters anything. Cheers.
Thank you, I look forward to your results. If there is anything else you want me to try, do let me know. My own suspicion is that you have some software installed on your PC, therefore you do not get the error.
MSMG ToolKIt v9.2 > Unfortunately, it does Not Work Well, I'll have to wait for a new version. Yes I run it > start.cmd > (version 9.1 if it works Very Well)
MSMG said that the LTSC will receive errors on both toolkits. I'll still be waiting for a fix as for now stuck using 1607.
Where did he said that? I only need x86 and multilang support. The released toolkit 9.2 is supposed to work, so if any errors are found then we need to solve them. Cheers.
I can just speak for myself: I always use WHD x64 folder to integrate Updates. Works well up to ToolKit 9.1 When using 9.2 I got errors when removing almost any windows components. Tried to integrate updates using the update x64 folder. More problems when removing. I think the WHD folder is read by the Toolkit in the right order. If we integrate Updates after removing windows components and advanced, does removed programs comes back ? How the Tookit can interpret if I have removed Windows defender or any other system program for example ?
OK I can now testify MSMG is correct. Toolkit works flawlessly on x86 LTSC Spanish. I just had a perfect run, solved the error. Cheers.
It's in the release post here : https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-494#post-1509509 Under notes it states component removal is broken for LTSC, we have to wait for a new version that fixes it.
I'm sorry but you have not been following the discussion. Read: I've said multiple times that I only need x86. Anyway, it's working perfectly fine, the image has been prepared without error. Cheers.
