Forum Discussion
Edge Beta install, runs once correctly, then get a blank screen on startup and crash
Hi there,
please try the suggestions explained in here and see if any of them fix your issue:
https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/
Temporarily disable the new protection
You can temporarily launch the browser without this sandbox feature to verify that it’s the source of the crashes.
- Close all browser instances (verify that there are no hidden msedge.exe processes using Task Manager)
- Use Windows+R to launch the browser with the command line override:
msedge.exe --disable-features=RendererCodeIntegrity
Ensure that the tab processes work properly when code integrity checks are disabled.
If so, you’ve proven that code integrity checks are causing the crashes.
Hunt down the culprit
Visit Edge://conflicts#R to show the list of modules loaded by the client. Look for any files that are not Signed By Microsoft.
If you see any, they are suspects. (There will likely be a few listed as “Shell Extension”s; e.g. 7-Zip.dll, that do not cause this problem)– check for an R in the Process types column to find modules loading in the Renderers.
You should install any available updates for any of your suspects to see if doing so fixes the problem.
Also, are you able to access the Settings page in Edge insider Beta or does it crash/hang when doing so?
- Fabrice BAUEROct 16, 2019Copper Contributor
HotCakeXthanks very much for your reply.
I have the same issue when using msedge.exe --disable-features=RendererCodeIntegrity
Same issue whether I start it as Admin or not.
I cannot go to any Edge:// url as the browser fully crashes at startup 😞
Is there anything else I could look for?
Thank you
- HotCakeXOct 16, 2019MVPYou're welcome,
Sorry I can't think of anything else at the moment, could you use Edge insider Dev or Canary instead?- Fabrice BAUEROct 16, 2019Copper Contributor
HotCakeXsame with Canary and Dev versions 😞
First launch after install is ok, but then any other launch after that shows a full white screen for a few seconds and then fully closes.
Just saw it was the case as well when using Chrome, but after a few tries Chrome launches again. So might be chromium related and/or a setup on my machine.