![]() ![]() ![]() ![]() 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.Īs 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. 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).ģ. 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.Ģ. default removed in the WinSxS folder also with NTL / Remove Components so that future LCUs can be installed due to ServicingStack Compibitibility.īut 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.Ĭlick to expand.Hi francis11, I posted this toolkit here for two reasonġ. If I remove the new EC with NTL in the Components section, the EC files remain in the WinSxS folder. 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. It seems on this page of 21H2 that EC is a fixed part of the monthly LCU updates and can not be ignored.įor 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. 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. ![]() Requesting the dev nuhi & all the interested members to download & check this & share your valuable inputs here in this regard, thanks. 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. 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. One is by creating a new REG entity & another one is configuring the GPE. I downloaded this & noticed there is a CMD script that consists of two parts to block EDGE fully. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |