Forum Discussion
Internet Explorer Mode broken in Edge Dev Version 80.0.361.9
GreatToHearFromYou dmcaylor There is a known issue being worked on right now which casues IE not to validate a Microsoft signature on a dll shipped with Edge. If you are affected by this bug, you will be find a Microsoft certificate in the "Trusted Publishers" folder in certmgr.msc that matches the one Edge is being signed with. The workaround would be to remove this cert from Trusted Publishers until we get a fix out.
Hi there,
The Internet Explorer Integration policies are set at machine level.
The part I blurred out was the URL of a web page I happened to be on. Not sure why it included it there; maybe something to do with SSO on that page. If I go there now without that page loaded, it does not include it in the command line section.
Andrew
Before I received your reply I tested setting it all at User Level and that didn't make any difference. I tried the Beta versions (Public and Enterprise) as well thinking they do not have the change yet that broke IE Mode, however, they are broken as well, which makes me think that a Windows update of some sort may be the culprit. If I could only move back to Edge Dev Version 80.0.361.5, I could test that theory.
We had that issue on one of our users machines yesterday with a new install of edge beta. This morning it worked after an update and restart. I did notice that your settings are different in that we have sitelists identified in both IE and Edge...
Hi! Thanks for you input! I had high hopes, because when checking "Help and Feedback > About Microsoft Edge", it started installing a new update for Dev to version 81.0.381.0, unfortunately it is still a no-go. I have also tried the Beta (version 79.0.309.60) and that is a no-go as well. Initially I had the website list set for both the IE Policy and the Edge Policy when I first reported the issue. However when @AndrewSAIF reported the IE Mode in his Edge install was working just fine without the Edge Policy, I matched his settings, unfortunately to no avail. I will try setting the Edge Policy back again and see if that makes a difference.