Regarding integradetion of the blocking mechanism of the NEW Chromium based EDGE into the ISO

SM03

Active Member
Hi all,
Since MSFT now integrate the new Chromium-based EDGE into the LCU, so even after removing EDGE from NTLIte options while making an ISO & after installation that ISO (without EDGE), after receiving an LCU, EDGE eventually returns, so I recently found a script to fully block the new EDGE from MDL & sharing it here.

MicrosoftEdgeChromiumBlockerToolkit

I downloaded this & noticed there is a CMD script that consists of two parts to block EDGE fully. One is by creating a new REG entity & another one is configuring the GPE.

Now I know that the REG entity can be integrated via NTL while making the ISO, but I am not sure whether the REG entity is enough to block EDGE fully receiving from the (future) LCU(s) so asking, is there any way to add this script (along with the two ADMX & ADML file in it) to NTL fully, or in a splitted manner i.e. reg part from the registry adding section, & for the GPE configuration, I don't know how we can add/configure it via NTL, so posting here as a form of both, question, as well as suggestions.

Requesting the dev nuhi & all the interested members to download & check this & share your valuable inputs here in this regard, thanks.
 

francis11

Active Member
Hi - just another view on this.

Interesting despite the fact that the reg files are from 2019 and really just seem to be a tweak to update to the new Edge Chromium (EC) blocking.

It seems on this page of 21H2 that EC is a fixed part of the monthly LCU updates and can not be ignored.
Have so far only seen it in April LCU.

For others interested, I have been successful in removing the EC files from the WinSxS folder on the mounted image in NTL from an updated April version (19043.928) from uupdump, after which EC will not be installed. However, I will wait and test if the EC comes back after the May LCU or next uupdump update here at the end of the month as a precursor to the next LCU.

If I remove the new EC with NTL in the Components section, the EC files remain in the WinSxS folder.
Removed components are no longer pr. default removed in the WinSxS folder also with NTL / Remove Components so that future LCUs can be installed due to ServicingStack Compibitibility.

But maybe an exception should be made with the EC package before it probably becomes an integral part of Windows in the 21H2 version just like IE has been so far.
 

ege914

Active Member
i put abbodi's edge remover script at as task to windows boot.. and hide it via vbscript.... it runs at background at boot and removes edge if installed...
 

SM03

Active Member
Hi - just another view on this.

Interesting despite the fact that the reg files are from 2019 and really just seem to be a tweak to update to the new Edge Chromium (EC) blocking.

It seems on this page of 21H2 that EC is a fixed part of the monthly LCU updates and can not be ignored.
Have so far only seen it in April LCU.

For others interested, I have been successful in removing the EC files from the WinSxS folder on the mounted image in NTL from an updated April version (19043.928) from uupdump, after which EC will not be installed. However, I will wait and test if the EC comes back after the May LCU or next uupdump update here at the end of the month as a precursor to the next LCU.

If I remove the new EC with NTL in the Components section, the EC files remain in the WinSxS folder.
Removed components are no longer pr. default removed in the WinSxS folder also with NTL / Remove Components so that future LCUs can be installed due to ServicingStack Compibitibility.

But maybe an exception should be made with the EC package before it probably becomes an integral part of Windows in the 21H2 version just like IE has been so far.
Hi francis11 , I posted this toolkit here for two reason

1. Share this with all NTL members to check whether after applying this toolkit, whoever is running 21H1.9XX version of W10, can confirm whether EDGe returns when the next LCU installed or not.

2. Share this with all, especially the DEV, to find a more effective way to fully block EDGE via NTL option, if possible, because MSFT is making the integration tighter day by day by embedding it with LCu (earlier it was embedded with EP only).

3. As I said earlier, this toolkit has two parts to block edge, one is reg tweak & 2nd one is GPE configuration, so while am planning to make a new ISO adding this reg tweak to block edge, but IDK how can I add the GPO via NTL while making the ISO, so if anyone can help me out in that case, or if the dev is reading this then take this suggestion & consider to add these options in future NTL build to block new EDGE fully, that'd be beneficial for all of us, the users.

As you said, you will wait to check whether EDGe will return in May LCU or not, I request you to kindly add this toolkit to block edge via those two paths, & after receiving the May LCU, update here as you already said. I am going to do the same, gonna make an ISO adding this option (reg only, as don't know how to implement the GPE settings), then wait for May LCU to check whether EDGE is effectively blocking to get installed via the LCU or not, & revert here

i put abbodi's edge remover script at as task to windows boot.. and hide it via vbscript.... it runs at background at boot and removes edge if installed...

ege914 which script you're talking about? Can you share that here?
 

SM03

Active Member
ege914 & francis11

More interestingly, I found this recently over there in MDL
1.png
Gonna try this too via NTL, & wai for the result with May 21 PT LCU. Suggesting & sharing this same for you & all who's interested in this matter.
 

nuhi

NTLite developer
Staff member
SM03, thanks for the toolkit, unfortunately it just sets the "DoNotUpdateToEdgeWithChromium" reg value, which NTLite already does set on Edge Chromium removal.
I believe the point here is not about Edge returning via WU, but now it's part of Cumulative Update like any other component - in other words use Remove Reinstalls after updating.

If you see otherwise, and that any blocker works through Cumulative Updates (Win10 2004+), let me know.
 

SM03

Active Member
SM03, thanks for the toolkit, unfortunately it just sets the "DoNotUpdateToEdgeWithChromium" reg value, which NTLite already does set on Edge Chromium removal.
I believe the point here is not about Edge returning via WU, but now it's part of Cumulative Update like any other component - in other words use Remove Reinstalls after updating.

If you see otherwise, and that any blocker works through Cumulative Updates (Win10 2004+), let me know.
Hi nuhi

Firstly, I already checked(searched) for that reg entity i.e.
HKLM\SOFTWARE\Microsoft\EdgeUpdate "DoNotUpdateToEdgeWithChromium"=dword:00000001

in a system where the OS is modded via NTL with the latest EDGE removed option enabled, but there is no sign of that reg entity.

Honestly, I was expecting the same i.e. the presence of that reg entity in a 'NTLited' system OS installed, but as anything ain't there I found, so I shared this. This is surprising for me, but anyway, other users can confirm/share their side of the story on this.

secondly, about the concern, yes, that's the real issue right now, i.e. MSFT embedded EDGE with LCU now (instead of EP used earlier) so that will return on every month's Patch Tuesday with the help of the LCU.

Now for that matter, I found a FIX in MDL that I shared here, in this OP, Last Sunday, & was expecting you'd say anything over that too. I believed you might have missed that last post here, so highlighting again.

I already integrated these two fixes (Reg tweak+Empty EDGE folder in Programme File) into a newly 'NTLIted' OS installed into a spare system of mine & waiting for May-21 PT when the next LCU will come, to see/check whether EDGE will return or not.

Will update here.
 

nuhi

NTLite developer
Staff member
Retested now and the reg key is there on Edge Chromium removal.
I used a 21H1 image with updates and just Edge Chromium removal, checked results on both image itself and after setup, all good.
Tried to also remove legacy Edge after, to see if it maybe is cleaning it up, still there.

So how do I replicate what you saw, how to test for the missing reg key on removal?

Will keep the folder just in case, probably gonna get many comments about the leftover, but any extra reinstall block is welcome - until proven otherwise.
abbodi86 states that he did not try if online install works, and your results are questionable, so please retry the online block of it with the folder keeping method when you're at it next time.
 

SM03

Active Member
nuhi, ege914 & francis11

As today, MSFT officially released the 21H1, along with a new LCU 2021-04 CU+SSU KB5001391 [19041.964.1.12].msu, so I tried this LCU in my earlier mentioned 'NTLIted' installed Win10 v21H1.928, where EDGE is already removed via NTL while making the ISO & I applied both of the earlier mentioned trick to defer installing the new EDGE with LCU as discussed [Reg entity+placing blank Microsoft/EDGE folder in Programme files).

& this is what I get on 21H1.964, after installing the latest LCU 2021-04 CU+SSU KB5001391 [19041.964.1.12].msu over 21H1.928

1. Default browser is changed automatically from Chrome to EDGE after installing this LCU

3.png

2. EDGE is showing under START MENU & Setting/Apps with no ICON & insignificant amount of size occupied (16.0 KB). So, what does this means? Presuming the LCU tried to install EDGE but that was bypassed for those precautions taken to prevent edge installation? & for that, only a tiny amount of bytes received/occupied, with no ICON? Needless to say, if I click on the EDGE icon from the Start menu, nothing happens. Correct me if I'm wrong.
1.png


3. As if the edge is (somehow) already installed(?), it's showing the version info. Moreover, about those two precautions to bypass edge installation are intact, reg entity value/key didn't change or deleted, neither the Microsoft/EDGE blank folders are, that I placed over both Programme File & Programme File x86, nor contains any file inside it.
2.png

So here are my founding am sharing as I told earlier that I'd share, now, would like to know what do you think over this matter.

& francis11 & ege914, as you guys also mentioned that both of you are running some scripts & other tricks to prevent EDGE from being installed via LCU, just like me, so what's your experience after installing this latest LCU over 21H1.9xx? Share your side of the story to add more on this.
 
Last edited:

SM03

Active Member
i put abbodi's edge remover script at as task to windows boot.. and hide it via vbscript.... it runs at background at boot and removes edge if installed...
ege914

as you limit your profile view, so I can view your profile to PM, so asking here, can you share the script? requesting you to kindly PM me.
 
Last edited:

francis11

Active Member
Can confirm - none of all the (good) intended fixes work:

From 19041.1 to 19041.928 (KB5001330) with the folder trick from abbodi1406
(No sign of MS EDGE only remnants of old edge in user folders and startmenu shortcut not working)

From 19041.928 to 19042.928 (EP 20H2) and EdgeChrome get installed

Try again from 19041.928 to 19042.928 and this time add regfix:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate]
"DoNotUpdateToEdgeWithChromium"=dword:00000001

and still no luck - EdgeChrome come back

Then thinking about the regfix for not installing MRT from WU and try see if that work for EdgeChrome via WU (LCU) too, something like this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"DontInstallThroughWUAU"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"DontOfferThroughWUAU"=dword:00000001

and still no luck - EdgeChrome still get installed!

So it seems EdgeChrome is forced no matter what from MS via WU and is only removable after install/ LCU updates.

It get removed with NTL RemoveReinstalls if EdgeChrome is unchecked in NTL offline from beginning, and the Old Edge Startmenu shortcut as well!
 

ege914

Active Member
ege914

as you limit your profile view, so I can view your profile to PM, so asking here, can you share the script? requesting you to kindly PM me.

I made it into a exe file because it's really long to explain how to create a task and run a script in hidden mode at boot. So it is all automated solution now. If you want to see script inside. Just open the sfx file via winrar and look into the bat file.... its all open sourced.


this is just an automated method. script's removal part is taken from abbodi. so all credit goes to his original work. thanks
 
Last edited:

SM03

Active Member
Can confirm - none of all the (good) intended fixes work:

From 19041.1 to 19041.928 (KB5001330) with the folder trick from abbodi1406
(No sign of MS EDGE only remnants of old edge in user folders and startmenu shortcut not working)

From 19041.928 to 19042.928 (EP 20H2) and EdgeChrome get installed

Try again from 19041.928 to 19042.928 and this time add regfix:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate]
"DoNotUpdateToEdgeWithChromium"=dword:00000001

and still no luck - EdgeChrome come back

Then thinking about the regfix for not installing MRT from WU and try see if that work for EdgeChrome via WU (LCU) too, something like this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"DontInstallThroughWUAU"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"DontOfferThroughWUAU"=dword:00000001

and still no luck - EdgeChrome still get installed!

So it seems EdgeChrome is forced no matter what from MS via WU and is only removable after install/ LCU updates.

It get removed with NTL RemoveReinstalls if EdgeChrome is unchecked in NTL offline from beginning, and the Old Edge Startmenu shortcut as well!
francis11 did you read my comment here? In my testing I used 19041.1 ISO, removed old+new edge via ntl, & added all latest updates up to 19043.928 & installed that ISO, then updated to the latest 19043.964 via WU & the new EDGE didn't install. So believe you're missing on something otherwise it should work.
 

SM03

Active Member
I made it into a exe file because it's really long to explain how to create a task and run a script in hidden mode at boot. So it is all automated solution now. If you want to see script inside. Just open the sfx file via winrar and look into the bat file.... its all open sourced.


this is just an automated method. script's removal part is taken from abbodi. so all credit goes to his original work. thanks
ege914 as I wrote in my earlier comment here, already figured to stop EDge installation automatically via LCU, so now am reserving your script for the future, if MSFT block the folder tricks & EDGE somehow start installing again in future, I'll apply your VBS script.

Thanks, BTW, do you have anything similar for Windows Defender, because that's another thing too that returns after every LCU. & Am currently figuring out to block that too via EDGE, so asking. Let me know
 

ege914

Active Member
you are mistaken, its not defender that comes back. its the security center... nope i did not prepare for security center or defender since they are not softwares that can be easily removed. i use ntlite cleanup for that. and i made it also auto that works after windows update... but its not silence because nuhi is not adding any silent and unattended switches... i asked many times but he wont do it. so i am stuck with ntlite interface everytime i need to automaticly remove defender.
 
Top