Users complaining that the browser crashes all of a sudden

Apr 13, 2017 11:22 GMT  ·  By

Microsoft Edge is one of the apps getting significant improvements in the Windows 10 Creators Update, but for some reason, not everyone can enjoy all the new good stuff.

It turns out that the browser crashes on a number of Windows 10 systems upgraded to the Creators Update, and at first glance, creating a new user account seems to be the only way to avoid the bug.

The problem is described in detail in this post on the Microsoft Community forums, with user rhelmer explaining that although the browser launches, it crashes shortly after launch.

“Just installed the Creators Update, and Edge crashes within 2 minutes of launching. Every. Single. Time. To be sure, it does launch. It even browses the web without issue. Then it just disappears. It will launch again just fine. But it will disappear again, every launch,” the post reads.

New user accounts working just fine

One of the systems here at Softpedia is experiencing the same error, though it runs the same configuration as others that are working just fine. No workaround seems to make a difference, though creating a new user account and starting fresh does seem to run Edge flawlessly.

“It does work if I create a new user profile. But that doesn't help me fix it for my user profile. Recreating my user profile is not worth the effort just to use Edge... it should be fixable without having to start over with a new user profile, and it's disconcerting that the removal of the user profile elements specific to Edge still doesn't resolve the issue,” the same user post continues.

Similar issues with apps that crashed were also experienced on Windows 10 in the past and, in some cases, the bug impacted the Start menu and the Action Center as well, both of them failing to launch when clicked. Switching to a new user account helped deal with these problems as well, though it’s very clear that migrating to another account isn’t quite the most convenient solution.

Microsoft is yet to acknowledge the bug and it’s impossible to estimate how widespread it is, so we’ve contacted the company for more information and we’ll update the article should an answer be offered.