Share via

Microsoft Edge (Build 123.0.2420.53) closes unexpectly after update on 1st run

Anonymous
2024-03-23T12:31:15+00:00

I do not know why Microsoft always like to give a bunch of headache for their customers.

After upgrading to Microsoft Edge Build 123.0.2420.53 today (23rd March 2024), the application cannot run anymore. When I call the program from any point, either shortcut or directly from C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe, it will show white blank screen for a brief period then just close. No error was produced. I tried to repair the application from settings, but sadly the symptoms persist. So last resort was to downgrade Microsoft Edge to last working version, Build 122.0.2365.106

When I check on winget using these command (from command prompt or Windows Power Shell or terminal):

winget download --id "Micosoft.Edge"

Surprisingly it download the build 122.0.2365.106 instead of built 123.0.2420.53.

Alternatively, I open the https://www.catalog.update.microsoft.com/Search.aspx?q=edge%20122 just to make sure that is the latest stable version before last build. No other stable Built 123.x.

The setup is very troublesome as I had to use command prompt to perform downgrade install.

msiexec /I Microsoft Edge_122.0.2365.106_Machine_X64_msi_en-US.msi ALLOWDOWNGRADE=1

The Edge is finally back to normal.

My question is:

Can Microsoft stop forcing crappy update? You said updates were to give customer safety experience but what I see is crappy experience. I used Google Chrome and Opera... I never ever had a crappy updates like this!

And another thing PLEASE PLEASE PLEASE PLEASE PLEASE enable downgrade without having to put them in commmand. STOP giving lying to us by giving us FAKE slogan about updates is to make better. Microsoft very so often make worse from updates!

BTW why I am writing this by the way. Microsoft won't listen...

Microsoft Edge | Browser crashes or stops working | Windows 11

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

32 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-24T09:37:07+00:00

    Why should I write on feedback?

    Will Microsoft listen? I do not think so... You know writing on feedback is a time-consuming process. I wrote them, re-read them, produce screenshots. Then no action area taken on my feed backs. So, finally what are the use of feedback if those stuff enter recycle bin in the developer side?

    I wrote here is NOT for Microsoft but for other users who are dependent on Edge. Microsoft always think they're doing everything right. "Thank you" from Microsoft is nothing more than a Lip Service.

    You know what? I only use Edge to browse Microsoft site. For 95% of site outside Microsoft, I use Google Chrome. and 4.99% I use Opera for site that requires VPN. Because till this date I still mark Microsoft product is the worst ever. Luckily browser is not only Edge, so no point of feedback for corporate that think they are doing right.

    If Microsoft need a feedback read complains from here is more than adequate.

    10 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-03-24T15:25:57+00:00

    same issue but on a enterprise level, Monday is going to be fun, 30 users so far and counting

    5 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-03-25T09:26:28+00:00

    30 Users, 300 User, 100 Users? Huh?!

    That is your problem! Not Microsoft problem.

    You write on feedback? What is the use? They do not read them. Feedback hub, that is just decoration to make Windows 11 have color stuff.

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-03-25T10:37:49+00:00

    We have found a way around the issue that seems to be work for us but is less than ideal.

    If you rename this folder within the users profile:

    C:\Users(The Users Name)\AppData\Local\Microsoft\Edge\User Data to .old ......... Edge will then load. I'm not saying this is a fix as doing the roll back to 122 as per the original post also resolves the issue

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-03-25T09:08:00+00:00

    Same here, around 100 users already reported issues, the joys of Microsoft !!!!

    2 people found this answer helpful.
    0 comments No comments