edgeupdate Service on Windows Server 2016 1607

Topic

New Reply

Both of my Windows Server 2016 1607 servers (one physical hosting one virtual) have been updated with Chromium Edge. The issue is “Microsoft Edge Update Service (edgeupdate)” is installed as an “Automatic (Delayed Start)” service. But on both Server 2016 and Windows 10, it seems to start and then shortly shut down. Probably fine on Windows 10, but on the Server 2016 Server Manager Dashboard, it shows as an error condition since an Automatic service is not running.

I have changed the service startup to Manual, but something keeps changing it back. I’d rather not disable that service, since I do want Edge to get updated. But I do want my Dashboard to show only actual errors, not “pretend” errors. I do have WSUS installed, so maybe that will update Edge?

Any suggestions? Thanks.

Reply | Quote

Replies

Hi Kurtl, I am afraid this unwanted behaviour is by design and they have not considered the Server Manager here. I am linking this to twitter. But please report it in Edge on Windows Server and let them have a screenshot Alt+Ctrl+I. They are really responsive to your feedback and if you include your email you also get questions or updates on your requests.

Best regards,

Karl

1 user thanked author for this post.

kurtl

Reply | Quote

I deleted both the “edgeupdate” & “edgeupdateM” services from the Windows Registry [located at “HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\edgeupdate” and/or “HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\edgeupdatem” in (regedit.exe)] so that they won’t load at all and won’t silently update MS Edge.

also need to set “MicrosoftEdgeElevationService” to Disabled in services.msc in order to prevent MS Edge from silently restoring the “edgeupdate” & “edgeupdateM” registry keys [until MS Edge was updated manually by installing a new version over the old one, then setting the “Microsoft Edge Elevation Service” to disabled will have to be performed again]

Reply | Quote

The correct way to do this is using Sc delete or PowerShell Remove-Service (PowerShell 7)

you should not delete only registry entries.

1 user thanked author for this post.

Microfix

Reply | Quote

On an endpoint machine not joined to a domain or not attached to a server, would performing the procedures detailed above prevent an administrator from launching Edge (Chredge) and manually having it check for updates through the built-in functionality of the Help and Feedback>About Edge menu item within the browser?

Reply | Quote

Cannot tell never tinkered with this.

Reply | Quote

So I found two solutions to this in my environment:

1. (the best): In Server Manager, click on Services for Local Server and All Servers in the Dashboard. Then in Services Detail View, click the Services drop down and uncheck any services you don’t want Server Manager to report on.
2. Disabled the “edgeupdate” and “edgeupdatem” services on just the Windows Server 2016 servers. Then I used WSUS Windows/ Microsoft Edge product to download and push updates. This was less than ideal as only the two servers actually needed the updates since all the clients are already getting their own Edge updates. Also, Edge updates are published frequently with Developer/ Beta/ and Production versions. So it was annoying to administrate.

Reply | Quote

If the servers are domain joined, you can create a group policy and link it to the OU the servers are in.

Set Computer Configuration – Policies – Windows Settings – Security Settings – System Services

Microsoft Edge Update Service (edgeupdate) = Disabled

Microsoft Edge Update Service (edgeupdatem) = Disabled

 

While you are at it, for Windows Server 2016 set

Downloaded Maps Manager = Disabled

Reply | Quote