Forum Discussion
Solved
Which update impact might Edge Enterprise have if running a non updated 'MicrosoftEdgeUpdate.exe'?
Hello, could anyone please be so kind to tell me something about which update impact might Edge Enterprise (Stable) have if on my OS there's still running a non updated version of 'MicrosoftEdgeU...
KenChong (again & other insiders interested as well...)
In addition to correcting my last week reply (Sep 18 2021 07:05 AM) with main KB article I was really considering with Edge known update statuses, I can finally confirm I found a definitive answer also to my last past assumption about the (annoying) always indefinitely rolling icon seen while 'Checking for updates' remained displayed forever.
That was indeed another issue and only today I also definitely discovered it was related to running a 'partially only' updated 'MicrosoftEdgeUpdate.exe' (again by 'partially only' I mean to indeed have previous 'MicrosoftEdgeUpdate.exe' v1.3.147.37 still running one together with only its main supporting DLL 'msedgeupdate.dll' correctly updated to v1.3.151.27 as expected, but nevertheless and strangely enough :-s 😛 inside 1st main log file listed below reported version is v1.3.151.27).
So for everyone's sake here's how I found it out and then finally & definitely solved it (apologies in advance if it may seem long, but I'm already summarizing all at my best).
At first I had to spent quite some time checking contents of the 2 main log files updated regularly (C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log) and only during updates (C:\Windows\Temp\msedge_installer.log) and since 1st file still continued to be updated properly even while 'Checking for updates' status never changed and I indeed received Edge updates, I decided to only focus on it.
So this (early) morning I found which component ('MicrosoftEdgeUpdate.exe' /broker) normally logging inside it, instead stopped updating it properly (since 08/20) even if it was still running since then (& probably simply just stuck in memory).
After checking all handles it had open (& luckily not locking itself either), I renamed it then copied its updated v1.3.151.27 version in same execution path (C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe) and assigned same file ownership (SYSTEM) of old file, then manually forced closing all few handles it still had opened (those listed by handle64 SysInternals as File at 1st, then all remaining listed as Section) and finally forced closing it.
I was also quite surprised to see that it self-started running again for about 14minutes more, but this time it was indeed v1.3.151.27 updated version and at the end it also properly quitted from memory (as typically expectable and already done in the past).
At the end I started Edge (still v93.0.961.52) then opened Settings -> Help and feedback -> About Microsoft Edge and voilà 'Checking for updates' status changed almost immediately since it found a new update and started downloading it, so once it completed I pressed (expected) [ Restart ] button and so now I'm already on v94.0.992.31 😄 (but quite strangely enough new 'welcome tab' that self opened still looks empty).
Regards
Rob
KenChong again (& other insiders as well...),
another update for your awareness of what else I've verified.
Even if running 'MicrosoftEdgeUpdate.exe' (with /broker option on my laptop) is not latest yesterday I also additionally noticed that anyway it's already running together with msedgeupdate.dll from latest v1.3.151.27 update subfolder that was also received during my installation of Edge Enterprise, so now I'm expecting that most of real versioning logic might indeed be there.
And this also (side) explains quite good why ITMT my Edge Enterprise already received and installed properly v93.0.961.47 since 9/13 (late afternoon in my TZ).
P.S. Only issue (indeed quite annoying) I see at this point is the never ending rolling icon that appears near 'Checking for updates' and that so far was no more able to properly tell me that another update was available or even that it already took place and it's only just awaiting me to restart Edge (& so far I only saw this message while I was still working into Edge when 1st update took place from v92.0.902.73 to v92.0.902.84 😮 ).
Regards
Rob
Glad that you fixed the problem!
Regards,
Ken
Regards,
Ken
KenChong (again & other insiders interested as well...)
In addition to correcting my last week reply (Sep 18 2021 07:05 AM) with main KB article I was really considering with Edge known update statuses, I can finally confirm I found a definitive answer also to my last past assumption about the (annoying) always indefinitely rolling icon seen while 'Checking for updates' remained displayed forever.
That was indeed another issue and only today I also definitely discovered it was related to running a 'partially only' updated 'MicrosoftEdgeUpdate.exe' (again by 'partially only' I mean to indeed have previous 'MicrosoftEdgeUpdate.exe' v1.3.147.37 still running one together with only its main supporting DLL 'msedgeupdate.dll' correctly updated to v1.3.151.27 as expected, but nevertheless and strangely enough :-s 😛 inside 1st main log file listed below reported version is v1.3.151.27).
So for everyone's sake here's how I found it out and then finally & definitely solved it (apologies in advance if it may seem long, but I'm already summarizing all at my best).
At first I had to spent quite some time checking contents of the 2 main log files updated regularly (C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log) and only during updates (C:\Windows\Temp\msedge_installer.log) and since 1st file still continued to be updated properly even while 'Checking for updates' status never changed and I indeed received Edge updates, I decided to only focus on it.
So this (early) morning I found which component ('MicrosoftEdgeUpdate.exe' /broker) normally logging inside it, instead stopped updating it properly (since 08/20) even if it was still running since then (& probably simply just stuck in memory).
After checking all handles it had open (& luckily not locking itself either), I renamed it then copied its updated v1.3.151.27 version in same execution path (C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe) and assigned same file ownership (SYSTEM) of old file, then manually forced closing all few handles it still had opened (those listed by handle64 SysInternals as File at 1st, then all remaining listed as Section) and finally forced closing it.
I was also quite surprised to see that it self-started running again for about 14minutes more, but this time it was indeed v1.3.151.27 updated version and at the end it also properly quitted from memory (as typically expectable and already done in the past).
At the end I started Edge (still v93.0.961.52) then opened Settings -> Help and feedback -> About Microsoft Edge and voilà 'Checking for updates' status changed almost immediately since it found a new update and started downloading it, so once it completed I pressed (expected) [ Restart ] button and so now I'm already on v94.0.992.31 😄 (but quite strangely enough new 'welcome tab' that self opened still looks empty).
Regards
Rob
KenChong again (& other insiders as well...),
if interested I've re-edited again my past (Sep 13 2021 08:51 AM) reply having steps A) & B) so that now to avoid the 2 msedge.exe background instances a much faster new step A) exists while old ones were shifted to B) and C) respectively.
P.S. FYI I'm also about to 'Send feedback' (bug) also the always rolling icon 'Checking for updates' that I see because of the different already known typical statuses I found into support KB article 'MS Edge update settings' (a correction was needed here because 'Troubleshooting tips for installing and updating MS Edge' indeed only contains some status messages but those can be found in particular conditions).
Best Regards
Rob
Ehm, I'm not so sure yet. When I opened my question/discussion I was simply unsure about what to expect, but unluckily so far I'm still not 100% if any more problems might be found.
Maybe a known one might be the one I documented of an update still only remaining in pending state because of the 2 msedge.exe instances still unexpectedly running in background even if this wasn't really expected to happen (and its additional dump creation after OS resuming from being suspended into memory).Maybe another is the (annoying) always indefinitely rolling icon seen while 'Checking for updates' is displayed... (this because IMHO if after some seconds Edge should be still unaware of updates availability then it also should give user a proper message...)
Regards
Rob
