Forum Discussion
Bug: Edge v104.0.1293.54 always unable to start after own update on v103.0.1264.77 (Stable)
Hello all, 3 days ago my client still running Edge Enterprise v103.0.1264.77 (Stable) received via MicrosoftEdgeUpdate.exe (v1.3.165.21 updated manually by me to avoid unexpected effects, if also...
Kelly_Y(and others) Hello again,
I'm updating this thread once more because same issue I reported initially on Sep 24 2022 faced again yesterday after 2 days ago my OS received latest/current Edge Enterprise v109.0.1518.95, while v109.0.1518.78 was still running.
Once again issue is being experienced after another unexpected OS freezes occurred, but nevertheless I'm also quite sure this is not related to issue because I always make sure CHKDSK C: /X /V can run at every boot if needed, and then after proper boot, inside Application Log Wininit Event ID 1001 I always find the sentence 'File system check completed. No problem found'. Also since I know this topic has become a little too much TL;DR for you all (I'll just continue summarizing issue status as much as I can).
Quick workaround only recap : as I said still same found and described in the past to be able to run current Edge Enterprise v109.0.1518.95 (so only using an elevated IE11 InPrivate session to view a frame embedded YouTube video hosted in a local web site page and initially inside same IE11 tab, to then try to switch video display to YouTube directly, allow me to "magically" see a new Edge InPrivate session starting correctly, so that after I can use again standard Edge icon in OS Application bar to then see Edge start correctly and also be able to fully recover all previously already opened standard windows and sessions).
Of the several attempts I did to run only 1 created a new .dmp file that I already submitted via another 'Send feedback' I already sent yesterday.
ASAP I'll also try to see if manually forcing Edge to restart or close all its opened windows might make any difference in using known workaround or possibly revert Edge to normal usage.
ITMT I already made sure to empty Edge cache (something that so far I haven't been doing so very often 😮 :-s ).
Best Regards
Rob
@Kelly_Y(and others) Hello again,
just another update for this thread topic that I know looks still too much TL;DR for you all (& I'm just continuing to summarize issue status as much as I can).
After one more unexpected OS issue (on Fri 03/31 and this was a complete BlueScreen for a STOP 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA, and I verified BugCheck 0x50 occurred during a write operation and apparently caused by NPFS.SYS, once again CHKDSK C: /X /V ran at next boot as expected, and once again inside Application Log Wininit Event ID 1001 I found usual sentence 'File system check completed. No problem found'), this time I'm quite happier to tell you that my past known workaround was no more needed and so I was able to correctly start current Edge Enterprise v109.0.1518.95 from basic icon in OS Application Bar and as always it could recover all its opened windows and sessions.
Since I did very little it seems that manually emptying Edge cache more often (something that now I've started doing some more frequently than before 😮 :-s ) might have probably brought some benefit, but only time will tell if this is really true.
ASAP I'll also check if manually forcing Edge to restart or close all its opened windows via quick shortcuts that I've been able to create (thanks @Noel_Burgess for confirming this in another thread question I asked in March) might make any difference too to still avoid using weird known workaround I reported above in this same and again continue to use Edge normally.
Best Regards
Rob
