Microsoft Edge closes immediately upon opening. I've tried many fixes none work.

Anonymous
2023-08-15T11:52:24+00:00

Yesterday, I wanted to clean up my favorites in Edge (remove duplicates, remove obsolete links). In the midst of this, Edge closed without warning or error message. When I restarted Edge, it closed immediately. I could not select the three dots in the top right. It closed too quickly.

I found several possible solutions including tools in the Settings/Apps menu, other fixes involving removing and then reinstituting the %LocalAppData%\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe directory

None of these fixes worked.

When I restart Edge, it closes immediately.

How can I get it to work properly?

Microsoft Edge | Browser crashes or stops working | Windows 10

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

161 answers

Sort by: Most helpful
  1. Anonymous
    2023-11-16T21:30:30+00:00

    Yes! Microsoft then Edge folder

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-11-16T20:51:45+00:00

    Your video is great and I can understand you completely - but I don't see the "EDGE" folder on I go to the Microsoft folder ????

    thank you!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-11-16T18:38:01+00:00

    This actually worked. Make sure you're able to find the above mentioned folders by changing the setting on the file explorer to show hidden folders. By the way, I've started experiencing same issues with Chrome.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-11-15T17:19:00+00:00

    This procedure worked great. I am running inside of VMware.

    Thank you !!!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-11-15T13:07:26+00:00

    I did try all of Microsoft recommendations and the above tips that did not work. This one did the job, thanks

    incredible that microsoft itself is unable to solve a problem they created themselves in an update / kb

    Was this answer helpful?

    0 comments No comments