Forum Discussion
About most proper way to report a Startup boost issue experienced whenever I suspend OS...
@ MS Edge Product Team, (please note that I just simply edited some content on 9/13 to only make some things clearer and obviously not to repost it at all, also if you should believe Enterprise migh...
Just updating this again discussion after noticing it was silently unlocked by Admins and released to normal discussions.
Since now I'm on v96.0.1054.43 I'm not really expecting more updates on this and I also believe same issue I reported was only dued to some Edge components that had remained stuck in memory, probably also MicrosoftEdgeUpdate.exe.
I also reported more about this same component in another discussion ('Which update impact might Edge Enterprise have if running a non updated 'MicrosoftEdgeUpdate.exe'?') that I already closed some near end of September after realizing what quite likely happened for that situation.
Anyway because after solving that issue, also the one I reported here never happened again I'm quite confident to say that it was probably only dued to a side effect of those same components stuck in memory.
P.S. Nevertheless, (sorry for adding this here even if obviously off-topic for this discussion, but anyway it's for anyone else awareness too), even if same issue described here never appeared again, I still noticed that whenever MicrosoftEdgeUpdate.exe receive an update, it still continues to not fully update itself into %ProgramFiles(x86)%\Microsoft\EdgeUpdate folder.
So after its own self update complete anyway, I typically need to temporarily manually rename old executable (obviously while not already running) still left in same folder as 'MicrosoftEdgeUpdate_old.exe' then manually copy updated version from own subdirectory also in that same path (.\1.3.153.53 was last update I received after mid November) and then also manually set new MicrosoftEdgeUpdate.exe ownership to SYSTEM as last step since originally found already set same way before.
BTW at least I saw that any 'MicrosoftEdgeUpdate_old.exe' I've still left in same folder above always gets self-deleted while MicrosoftEdgeUpdate.exe (almost fully) self-updates again.
I'm wondering why doing this cannot be self-automated during MicrosoftEdgeUpdate.exe self-updates so to ensure same component if always fully updated too when executing.
Thanks anyway for your attention.
Regards
Rob
Since now I'm on v96.0.1054.43 I'm not really expecting more updates on this and I also believe same issue I reported was only dued to some Edge components that had remained stuck in memory, probably also MicrosoftEdgeUpdate.exe.
I also reported more about this same component in another discussion ('Which update impact might Edge Enterprise have if running a non updated 'MicrosoftEdgeUpdate.exe'?') that I already closed some near end of September after realizing what quite likely happened for that situation.
Anyway because after solving that issue, also the one I reported here never happened again I'm quite confident to say that it was probably only dued to a side effect of those same components stuck in memory.
P.S. Nevertheless, (sorry for adding this here even if obviously off-topic for this discussion, but anyway it's for anyone else awareness too), even if same issue described here never appeared again, I still noticed that whenever MicrosoftEdgeUpdate.exe receive an update, it still continues to not fully update itself into %ProgramFiles(x86)%\Microsoft\EdgeUpdate folder.
So after its own self update complete anyway, I typically need to temporarily manually rename old executable (obviously while not already running) still left in same folder as 'MicrosoftEdgeUpdate_old.exe' then manually copy updated version from own subdirectory also in that same path (.\1.3.153.53 was last update I received after mid November) and then also manually set new MicrosoftEdgeUpdate.exe ownership to SYSTEM as last step since originally found already set same way before.
BTW at least I saw that any 'MicrosoftEdgeUpdate_old.exe' I've still left in same folder above always gets self-deleted while MicrosoftEdgeUpdate.exe (almost fully) self-updates again.
I'm wondering why doing this cannot be self-automated during MicrosoftEdgeUpdate.exe self-updates so to ensure same component if always fully updated too when executing.
Thanks anyway for your attention.
Regards
Rob