If the Source OS is Windows 11 then these are Edge update services, removing Edge Chromium will not remove the Edge update which is required by Edge WebView component. Removing Edge WebView will remove Edge Update too.
I disabled the services that appeared and the edge update folder does not appear. If I remove the services, they will reappear... I have Windows 11.22621.819 and uninstalled Edge Chromium along with Edge WebView. After installing Windows, after about a couple of days, these services appear and the update folder in C:\ProgramData\Microsoft.
Updated the Toolkit to v13.1 Spoiler: Change-log v13.1 + Updated Toolkit's Bin folder with Windows 11 v22H2 Insider Preview WADK (v10.0.25267.1000) Tools. + Updated the Microsoft .NET Framework 4.8 Pack (Windows 7/Server 2008 R2) with .NET 4.8 KB5020879 (4.8.4590.2) (Thanks to MDL Member : abbodi1406). + Updated the Microsoft .NET Core 3.1 Desktop Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Microsoft .NET Core 3.1 Desktop Runtime 3.1.32 Runtime. + Updated the Microsoft .NET 6 Desktop Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Microsoft .NET Desktop Runtime 6.0.12 Runtime. + Updated the Microsoft .NET 7 Desktop Runtime Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Microsoft .NET Desktop Runtime 7.0.1 Runtime. + Updated the Microsoft Windows PowerShell 7 Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with PowerShell 7.3.1 Runtime. + Updated the Microsoft Edge Chromium Browser Pack (Windows 7/Windows 8.1) with Microsoft Edge Chromium v108.0.1462.54 setup files. + Updated the Mozilla Firefox Browser Pack (Windows 7/Windows 8.1/Windows 10/Windows 11) with Firefox 108.0 setup files. + Fixed a Bug in the Feature "Remove Windows Components", Where Removing Windows Mixed Reality component would break the Remote Desktop for Windows 10 Client v1903/v1909 Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809/LTSC2019 (v10.0.17763.1/v10.0.17763.3770 [KB5021237]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1903 (v10.0.18362.1) & v1903/v1909 (v10.0.1836x.2274 [KB5013945]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2 (v10.0.1904x.2364 [KB5021233]), LTSC2021 (v10.0.19044.1288/v10.0.19044.2364 [KB5021233]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.1335 [KB5021234]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v22H2 (v10.0.22621.1/v10.0.2262x.963 [KB5021255]) Source OS. + Optimized the Toolkit code (Thanks to MDL Members : inTerActionVRI).
Can someone try MSI Afterburner after removal of all listed components, integration of VC++ pack, and DirectX 9 pack on Windows 11 image with the latest update? MSI Afterburner and some other programs with VC++ dependencies start showing "side by side" error, which basically means VC++ is not detected correctly or needed dependency is not present. In this case, I think VC++ becomes permanently corrupt because re-installation of VC++ on live image does not fix the error. I think a similar issue happened a few years back with DirectX 9 pack, where its integration into offline image was incorrect and re-installation of DirectX 9 on live image couldn't fix it. Or it could be that MSMG Toolkit's removal of UWP Native NET components corrupts something.
@MSMG Where can I get LanguagePacks for Windows 10 and Windows 11 now? Where else can you download apps?