Microsoft's Enhanced Mitigation Experience Toolkit breaks recent versions of Chrome. I had a nagging issue with Chrome in that it wouldn't load the newly sandboxed flash player. This would cause minor irritations like not being able to view youtube videos in Chrome as well as major problems like Google Calendar completely crashing.
After spending a day and a half troubleshooting drivers, services, and startup programs between safe mode and normal mode (Chrome worked fine in safe mode with networking), I uninstalled EMET on a whim and low and behold, Chrome works.
EMET is designed to automatically employ ASLR and structured exception handling protections on executables that weren't necessarily compiled with these features in mind. It also breaks stuff. Lots of stuff by the looks of it. Including Chrome.
I'm not sure which mitigation was breaking Chrome, but uninstalling EMET took care of it :) I wish I knew more about the flash sandboxing implementation in Chrome in order to identify exactly what went wrong. Reversing Chrome's sandboxing sounds like a project for another day. I'm sure PinkiePie knows exactly what happened.
EDIT: Looks like SEHOP is the offending mitigation. Disabling this for chrome.exe may be less hammer like than uninstalling EMET.
Can you explain how to disable SEHOP from chrome.exe. I've been having this issue as well and am so excited I found this post........but don't know how to exectue.
ReplyDeleteI've actually uninstalled it from all computers I have available, so I can't give you step by step directions. However this blog has a great tutorial and screenshots on how to configure EMET:
ReplyDeletehttp://www.rationallyparanoid.com/articles/microsoft-emet-3.html
Take a look at the screenshot with all the executables listed on the left; basically you want to uncheck the box under SEHOP for chrome.exe. Good luck!