Forum Discussion
Internet Explorer Mode broken in Edge Dev Version 80.0.361.9
- Jan 24, 2020
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.
Hey, I tried the most updated version of dev channel and it works fine to me.
Could you do another update and give a try again?
Thanks,
Ning
- GreatToHearFromYouJan 09, 2020Brass Contributor
Hi! Thanks for joining in. Yes, I downloaded the latest version today, see my last message, but that still popped out Internet Explorer in a separate Window. I've worked on a complete clean computer this evening, not on the domain, and installed the latest Dev version on it. Then matched all the local IE and Edge policy settings to those of our Domain policy and it works just fine, IE Mode works natively within Edge on that computer, so I am really baffled what is breaking it on our Domain computers. It's frustrating, because everything was working as it should, and we were ready to go live shortly after January 15 when Microsoft is planning to update the old Edge with Edge Chromium. However, then 80.0.361.9 came along and that broke IE mode for us.
I'm sorry to hear that you seem to have the same problem. Did you happen to find a solution?
- nizhonJan 09, 2020
Microsoft
Well, IE Mode can work based on lots of factors and it's hard to diagnostic immediately. That's why the diagnostic page(edge://compat/iediagnostic) is important right now. We will have more features on that page which can help diagnostic the failure reasons further.
Just to clarify, you are using the same setting for two machines, and the domain joined one fails to launch IE mode, but the other one works just fine?- GreatToHearFromYouJan 10, 2020Brass Contributor
Thanks for your reply! Yes, IE Mode on the computers joined to our Domain stopped working when Edge Dev Version 80.0.361.9 was installed and it has been broken ever since. I've indeed set up a quick test computer not joined to our domain and I only matched the Edge and Internet Explorer Policy settings including the XML site list, just to rule out if anything was incorrect with these settings and IE Mode on that laptop worked just fine. In the meantime I have also ruled out our anti-virus. The next step is to set up a laptop from scratch, join it to our domain without any policies applied, and then apply our policies one-by-one to hopefully figure out at what point IE Mode breaks.
- Daniel_CapadonaJan 09, 2020Copper Contributor
GreatToHearFromYou
Hi, I have not found a solution yet. I have tried several versions of Windows 10 with different versions of Edge Beta. I'll make sure I have the newest version out there and try again. One thing I found is that if I remove IE 11, then nothing opens. If I have IE 11 installed, it opens in a completely new window, but the error still pops up. Very strange. I almost wonder if there is another GPO that is messing with it.....- GreatToHearFromYouJan 09, 2020Brass Contributor
Thanks for your reply! Yes, IE11 is definitely needed in able to have IE Mode run properly in Edge. Edge doesn't have the IE engine built-in, it uses it from the installed IE11. So yes, you do have exact the same problem, IE pops out in a new Window and Edge shows the "administrator privileges" message, neither one should happen. Did you ever got it working properly before, or did you always have this problem? When testing it on a Windows 7 computer (even though we're phasing them out right now) I see an IE Error that requires to close the program, see print screen below. This happens before receiving the "administrator privileges" message. Only when I click "Close the program" the "administrator privileges" message appears in Edge and IE opens in a new windows instead of within Edge. That made me wonder if the same error happens in Windows 10, but get suppressed and sure enough, when checking the Event Viewer, I saw the error in the print screen below. Now I will have to concentrate on that error to see what that is all about.