Forum Discussion
We're Listening!
Elliot KirkI cannot get either Edge Dev or Edge Beta to connect to the internet. Obviously other browsers connect fine or I wouldn't be able to post this. I can't get to settings either. I've uninstalled/reinstalled, rebooted, and added exceptions to the firewall all to no avail. What's going on with this thing!?
Wingnut80
In addition to whatever Elliot will have to say... would you, please, give https://www.microsoftedgeinsider.com/en-us/download a go with the others removed (first) & report back? Thanks.
Cheers,
DrewDrew1903, #SameProblem. Installing Canary actually loaded the start page...until I restarted the browser. Then it went right back to what Beta and Dev channels were doing.
- Hi,
the problem is very unlikely to be related to any malware or virus on your computer.
however you can always run a full scan with Windows Defender that is already built in your Windows. no need for 3rd party premium tools.
have you tried this?
https://techcommunity.microsoft.com/t5/Articles/We-re-Listening/m-p/888976/highlight/true#M1733
it looks like there is simply a conflict with the Edge and once you identify it you can take care of it quickly.
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.
