Aug 22 2019 01:55 AM
Hello everybody!
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.
Oct 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.
Oct 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).
Oct 09 2019 06:29 AM
Oct 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!).
Oct 11 2019 02:56 AM
Dec 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:
--disable-features=RendererCodeIntegrity
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?
Dec 05 2019 02:53 AM
Dec 09 2019 04:51 AM
I'm back to the same issue as well. Same work around in place.
Dec 11 2019 07:25 AM
Dec 11 2019 09:39 PM
@thommck-on-twitter Unfortunately the Dev version from early last week or the week before has reintroduced the issue, so depending on whether or not they fix it before the next Beta release you may need to keep the flag handy.
Dec 17 2019 11:52 AM
Jan 07 2020 08:11 AM
Feb 09 2020 07:23 PM
after upgrade edge chromium 79.0.309.71 to 80.0.361.48
(windows 10-1909 with 79.0.309.71 no problem)
..This page is having problem same as Chrome 79.xxx (show error Aw Snap......)
i'm solve by...
1. add --disable-features=RendererCodeIntegrity to shortcut
2. or set compatible to Windows 8 with change setting for all users
Feb 09 2020 11:35 PM - edited Feb 09 2020 11:36 PM
@9POLsame here and its no option to disable it for devices via gpo because as Microsoft says in its own gpo comment "Disabling this policy has a detrimental effect on Microsoft Edge's security and stability because unknown and potentially hostile code will be allowed to load inside Microsoft Edge's renderer processes."
now we can choose between insecurity through disabling render integrity or through not updating edge to this latest version but its an security update. Thanks ;)
Feb 13 2020 09:24 AM
This problem is back for me (again, ugh) in 81.0.416.3
Feb 18 2020 10:37 PM