Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by FCA711

  1. Seems to work for me. No crashes. I'll try it out for a couple days to test. Thanks!!
  2. Me too. I updated Chrome manually and verified the latest Trusteer was on there. Still crashed, but after removing just the Advanced Memory Protection setting for Chrome, now all is good again. The CALL ROP is activated. So, we're making progress I think.
  3. That's my question as well. I wish they would just come out with a fix and not require this workaround. Turning off features is like punching holes in the security, so it's probably not ideal in the log run.
  4. For me, I had to do BOTH of these workarounds: MBAE -> Settings -> Advanced Settings -> OS Bypass Protection -> CALL ROP gadget protection (32/64) -> uncheck for Chrome -> Apply MBAE -> Settings -> Advanced Settings -> Advanced Memory Protection -> Malicious return address detection -> uncheck for Chrome -> Apply I have both Chrome and Trusteer Rappport. If I do the workarounds, Chrome works OK. If I shutdown Trusteer first, Chrome opens OK. Don't know what's causing the conflict, but it's definitely MBAE/Trusteer combo that interferes with Chrome opening.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.