Forum Discussion
Bug: Edge v104.0.1293.54 always unable to start after own update on v103.0.1264.77 (Stable)
Kelly_Y Hello and many thanks for confirming also which is current known status for Edge command line options.
Good to know that Eric Lawrence posted that article on his own blog, where I've already found some other interesting contents after Sep 21 when I investigated some more on resource.pak contents and usage, and while also trying to figure out if/which additional troubleshooting could be made for Application Log Event ID 256 (Source: Edge) error I also unexpectedly found recently and related to another OS reported corruption of an Edge extension that was installed months ago.
(Just adding some more details here too:
Source: Edge "[2508:13316:0921/171231.326:WARNING:chrome_content_verifier_delegate.cc(231)] Corruption detected in extension emejglhjgnlgoeefgcdpfihajdhlfjen installed at: C:\Program Files (x86)\Microsoft\Edge\Application\105.0.1343.33\resources\edge_share, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent"
...
Source: Edge "[23948:11212:0411/235326.953:WARNING:chrome_content_verifier_delegate.cc(233)] Corruption detected in extension emejglhjgnlgoeefgcdpfihajdhlfjen installed at: C:\Program Files (x86)\Microsoft\Edge\Application\99.0.1150.39\resources\edge_share, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent").
ITMT (yesterday), my client also received Edge v105.0.1343.53 but once again it hung (=stopped responding) on startup with no new dump created (inside C:\Users\<myAlias>\AppData\Local\Microsoft\Edge\User Data\Crashpad\reports) after I used same Edge default icon, I've put on OS Application bar since after 1st Edge installation ('"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --profile-directory=Default').
Anyway since with Edge not working I'm also without access to my mailbox on Outlook.com, I decided to do more attempts using same method (trying to access a YouTube hosted video after IE11 displayed another local web embedded page YouTube video) that already worked in the past with other versions (for more details about versions see above my previous posts).
After Edge hung again (=stopped responding) on startup during 1st attempt I did (right after my IE11 InPrivate window started as Admin opened a new tab confirming that proper browsing needed an updated browser too) I also noticed that MS Security Essentials was also still doing its weekly quick scan so I decided to do a 2nd attempt after end of scan and luckily enough this 2nd one succeeded and IE11 successfully started a new Edge InPrivate window (with this same command line that failed during 1st attempt '"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --from-ie-to-edge=1 --inprivate --customer-type=1 --flag-switches-begin --flag-switches-end --do-not-de-elevate https://www.youtube.com/watch?v=IdhK3jtBQOY&feature=emb_rel_end') while showing 2 tabs (1st one showing involved YouTube video, 2nd one, also with focus, displaying 'Javascript Manager' extension default home page, while this time IE11 new self-opened tab was only showing an empty page).
Only after this, just like in the past, I was still able to use same Edge icon I have in OS Application bar to restore proper status of 3 Edge standard windows that were still opened before another unexpected freeze my OS experienced again on Tue 27th September morning.
Because of all these tests results and additional related contents found inside that Eric Lawrence blog post, I've determined that I'll need to do more tests experimenting Edge startup using so far known Edge command line options I've already documented in my earlier updates plus maybe some other other additional ones found thanks to that post from Eric Lawrence blog.
Best Regards
Rob
Kelly_Y (and others) Hello again,
once more I'm sorry for so much more delay occurred before adding this reply (this time less related to some unexpected OS freezes) and I know so far this topic has become a little too much TL;DR for you all (but as always I try to summarize all as much as I can).
Quick recap: since I determined that quite too much time was effectively needed to do more specific tests experimenting Edge startup while using best possibly applicable command line options among so far known Edge ones found, again thanks to reported post from Eric Lawrence blog, so I decided to postpone those tests also because I had to be involved in other issues too.
ITMT my client already received v108.0.1462.76 (that I was still able to start on 01/08 using same methods I already described before) and then latest v109.0.1518.78 (among 02/10 and 02/11 but only after also receiving v109.0.1518.49 on 01/13), that on 01/08 I also learned to be latest and last ever to be released for Windows 7 SP1 x64 (still my OS that I should hopefully quite soon be able to finally upgrade to Windows 10 0:-| :-((( ) so after another last unexpected OS reboot, yesterday was finally able to try using Edge Enterprise v109.0.1518.78.
At 1st I tried several times (8~9) with older method I already found and described in the past (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, and then "magically" see an Edge InPrivate session start correctly just right before using standard Edge icon in OS Application bar to then see Edge start correctly and also be able to fully recover all already opened standard windows and sessions) but any Edge InPrivate window that opened always stopped responding and so basically I always had to force closing it (only 3 times Edge succeeded in self-detecting own stopped responding status and then asked me to confirm restarting own window and InPrivate session, but always there was no real way to try to proceed further without closing involved window, and then in Edge Crashpad folder I also found 3 very recent .dmp files not already self reported by Edge...).
After all that I simply started again to think to temporarily switch to latest Firefox, but then I also decided to also try to run Edge via same icon I put in OS Application bar right after Edge completed own 1st ever installation (it was v92.0.902.73 then, and app execution was specified using this very basic option "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --profile-directory=Default) and then I was so very happy to see Edge coming again back to "normal" life, self check it wasn't closed correctly and then also be able to let me use [ Restore ] button to reopen all windows and standard sessions I still had opened before an OS unexpected Blue Screen.
I was still a little doubtful about Edge v109.0.1518.78 really getting back to normal usage, until today too (and very early in the morning in local TZ while I was also writing this update...), my laptop decided to self reboot suddendly without any Blue Screen but once again after that my OS indeed recovered fine. After that I only ran Edge via Application bar and once again I'm very happy to say that it started fine and once again allowed me to use same "magic" [ Restore ] button to get all past Edge opened windows and sessions back to normal life.
So I guess and hope all this also seems to at least end this discussion thread...(and all previously unreported .dmp files were attached to a 'Send feedback'...) 0:-) ;-D
Best Regards
Rob
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