Aug 20 2021 09:47 AM
Aug 20 2021 09:47 AM
We are using Edge on a special-purpose disconnected Environment (Network without any Internet Connectivity). EdgeUpdate Policies are configured as follows to turn off automatic updates (which cannot be done "online" in this environment). We are deploying Edge and Edge Updates using MSI-Packages with our own Depoyment-Mechanisms, but we have no need to roll out every single new Edge-Version, we update Edge after testing the compatibility for this special purpose about every 3 months).
But what happens after some time is, that Edge annoys the Users to Update because "Microsoft Edge is out of Date". This pops up every Edge start. This seems to be a bug, because if Updates are disabled by policy the user of course should not be annoyed - IT is taking care of the updates!
Kindly asking @Kelly_Y for support to forward this to the right team.
Aug 20 2021 03:40 PM
@Gunnar Haslinger Happy Friday! Yes, I've reached out to the team about the message. We'll let you know any updates or if there are any follow up questions. :) Thank you!
Aug 23 2021 11:38 AM
@Gunnar Haslinger Hi! Couple of things we wanted to confirm and just double check.
Is the AutoUpdateCheckPeriodMinutes policy set to 0 so all auto-update checks are disabled? (Basically since you folks are controlling the updates)
Aug 23 2021 11:55 AM
Aug 27 2021 03:38 PM
@Gunnar Haslinger We've been continuing conversations internally about your issue :) Would you be able to provide the latest MicrosoftAutoUpdate.log/MicrosoftEdgeUpdate.log from one of the devices?
Should be found at %ALLUSERSPROFILE%\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log (You can send it via message if you prefer.)
Aug 30 2021 12:09 AM
Here you find my full MicrosoftEdgeUpdate.log: https://link.hitco.at/EdgeUpdate-Log
The machine I took this LogFile from was fresh installed on 08. July 2021 - same date where the Log starts. Machine was only used for a few times as you can see when looking at the date/timestamps in the log. It is displaying the warning every time edge starts, as I described and screenshotted above. It was never connected to the internet, we update and patch those machines via MSI-Deployment (not a Microsoft Update Infrastructure like WSUS).
[08/30/21 08:32:47.817][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][DllEntry]["C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" /ua /installsource core] [08/30/21 08:32:47.817][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][C:\Program Files (x86)\Microsoft\EdgeUpdate\184.108.40.206\msedgeupdate.dll][version 220.127.116.11][opt][official] [08/30/21 08:32:47.817][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][is machine: 1][Current dir][C:\Program Files (x86)\Microsoft\EdgeUpdate\18.104.22.168] [08/30/21 08:32:47.817][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][GoopdateImpl::DoUpdateAllApps] [08/30/21 08:32:47.832][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][OS EULA check returned false or failed][0x00000000] [08/30/21 08:32:47.832][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][IsEULAAccepted][OOBE completed] [08/30/21 08:32:47.832][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][ShouldCheckForUpdates returned 0][checks disabled] [08/30/21 08:32:47.832][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][Update check not needed at this time] [08/30/21 08:32:47.832][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][Update all apps process finished][0x0] [08/30/21 08:32:47.832][MicrosoftEdgeUpdate:msedgeupdate][2336:3868][DllEntry exit][0x00000000]
Aug 30 2021 07:41 AM - edited Aug 30 2021 07:44 AMSolution
As there were some new customer-Tickets opened the last days I did some more debugging and compared "old" machines which seem to work fine with newer ones which have this issue.
MicrosoftEdgeUpdate.log doesn't give any hints. Log of machines having this issue look exactly the same like machines which are fine.
I compared the Registry Key/Values of EdgeUpdate in depth and found the solution as follows:
This setting works fine:
But on the newer machines having this issue the value "brand" is configured "GGLS" instead of "GCEU". I tried it both ways:
According to docs.microsoft.com - Windows diagnostic events and fields this value seems to have following semantic: appBrandCode The 4-digit brand code under which the the product was installed, if any. Possible values: 'GGLS' (default), 'GCEU' (enterprise install), and '' (unknown).
Both Machines are Windows 10 Enterprise v1909, same hotfixes applied. I have no Idea why "brand" is configured "GGLS" in the newer installed ones. But I have the idea that this is because of EdgeHTML was replaced by EdgeChromium out of the box on the newer Installation-ISO-media which is used for our unattended deployment. Seems the included EdgeChromium in the new ISO-Image has this preconfigured in a wrong way?
Aug 30 2021 12:06 PM
@Gunnar Haslinger Thank you for doing all that investigation! I've passed this all on to the team! We will let you know any updates from them.