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.
yeah, finally it comes! thank you for your work also want to ask, for next Win releases, like redstone 6, you will need to do same for all langpacks, or it stay the same and needs just a little corrections?
There's no order You mean to say offline installing updates after the OS installation using a cab file and then again checking with Windows Update?
I had checked with one Windows 10 v1903 x86 Host and a Windows 10 v1809 x64 HOST and on both the systems the component removal is working. Will try with a different HOST and see what's the result.
I said the current ToolKit won't work with both the x64 LTSC ISO's be it original release or the refreshed one.
What's the HOST OS you are using? I'm testing this issue will report back once I do replicate the issue. Integrating or Installing the updates after the component removal can restore empty folders like for defender the <Program Files\Windows Defender> will be re-created. I do check for the folder/file names for package existence since some packages doesn't have a proper package names.
What's the HOST and Source OS you used? Did the installation went fine? With en-US/en-GB x86 Images there are no issues for me if the component are removed in any order but with ru-RU image I got setup error when the Apps are removed and then found out the Image-Cleanup is causing the error, still need to do further tests to know whether that's the cause.
Now most of the MUI data to be removed is automated to get the data from the registry, only few lines of code are added manually which I have seen so far hasn't changed for all Windows 10 versions. If the newly added function to fetch the MUI data works properly then adding support for future builds will be easier. I do use the MUI Image for verification of ToolKitHelper.exe Log with the Component Removal Database.