@MSMG Sorry my bad English..!! Which the last Windows 10 version (e.g. 1709, 1803, 1809, 1909) than completely removed Windows Components and Advanced Windows Components and doesn't return later on Windows Update (CU)..?? Thanks in advance..!!
I think this may have been asked a year ago, but I couldn't find the post, so apologies if this is a duplicate. Is there a way to revert the network status icon in the system tray to that used in 1809 or before? If there is a way, may be it would be a good addition to the tweaks menu? The globe is uninformative particularly when your PC has multiple adapters, VPN and VMs and you use the PCs for testing various scenarios. Quite annoying. Just more stuff M$ changed for no good reason. Switching between private and public modes also seems to cause the globe to appear, as does various wireless scenarios. Being totally white too with someone with aging eyes doesn't help either.
And you may like to engage with ''Windows 10 Enterprise LTSC 2019'' Which has a long update support for another 9-10 years. Thanks. ...
Hello when I try to use the removal of windows Components Using Package List I get the following error: Removing AdobeFlashForWindows Package... ------------------------------------------------------------------------------- MSMG ToolKit Commandline Helper Version: 1.0.2700.0 Image Version: 10.0.19041.153 Error: Unsupported Windows OS Image ToolKitHelper only support Windows 10 v1809 and v1909
The first thing I did a while back was remove all editions but 64bit enterprise english from my original ISO file so no other option would exist. All installs since have been based on that. Vanilla 1909 will in place update to vanilla 1909 keeping files and apps but not to CU 1909 unless I've installed the CU first, then it takes it. Way back, 1903 updated to 1909 with no complaints. Every install for several versions has been touched by the toolkit. I've read up on this error and everything says it's either the language or something about the location of "Program Files" in the registry and neither of those situations apply here.
Ok, did you tried adding the update (KB4541339) for the Windows 10 v1909 setup source folder ? This update is provided for Windows 10 setup source media folder if you have integrated the updates to boot.wim, install.wim and winre.wim. This update will also helps in upgrade issues with images with CU integrated.
@MSMG I tried using an "older" version (1903) and I keep getting this error ? =============================================================================== MSMG ToolKit - Remove Windows Components Using Package List =============================================================================== ------------------------------------------------------------------------------- ####Starting Removing Windows Components Using Package List#################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 3 Image Architecture : x64 Image Version : 10.0.18362.657.0 Image Edition : Enterprise Image Default Language : en-US ------------------------------------------------------------------------------- ####Removing Windows Components Using Package List############################# ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Removing AdobeFlashForWindows Package... ------------------------------------------------------------------------------- MSMG ToolKit Commandline Helper Version: 1.0.2700.0 Image Version: 10.0.18362.657 Error: Unsupported Windows OS Image ToolKitHelper only support Windows 10 v1809 and v1909 -------------------------------------------------------------------------------
For component removal, you need v1909 which is v1903 + Feature update for v1909 + latest SSU & CU. Do integrate the required updates and then try removing components or Use the latest v1909 available ISO.
I added it here: C:\ToolKit_v9.6\Updates\w10\x64 This file: windows10.0-kb4551762-x64_dacef156c781f2018d94d5a5286076610ba97279 Which I see is not the KB you are referencing... Is the one you are reference the servicing stack update?