Forum Discussion

jdbst56's avatar
jdbst56
Brass Contributor
Mar 20, 2021

Edge 89 Stuck In Update/Restart Loop

We are deploying Edge updates through our local WSUS, and we have the Update policy override default policy set to enabled and Updates Disabled so that Edge does not update from the Internet.  Since upgrading to Edge 89, we have been having issues with Edge prompting that it needs to update and restart, even though no updates are available through WSUS.  When this happens, the user selects restart which restarts Edge, but the prompt will come back about an hour later.  It almost appears that Edge is seeing that an update is available online even though it is not yet synced to the WSUS repository.  Right now we have 89.0.774.54 deployed but we are aware that 89.0.774.57 came out on 3/18, although it has not yet synced into our WSUS.

 

I am aware that there are two scheduled tasks and two services that trigger Edge updates.  The one scheduled task runs every hour.  I have attached the log file from the MicrosoftEdgeUpdate.exe service, but it is not particularly helpful.

 

This issue is very annoying for our end users and didn't start until we updated from 88 to 89.  Complete removal of Edge and the Edge Updater service and reinstallation does not resolve the issue.

 

Group Policy Configuration is as follows:

 

Enable component updates in Microsoft Edge Disabled
Notify a user that a browser restart is recommended or required for pending updates Enabled
Notify a user that a browser restart is recommended or required for pending updates Required - Show a recurring prompt to the user indicating that a restart is required
Set the time period for update notifications Enabled
Set the time period for update notifications: 3600000
Update policy override default Enabled
Update Policy Updates disabled
Update policy override Enabled
Update Policy Updates disabled

 

Any assistance with this issue would be appreciated.

 
  • jdbst56 Hello!  Sorry to hear about the issues that started with v89.  I'm reaching out to the team to check if this is a known issue.  

     

    If you haven't contacted MS Edge Support (https://microsoftedgesupport.microsoft.com/hc/en-us)  already, they would be a good option to help troubleshoot and gather any necessary logs to investigate your specific case.  

     

    I can follow up here if I receive any updates.  Thanks! 

     

    -Kelly

Resources