What's the source OS used and Is it Edge or Edge Chromium you referring? Even for older OS version below v2004, the MS has included the Edge Chromium with the CU and the Toolkit removal program needs to be updated to support removing Edge Chromium for these OS.
What's the source OS used and Is it Edge or Edge Chromium you referring? Even for older OS version below v2004, the MS has included the Edge Chromium with the CU and the Toolkit removal program needs to be updated to support removing Edge Chromium for these OS.
Will be adding below components for removal when I do resume updating the Toolkit removal program, it will be available from next version. Microsoft.AsyncTextService_8wekyb3d8bbwe - related to Maps and People microsoft.creddialoghost_cw5n1h2txyewy - Related to Hello UI Microsoft.Windows.XGpuEjectDialog_cw5n1h2txyewy - Modern Safe to Eject for External GPU NcsiUwpApp_8wekyb3d8bbwe - Related to Network Status Indicator for modern Apps. MicrosoftWindows.Client.CBS_cw5n1h2txyewy (User Experience for Windows) - Required for Touch screen, Store, it includes InputApp These components are required, so need to further check. Microsoft.AccountsControl_cw5n1h2txyewy - Required for User creation, Logging into Microsoft Services including Store and Edge Chromium Microsoft.Windows.AddSuggestedFoldersToLibraryDialog_cw5n1h2txyewy - Need to check Microsoft.Windows.AppResolverUX_cw5n1h2txyewy - Required for modern Open With Dialog Microsoft.Windows.CapturePicker_cw5n1h2txyewy - Required for Screen capture function Microsoft.Windows.FilePicker_cw5n1h2txyewy - Required for Modern File open/save dialog Microsoft.Windows.PinningConfirmationDialog_cw5n1h2txyewy - Required for Pin to Taskbar MicrosoftWindows.UndockedDevKit_cw5n1h2txyewy - Required for Settings and OOBE
The below command will get the list of all packages excluding the language related. Code: Dir Windows\servicing\Packages\*.mum | findstr /v "en-US"
Code: :: Saving & Un-Mounting Source Boot Images for /l %%i in (1, 1, 2) do ( if exist "%BootMount%\%%i" ( if "%IsBootImageSelected%" equ "Yes" ( echo.------------------------------------------------------------------------------- echo.Applying Changes ^& Un-Mounting [Boot.wim, Index : %%i] Image... echo.------------------------------------------------------------------------------- call :UnMountImage "%BootMount%\%%i", "Commit" call :RemoveFolder "%BootMount%\%%i" ) ) ) :: Optimizing Source Boot Image with Maximum Compression. echo.------------------------------------------------------------------------------- echo.Optimizing Source [Boot.wim] Image with Maximum Compression... echo.------------------------------------------------------------------------------- call :ExportImage "%BootWim%", "%Temp%\rebuildBoot.wim", "WIM", "No" move /y "%Temp%\rebuildBoot.wim" "%BootWim%" >nul Yes, I was going to ask about it. But now the question would be different. How could we do the conditions? They would have to be based on: if "%ImageBuild% geq "18362" if "%ImageBuild%" leq "18363" if %ImageServicePackBuild% gtr 1400 ( if "%ImageBuild% geq "19041" if "%ImageBuild%" lss "19042" if %ImageServicePackBuild% gtr 900 ( So: From which CU build did Edge Chromium begin to be forced?
I've used ISO for 19043.899 from UUP Dump, I've removed Edge Chromium (I guess) with the Toolkit, however in VM, Edge was still there.
I don't know from which CU but noticed with the current preview CU, knew that for v2004 it will be bundled but now even for 1903/9 it's been added, for v1809 it's not included. Now it's a mess first they released a Edge Chromium standalone update package which will copy the edge files to WinSxS folder and later gets installed on first boot. Then they included Edge Chromium package with 1909/2009 Enablement package which did the same as Edge Chromium standalone update package, later they released sysprep images with Edge Chromium installed. Now they included Edge Chromium as a .wim image embedded with-in the CU which gets applied to the Install.wim like I did created Edge Chromium Pack earlier for Toolkit. Don't know whether they will stop releasing Edge Chromium standalone update package or including it with Enablement package, I hope they do stop it and follow the Current CU embedded method so that it would be easy to check for Edge Chromium existence and removal. Soon or later the removal program needs to be update to current CU so it doesn't matter from which CU it's been included.
But then there is no need to place conditions. Simply place the Edge Chromium to be displayed in the menu. If it is present, in a way that the toolkithelper current version recognizes it will be removed. otherwise, only that message will appear: "This component has already been removed." Edit: Today I had time to get involved in the Custom Toolkit, and I decided to merge with the last cmd that you posted on the 22nd. I'll take advantage and leave this option active, as well as some Custom typos have been fixed and the optimization has been implemented.
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-793#post-1606110 Sent an 2021-03-31 updated file in the link above. Spoiler: CHANGELOG 2021-03-31 Merged with Toolkit.cmd 11.4 2021-03-21 included in MEGA on 2021-03-22. Fixed Custom Toolkit typos: in the :StartIntegration session that was skipping Integrate Custom Features; in Select EdgeChromium to remove, for ImageBuild Greater than 19041. EdgeChromium display conditions, removed. It is now displayed in the Menu for any Build. If the Edge Chromuim is not present or the removal method has to be updated, at most that familiar message will appear: "This component has already been removed." Optimization of boot.wim and WinRE.wim has been implemented, regardless of whether they are mounted or not, whenever we save our work they will be optimized. Improved :WIMExport session code. Code: [1] Just Create a New [Install.wim] [2] Create a New [Install.wim] and replace the previous one. [3] Add selected Image Indexes to the same [Install.wim] Note: The chosen ones will be added after the already exists Image Indexes Enter your choice : Before I didn't have the option to replace it, I needed it today, then I put it there. Spoiler: CHANGELOG 2021-03-16 Merged with Toolkit 11.3 and 11.4. *Some Custom Toolkit Tweaks and Remove Menu minor fixes and code improvement. Returned to the Toolkit standard aspect Ratio. In this way, all the menus that require more space to show the menus on the screen, have been divided into more screens. just press B to Back and N to Next. This, just to avoid the use of scrolling with each choice made in the menu, which you are working on. Get ImageBuild from updated Image system, implemented to correct the error in the automated making ISO label and file name. All the environment and path variables for the packs were concentrated in some sessions, at the beginning of the custom toolkit. This way it is easier to reset the variables at each integration performed. Also so that the multiple choice system facilitates the multiple integration of features sequentially. Multiple choice has been implemented within the integrate menu, for all features that are submenus. In other words, if it is a sub menu, a negative sign will appear as a default. If it is to integrate this signal it will become positive. To apply the integration you must go back to the "Integrate Menu" and choose "Start Integration". In the options without signaling, integration will occur as soon as you select. These are the submenus mentioned: IntLanguagePacksMenu (tested) IntDriversMenu IntInboxAppsMenu IntRSATMenu IntOfficeUWPAppsMenu IntDaRTMenu (tested) IntThinPCpkgsMenu IntGamesMenu (tested) IntCustomFeaturesMenu (tested) Note: As I said earlier in the post below, these changes were made in order to implement the multiple choice system in the menus but there may be variables that do not get the values set and end up breaking something. We always think that we thought of all the possibilities until we found something new to be corrected or improved. As I said before, I can't test everything here for lack of storage space. Then, for final images of daily use, make integrations with the Official Toolkit. Removal, Customizations, Tweaks, can be done with Custom, if you want. So, it is necessary that this part be tested by volunteers. I am grateful for the feedbacks. Thnks! Edit: I forgot to mention changes in the session: WIMExport. Added in today's changelog.
I also thought like you. Currently, I do not exchange UUP Dump for anything. The Script downloads only the updates that are needed. If CU already has an update, it does not download duplicate. Whenever I download a new version, I go inside the UUPs folder and delete all the files "windows10.0-kb * .cab" the rest are only windows system base files, there is no need to download again. If there is such a need, the script checks the hashes and deletes and downloads the new version. It is much more practical.
Wait... what? People on 1809 LTSC will get Edge Chromium installed when installing a CU? From which CU did this start? Is every CU going to add it back?
Only the condition to check the CU is not required as right now Edge Chromium is not included with 1809 CU yet, it may ne included in patch Tuesday update as there's a pattern with CU which I have seen that the fixes added to CU for latest Windows 10 version will be added to older version in next release.
No for 1809 it's not included yet, need to wait for next CU to see if get's included or not, right now for v1903/19H2, 2004/20H2/21H1 it's been included.
Well, if they've gone back to 1903 and stop there, great, but I can't imagine they'd miss any opportunity to force their garbage on more users. I will have to find a way to manually remove it because I don't want to be rebuilding images every month. This is exactly why I stay 2 CUs behind.
Much more pratical. You are genius. Definitely, in the future, i will use your method. Thank for that. It will facilitate my life now.