Do the Group Policy templates actually work for stopping/controlling Microsoft Edge Updates?

Copper Contributor



I am current testing MS Edge for Business with the specific goal of controlling the update cadence for the Stable channel. I want complete control on when these updates are applied and ONLY deploy them in a small business environment via WSUS or ManageEngine Desktop Central.


I have downloaded the current policy files for Edge Business and studied the update attributes and items found here:


But I have some serious concerns about the validity of these group policy templates. I have been unable to determine the exact policy combination to get the updates to stop while continuing to allow Edge's default payloads to be enabled (3 Services and 2 scheduled tasks that appear in Task Scheduler) after a standard install OR an update?


I have been testing this a lot for weeks now and in a stock install of Edge for Business - either a new install OR an update to an existing install - the installer adds (AND reactivates if disabled) the following services:





It also adds (and re-enables if disabled) the following tasks into Task Scheduler as well:





These 5 items – if present and enabled – would seem to allow Edge to update itself like it would in a consumer environment - by itself - every hour on the hour regardless of any GP that may be enabled.,


The only way I have found to exert any control over the updates is to set these policies (Via GPEDIT)




And then run a standalone PS script that actually DELETES the scheduled tasks and disables two of the three services. But I should not have to do this much work.


Q: Does the group policy (Update policy override setting) actually override/stop the activity of these 3 services and 2 tasks? 


While I always believed that GP should be the law - I am skeptical if these services and tasks are actually taken out of the equation with the GP (Update Policy Override) enabled. 


And even with all this extra work - if a user goes and opens the "..." menu in the upper right and then choose Settings->Help and Feedback->About Edge - Edge will then attempt update itself here as well - which I also do not want my users to be able to do.


Ideally what I really want is this to display if a user attempts to select "About Edge":




Appreciate any update on how to completely control the Edge Update cycle and have the system ignore these tasks and services that it places on the machine during each update.





7 Replies

@Bruce_McDonald Thanks for reaching out. I'm looping in our Enterprise team and will let you know if they have any insights to share.


Fawkes (they/them)
Project & Community Manager - Microsoft Edge



Thanks for the update!


I am finding it very odd that there is not a lot of guidance on this subject. You would think there would be a simple article somewhere on the web saying "make the following settings and Edge is under control" :)


OR - every other admin worldwide has either figured it out OR is letting Edge update itself automatically and not worrying about auto updates.


Edge for Business (the browser itself) is very very good - if I can get the update cadence reeled in a bit for my users - that would just about make it perfect.






@Bruce_McDonald I'm glad that Microsoft Edge is working well for your Enterprise environment! While we wait to hear back from the team, I will do my best to address your questions.


For documentation: this landing page is your go-to source for all MSFT Edge information. After a quick search, I came across details for this policy, which may help answer your question. (In full disclosure, this is not my feature area, so please use your own discretion regarding its applicability to you.)


From what I've heard from other Admins, they let the browser update automatically and just keep an eye on our shipping cadence. (Our releases roughly align with the Chromium schedule, in order to deliver cohesive browsing and developing experiences.) We also recommend allowing automatic updates to ensure that your machines receive any/all intermittent bug fixes or security patches. 


Fawkes (they/them)
Project & Community Manager - Microsoft Edge


Appreciate the info and update.

While I may consider letting Edge update itself in the future - it needs some maturity and historical context before I would consider it. All you need is one dicey update to wreak havoc. Would rather be safe than sorry.

Having full control of the app update cadence is well established here and would most certainly apply to vetting major items like the web browser.

Hoping that the enterprise team can shed some light on what is happening here so I can sort this out quickly. Should not really be this difficult. By way of contrast - Chrome is super easy to control and has a specific set of policies that just work all of the time.


best response

Hi @Bruce_McDonald,


Setting the "Update policy override" to "Updates disabled: Updates are never applied" will prevent Edge from being updated on any domain-joined machine. Setting this is sufficient to prevent any updating from happening. When configured, the services / scheduled tasks will not update the browser. They're still scheduled in the case that the policy changes from "off" to "on". 




Andy Zeigler

Edge Team








Appreciate the update - but does the logic apply to a "non-domain" joined machine? I manage several small business layouts and there are no domains present.


And - what does this setting do if a user chooses "About Microsoft Edge" from Help and Feedback under the main menu on the right. This action kicks in the upgrade mechanism and I need to close that vector as well.


Please advise.









Would also like some insight into what the Edge "About Edge" dialog is doing once that GP/Reg edit you suggested has been placed. During testing this week - I see that the dialog now displays a different, more confusing message:




This now indicates that "something" is happening and to come back in a bit and see what it is. When I come back into "About Microsoft Edge" 5 minutes or 10 minutes or any minutes after - the same message appears - yet the version of Edge installed does not change.


So - while the GP setting seems to work - it would just be nice if the user was told straight up that the updates are "Managed By your Organization" like this:



I also found out today that this message above only appears if Edge is running on a domain connected device. All of my user machines are in a workgroup and do not display this message.