That thought crossed my mind. It's a good idea. I will test vanilla 21H2. Although, I will never let vanilla Windows connect to the Internet so somethings I won't be able to test. Well, if multiple people have observed the same behavior perhaps ignoring it is not a wise choice. I guess I noticed it because I've been running 1809 for so long and I skipped all of the 19xx and 20xx releases. It's like the frog in the pot syndrome. The performance got marginally worse with each release, but bceause it was so little over so many releases no one really noticed. And I've taken the biggest system killers out of the image, Like Windows Defender. Is it possible to take StartMenuExperience host out of the image?
@MSMG, the toolkit 12.8 broke inbox apps integration for Windows 8.1. While previous versions (can't recall exactly which version) worked fine, this version errors out on any and all appx packages. Another issue arose with package removal by means of dism. Removing VPN components and system restore errors out with "a volume for a file was externally altered and is no longer valid". I do understand that Windows 8.1 is rather old and most have moved on since. But it would be great if you can take a look at it. Cheers.
@soundwaves As I said, you're a month behind on the windows version. You're also using an old build of MSMG Toolkit. Now from the screenshots I don't see you removing anything that affects search. Try using MSMG Toolkit 12.8 and a compatible windows build and check again.
New "VirtualCreate_ImageIndexEditions.zip" 2022-10-16 (updated with 2022-10-12 "uup-converter-wimlib-85") and new Custom Toolkit. Download in my Signature.
Hello. I'm trying to integrate the latest cumulative update to Windows 10 21H2 (KB5018410), and even after installing the servicing stack update for Windows 10 21H2 x64 (KB5014032), I still get a version mismatch. Is there something I'm missing? Log says I need a more recent Servicing Stack, but according to Microsoft's website and the update catalog, I'm using the most recent version.
Well, after testing vanilla un-modified 21H2 LTSC it's just as bad as the de-bloated version I created with the toolkit. In fact, the vanilla install, with 126 processes is even worse that the image I created with the toolkit. It needs more services running to do the same things 1809 can do without the service. It is slower to load programs. It is slower at neworking. Verdict: 21H2 LTSC performance is noticably worse than 1809 LTSC 32GB DDR4-3733CL16, I9-10940X @ 4.5GHZ all core, 970 Evo Plus 2TB. RTX 3080 Ti, 10G LAN
Search Box stopped working on Windows LTSC 2019 after i removed some stuff with the Toolkit v12.8, does anyone have any idea, why this happened? Can someone give me a few tips on what i need to watch out next time before i remove components of Windows? Thank you in Advance!
There are times when removing components with the Toolkit breaks Cumulative Updates from installing, while other updates like dotNet and drivers are working. This is actually a good thing, as these Cumulative Updates just restore the unwanted functionality previously removed. So, is there a way to deliberately disable Cumulative Updates only and keep all other updates, either with some Toolkit options or any other methods?
Manually install updates other than CU. https://forums.mydigitallife.net/threads/windows-update-minitool.64939/
Thank you, but I would prefer an automated way. There should exist a reason why updates are failing after some Toolkit actions. It would be great to have a possibility to use it on purpose.
Have uploaded updated ToolKitHelper.exe for people who cannot wait until the next release. Supports the below source images 17763.3532 1836x.2274 1904x.2130 22000.1098 2262x.674 17763.3534 1904x.2132 22000.1100 2262x.675