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.
We have had the same problem, but once it broke after a version upgrade, it broke across all versions (dev/beta/canary/stable).
Hi,
Yes, same for us, it broke all versions. Now we have 3 users (you, Daniel_Capadona and I) on this forum with the same problem, I am sure more will come and hopefully we can find a common denominator between us. Unfortunately I haven't had the time yet to start from scratch and add our policies one-by-one to see if it is one of our other policies causing it.
GreatToHearFromYou I have noticed that it appears to be profile specific. I don't think it is policy related. A new user signing on to the affected PC has no issues even with the same policies applied.
I've fully uninstalled all versions, deleted the Edge folders under appdata/local/Microsoft/, and entries in the registry, but after a reinstall the issue is still there for the user profile with the issue.
For us, the same issue appears also with a new user profile. While I was working with the new profile, I also tested if it had anything to do with the xml file that determines the app defaults, I've set the default apps to Windows recommended (automatically making Edge the default browser), rebooted without our "default xml file", but the problem is still there.
Since all was working fine until we got Version 80.0.361.9, which broke all other versions as well, I am also not sure if it is a Policy Setting. However, it is certainly a combination of the update and whatever settings we have on our computers that suddenly broke it, because most people who posted on this thread are fine, or were effected but then fine after an new version update.
