amihost.blogg.se - Microsoft autoupdate cannot connect to update server

#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER PATCH#
#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER WINDOWS 10#
#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER CODE#
#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER WINDOWS#

Wuauclt /detectnow command line, you should find this line in it :

#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER WINDOWS#

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.How do I verify the Windows Updates are coming from my internal WSUS server instead of from MS Online Updates? Thanks for your help.Īs Lawrence said, if you take a look at your WindowsUpdate.log file after doing a I have no Idea why "brand" is configured " GGLS" in the newer installed ones.

#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER WINDOWS 10#

Possible values: ' GGLS' ( default), ' GCEU' ( enterprise install), and '' (unknown).īoth Machines are Windows 10 Enterprise v1909, same hotfixes applied.

#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER CODE#

I configured a " bad" machine which has this issue from "brand"=" GGLS" to "brand"=" GCEU" => OK, after restarting Edge the warning doesn't pop up again, Problem solved.Īccording to - 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.

=> configured back to "brand"=" GCEU" => Restart Edge => No Warning, OK.

I configured a good machine to "brand"=" GGLS" => Restart Edge => Brings warnings.

I compared the Registry Key/Values of EdgeUpdate in depth and found the solution as follows:īut on the newer machines having this issue the value " brand" is configured " GGLS" instead of " GCEU". Log of machines having this issue look exactly the same like machines which are fine. MicrosoftEdgeUpdate.log doesn't give any hints. Hey 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.

#MICROSOFT AUTOUPDATE CANNOT CONNECT TO UPDATE SERVER PATCH#

It was never connected to the internet, we update and patch those machines via MSI-Deployment ( not a Microsoft Update Infrastructure like WSUS). It is displaying the warning every time edge starts, as I described and screenshotted above. Machine was only used for a few times as you can see when looking at the date/timestamps in the log. July 2021 - same date where the Log starts. The machine I took this LogFile from was fresh installed on 08. Thanks you find my full MicrosoftEdgeUpdate.log: But those who complained about definitely had fresh installed machines where Edge v90 was the first Edge-Version which was installed.

But this is just a guess - I cannot verify this because not all Users open a ticket, some just keep clicking without notifying us. Those installed several month before which had Edge v87 installed and were updated to v90 in June seem to behave correct and don't show this messages. Not all of them show this behavior - my best guess is, that only machines which where new installed during June/July with Edge v90 as initial Edge Version show this behavior. the machines started complaining to be out of date in late July 2021 / beginning of August 2021. Next update of this machines will be v93 in September. We didn't see this behavior until we updated to v90 in June. this seems to be kind of "timebomb", because they cannot grab this information from an update-server. I have no idea why they are complaining about "Microsoft Edge is out of Date". These devices had no chance to reach Microsoft-Servers/Internet, never - not a single second in their lifetime.

Yes, as you see in my Edge Updates Policies Screenshot in my initial post AutoUpdateCheckPeriodMinutes ist set to 0. Hi for your questions, answers as follows: