Internet Explorer Mode broken in Edge Dev Version 80.0.361.9

GreatToHearFromYou The fix for this issue will ship as part of the Windows update the week of 2/17.

Shilpa_SubramanianThanks for the info! This makes me somewhat optimistic. I did find a certificate that matches the one msedge.exe is signed with, I removed it, rebooted the computer and tried IE Mode again, unfortunately it is still popping out into a new Window. However, you mention a dll shipped with Edge and I noticed I decided to remove all the certificates, because the Edge dll's are signed with multiple certificates and after a reboot IE Mode indeed worked again as expected. This is fantastic news!

We will have to wait for the fix though, because those certificates are there because of our Software Restriction Policies and I don't want to break that. I guess anyone that has Software Restriction Policies in place could be affected by this bug, depending on how they have it set up.

Thanks for all your help.

Shilpa_Subramanian 

Great to know. Can you specify which DLL, since there are multiple MS code signing certs in use by Edge?

We have noticed the same error as described above.

In another test environment with the same policies, Internet Explorer Mode works fine.

I couldn't find out which certificates might be the cause.

MartinSchneeberger It appears to be user certs. I opened certmgr under the affected profile, clicked Trusted Publishers/Certificates, then deleted expired MS certs as well as MS certs with an intended purpose of 1.3.6.1.4.*.

dmcaylor Thanks! I removed the following certificate. The "Internet Explorer Mode" now functions perfectly.

Issuer: Microsoft Code Signing PCA 2010
Serial Number: 3‎33 00 00 02 ce 7c 9a ce 7d 90 5e d2 b7 00 00 00 00 02 ce
Thumbprint: ‎b1 06 07 fb 91 47 00 b4 0f 79 46 10 85 0c 1d e0 a2 15 66 c1

MartinSchneeberger dmcaylor 

Thank you for finding the offending certificate, and I can confirm that IE Mode is working again after removing this certificate. However, in our environment we've added this certificate to the trusted certificates through GPO, so that Microsoft Teams (which shares this certificate) can run. Our Software Restriction Policies do not allow programs to run from the user profile folder (or anywhere else but the 2 Program Files folders), unless we trust the certificate. Unfortunately Microsoft installs and runs Teams from the user profile folder, thus we need this certificate to stay in place.

So, even though this is a great find, this is unfortunately not a solution. However, now that I know the culprit I will see if we can move Teams to one of the Program Files folders instead, like we have done with OneDrive. But ultimately Microsoft needs to fix the issue.

Shilpa_SubramanianAny word on a permanent fix for this yet?

Edit: I just did a quick search and even using the Teams msi, it will still install in the User Profile folder. I don't get why Microsoft is pushing for this. Skype/Lync is installed in the Programs Files folder and get updated perfectly fine. Anyway, all the more reason that Microsoft has to permanently fix this issue.

LeeW78 

Please try latest stable Version 83.0.478.54. Perhaps this will help.