When trying to remove components from the wim image, I get the generic error "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." How do I fix this?
As I said, "This week I would try with the new update." I come to bring the resolution feedback. I simply made the new custom iso 19044.1947. I did the Inplace Update and everything went well. Problem solved.
Thanks. Sorry for the delay. Had to wait for the weekend to try it out. All of the slui.exe reg commands fail with Access Denied. Checked the registry after reboot and none of the slui.exe registry entries have been added.
Understood. If even executing the script as Admin, it didn't work out, I don't know another way to help you right now. You are not using some of the SPbuilds 1862, 1865 or 1889 right? If so, try update to 19044.1947. These previous ones were very bugged. In the tests and my daily use, I realized this. In this 1947 fluidity came back.
Has anybody heard from @MSMG recently? I suspect he has gone quiet, because he is working hard to help his family, but I wondered if perhaps anybody else knew if he was okay. Looking to reinstall Windows 10 19044.1889 on a machine soon, but would rather have a clean install with help from the ToolKit before doing so.
Are the apps we remove with MSMG toolkit still supposed to show up under settings > apps in win11? Several of the ones I removed are still showing up and can be "uninstalled".
No, all PCs here are LTSC 1809 Nothing useful or worthwhile in later versions, and the issue with bloat being restored was never solved so have stuck with what works. I forgot to mention I ran it as TrustedInstaller via nsudo. Ok, if it can't be done for a live system, can I integrate the registry tweaks with the toolkit? Only the slui.exe are needed as the software protection platform registry values are able to be added already.
At Toolkit, you can integrate as .reg file, but if the system does not support this integration, when starting the system, what you integrated will not be there. EDIT: What I meant is that there is a protection against obsolete registry inputs in each build. I suppose this because, otherwise, we could continue to fill the registry with entries that MS no longer uses. And that doesn't happen. There is no block of attempts to insert registry entries that are no longer considered for a particular build. But there is a filter that cleans these registry entries.
Was not being well from past week and so the delay, will be uploading the new version once the packs are updated, have uploaded the updated Toolkit.cmd and ToolKitHelper.exe to support the patch Tuesday update, you can use it to remove the components. The updated ToolKitHelper.exe supports the source images with the below updates integrated. Windows 10 Client v1809/LTSC2019 (v10.0.17763.1/v10.0.17763.3287 [KB5016623]) Windows 10 Client v1903 (v10.0.18362.1) & v1903/v1909 (v10.0.1836x.2274 [KB5013945]) Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2 (v10.0.1904x.1889 [KB5016616]) Windows 10 Enterprise LTSC2021 (v10.0.19044.1288/v10.0.19044.1889 [KB5016616]) Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.856 [KB5016629]) Windows 11 Client v22H2 (v10.0.22621.1/v10.0.22621.382 [KB5016632]) Also it supports Windows 10 Enterprise LTSC2021 (v10.0.19044.1947 [KB5016688]) Preview Someone was asking about component removal for arm64 source images, right now the ToolkitHelper does not support arm64 builds as I don't have a proper arm64 device to test the image, though I do a Raspberry Pi 3 but it's dead slow to operate.
I am sorry to hear that you haven't been very well recently. Thank for you keeping us updated and for also taking the time to update those CMD and EXE files. I shall probably do some testing tonight, as I have a 1909 system that keeps trying to do a feature upgrade and desperately needs reinstalling to shut it up.
Spoiler unable to update Windows 10 LTSC 2021 - 21H2 Build 19044.1288 - ru-ru_windows_10_enterprise_ltsc_2021_x64_dvd_5044a1e7 Spoiler ALSO DOES NOT REMOVE COMPONENTS
Because the cumulative update you're integrating(KB5016616) requires a servicing stack update to be integrated first. Try updating the image first. Remove components later.
shhnedo - servicing stack update , what do you mean? I thought SSU already part of the cumulative update KB5016616
Open KB5016616.cab in a new explorer window or with something like winrar/7zip and check if there's SSU-xxxxxxxx.cab inside. But even if there is, I think it still needs to be extracted and integrated before the CU update itself. If you were installing LCU.msu on a live system, then the ssu is indeed already inside and it gets installed automatically.