08-22-2019 01:55 AM
08-22-2019 01:55 AM
I started using Microsoft Edge Dev some months ago and everything went smoothly until today: I turned on my laptop, opened Edge Dev and noticed that it is not working anymore at all.
Any page that I try to open (even the welcome tab) doesn't load and moreover the only two extensions that I installed (uBlock Origin and Norton Password Manager) are crashing.
I would like to check the log file (if any) in order to understand a little bit better what's going wrong under the hood.
I'm using Windows 10 Pro 1903, unfortunately I can't provide the Edge Dev version since the "about" tab is not working. Trying to download and run the latest installer from the web did not help.
08-22-2019 02:15 AM - edited 08-22-2019 02:17 AM
Same here, running fine for weeks then suddenly the same problem - no pages (not even "Edge" pages, such as settings) will load, and all extensions crash. This happens with both Edge Dev and Edge Canary, and I've tried reinstalling both but the problem persists. I'm running Windows 10 Pro 1809 x64.
Starting Edge with the '-no-sandbox' switch seems to workaround the issue, but doesn't seem like a proper resolution?
08-22-2019 03:01 AM
08-22-2019 03:13 AM
@paolot I'm having the same issue on 64-bit Windows 10 (1809), it might be related to an open Chromium issue
08-22-2019 06:13 AM
I was having the issue a few days back with Edge Canary, but it's fine now after one of their daily updates. I've had it happen in Chrome Canary too and the same thing...usually by the next day update (or second next day update) it's fixed. Sometimes for whatever reason it carries into Dev. As others said there can be a specific reason or Windows reason for it happening (I don't know as Canary is working fine for me now, an I'm not on the Dev side of things).
You can also see if the same bug happens in Chromium:
(Keep in mind that Chromium is not meant to be used as an everyday or regular browser as it doesn't have auto updater or any updater except manually installing it everyday, and it lacks important codec that isn't built into it to run certain applications. So stick with Edge Canary/Dev/Beta for that, but it's good for testing to see if a bug is in the original source or for analyzing to see if an crashing issues found in the later versions like Canary and Dev are happening in the original trunk version). https://www.chromium.org/getting-involved/download-chromium
08-22-2019 12:34 PM - edited 08-22-2019 12:47 PM
Thanks, everyone for reporting this issue.
I have reported this problem to the engineering team.
I'm curious if it's only affecting specific extensions, could you all please list an extension or two you where using?
Thanks for your patience,
08-22-2019 12:45 PM
08-23-2019 01:00 AM
In my case the Chromium team think it's a known incompatibility between Symantec Endpoint Protection 14.0.3929.1200 and renderer code integrity. I am using that version of Symantec Endpoint Protection.
I don't currently have any extensions installed
08-23-2019 01:10 AM
@RetroChrisBI can see a correlation here too.
"--disable-features=RendererCodeIntegrity" solves the problem.
We're using Symantec EndPoint Protection on our PCs too, version 14 (14.0 RU1 MP2) build 3929 (14.0.3929.1200) on Windows 10 Enterprise 1709 (16299.1268) 64 bits.
08-23-2019 04:50 AM - edited 08-23-2019 04:54 AM
I came in this morning to the same issue. We are running SEP 14.2.1031.0100.
Creating a shortcut with --disable-features=RendererCodeIntegrity is a working workaround for me as well.
08-23-2019 04:46 PM - edited 08-23-2019 04:54 PM
I am having a similar but intermittent problem as well, both on MacOS and PC.
In my case, tabs will randomly redirect to the "this page is having a problem" error page, either immediately when opened, or a while after they are launched. No real pattern, and some tabs never have the issue.
I do not use Symantec Endpoint Protection in any capacity.
Using this list of extensions:
08-23-2019 05:02 PM
@V-FRROME I did a report through the browser, was erroring on Cisco WebEx (v1.5 & latest) plugin from the Google store, the only one installed. However even with it disabled I still had the issue. Had the same issue on the Canary build, but Beta being a bit older remained fine.
Alternate to the flags, on Win10 if you put the browser in Win8 compatibility mode it works fine.
08-26-2019 09:25 AM
I have this problem and i don't use SEP. I'm using 1903, edge dev and no extensions. I use any windows 10 built security. all pages show "this page is having a problem" even the settings etc... had to make a shortcut with --disable-features=RendererCodeIntegrity option to make it work. sigh. just when I thought I could leave firefox…
09-04-2019 01:25 AM
It seems like few days ago Symantec published a technical article about the issue, it should be fixed with the release of Symantec Endpoint Protection 14.2.
Since many of us will not be able to perform the update (since it is managed from our company) Symantec provides a workaround too, consisting of adding an "Application" exception to SEP.
Unfortunately I wasn't able to test the workaround since the option to add application exceptions on my instance is disabled by my company.
09-27-2019 10:54 AM
Having the same problem today with Beta 78.0.276.8. The only thing that changed to my knowledge is that I added the Webex meeting extension yesterday from the Chrome Store. I've tried uninstalling and reinstalling the Beta version, long with Dev 79.0.279.0 and Canary 79.0.286.0 all with the same results.
All pages in Edge display the same thing. Settings, Extensions, About. Event log
Faulting application name: msedge.exe, version: 78.0.276.8, time stamp: 0x5d8af48d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000009f1fc
Faulting process id: 0x855c
Faulting application start time: 0x01d57559e8b0e864
Faulting application path: C:\Program Files (x86)\Microsoft\Edge Beta\Application\msedge.exe
Faulting module path: unknown
Report Id: 8821d087-10c9-42cf-8372-28b566939c30
Faulting package full name:
Faulting package-relative application ID:
09-30-2019 12:48 AM
10-02-2019 07:14 AM
I'm still having this issue, on both Dev and Beta channels, and it's happening on multiple computers (one personal, one corp). Both a Dell computers if that's worth anything (an XPS 13 2-in-1 7390 and a Latitude 7480), with Symantec Endpoint Protection on the work Latitude. As for extensions, I only have 2 - 1Password X and Momentum Dashboard.
The --disable-features=RendererCodeIntegrity flag does seem to fix it for me on both computers that is failing. Prior to this, I noticed that reinstalling would fix the problem for a while, but then it would just show up out of the blue for no reason when starting the app sometime... Pages wouldn't load, and even the About and Preferences wouldn't load.
10-07-2019 04:51 PM
I have found that if I use the --disable-features=RendererCodeIntegrity", Edge works to at lease allow me to get into extensions. Once in Extensions, if I enable "Allow extensions from other stores" then remove the RendererCodeIntegrity switch, then the Edge issue seems to be resolved. I am using SEP 14.2.4814.1101 (aka 14.2 RU1 MP1).
10-09-2019 06:29 AM
10-11-2019 02:19 AM
I'm getting this same error page on most sites.
I'm using Edge Dev 79.0.294.1 on Win10 1903 and don't have any Symantec Software (I'm using Windows Defender)
This switch doesn't help
"C:\Users\<username>\AppData\Local\Microsoft\Edge Dev\Application\msedge.exe" --profile-directory=Default --disable-features=RendererCodeIntegrity
This means I've had to go back to the original Edge for my browsing (ironically the Chromium issue page won't load in that!).
12-05-2019 02:50 AM
Just updated Edge Dev to Version 80.0.345.0 and I'm experiencing this issue again, so I've had to put the switch back in to disable Renderer Code Integrity:
Looking through the release notes for this version I can't see any explicit mention of this feature being enabled again, but it was stated previously that it was only disable temporarily, so it seems like it's now back? (Or it may have happened in a previous release that I missed?)
Is there any more insight into fixing this issue?
12-11-2019 07:25 AM