Forum Discussion
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 ...
There is a workaround - launch with the following command line switch:
--disable-features=RendererCodeIntegrity
--disable-features=RendererCodeIntegrity
Thanks and everything back to normal.
Just did a check and looks like earlier this month chrome canary build also appeared the same issue (and workaround).
Edge supposed to use a stable chromium build which doesn’t have this issue but don’t know why still occurs.
Just did a check and looks like earlier this month chrome canary build also appeared the same issue (and workaround).
Edge supposed to use a stable chromium build which doesn’t have this issue but don’t know why still occurs.