Forum Discussion
We're Listening!
Hi,
try this:
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.
Yes this allowed a connection, but what does that mean? Is there something I need to have continuously disabled? This just started in the last release or 2, what changed?
Wingnut80 wrote:Yes this allowed a connection, but what does that mean? Is there something I need to have continuously disabled? This just started in the last release or 2, what changed?
It means there are some incompatibilities in the browser
Visit edge://conflicts/ to collect the full list of modules loaded into the browser process. 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.