Forum Discussion
josh_bodner
Aug 21, 2019Former Employee
Dev channel update to 78.0.249.1 is live
Hello insiders, we have a lot to share today! In addition to releasing build 78.0.249.1 to the Microsoft Edge Dev Channel, we’re also very excited to announce that as of yesterday, we’re making the ...
Eric_Lawrence
Microsoft
Aug 22, 2019Are you running a 32bit version of Edge? Try Win+R:
msedge.exe --disable-features=RendererCodeIntegrity
If that fixes you, then the bugfix is known and just waiting for the next push.
msedge.exe --disable-features=RendererCodeIntegrity
If that fixes you, then the bugfix is known and just waiting for the next push.
zhangchi1979
Aug 23, 2019Copper Contributor
Eric_Lawrence thanks and it works. Just FYI, I am using Windows 10 64 bit and Edge Dev also 64 bit version.
- Eric_LawrenceAug 23, 2019
Microsoft
Thanks. If you're using 64bit, that means that there's some software on your computer which is injecting itself into the browser. An old version of Symantec's security product was doing that; would you happen to be using it?
If not, if you could visit edge://conflicts and copy the data to a text file to share, we can investigate further.
thanks again!