[SOLVED] Conflict with Trusteer Rapport - BottomUp ASLR & Office

[Kevin75116]

I bought MBAE Premium today and it now blocks the opening of all excel and word documents unless I deactivate those shields in the program.

 

I have the latest version of MBAE. My MS Office and Windows 10 are fully up to date. I ran the MBAE-test download and it worked as it was supposed to. 

 

I have attached a zip of all the files in programdata.

 

Can you help me?

 

Thanks a lot

 

Cheers

 

Kevin

zipofprogramdata.zip

[pbust]

Welcome to the forum and thanks for posting Kevin!

 

Can you please post an FRST log to see if there is something else on your system that might be conflicting with MBAE? Instructions can be found in the "readme first" link in my signature.

 

As a workaround in the meantime do the following:

MBAE UI -> Settings -> Advanced settings -> Application Hardening -> Uncheck BottomUp ASLR Enforcement for the Office column -> Apply

Restart Word & Excel.

[Kevin75116]

Thanks the work around works. Here are the FRST logs.

 

Cheers

 

Kevin

FRST.txt

Addition.txt

[pbust]

Thanks for the logs. It's probably conflicting with Trusteer Rapport which has a known conflict.

 

You can either disable/uninstall Trusteer to see if the problem persists or simply keep the BottomUp ASLR Enforcement turned off permanently in MBAE.

[Kevin75116]

OK thanks. I guess I'll leave the workaround in place as my bank insists on Trusteer.

 

Cheers

 

Kevin

[Hyncharas]

I'm having the same issue with MBAE Premium Trial.  As far as I know we don't have Trusteer installed, but also get blocking errors in OS Protection.  I've deactivated those and reset because applying won't take effect, and it's still blocking them; the only way to use MS Office is to disable MBAE or uninstall completely...

 

I don't understand - this works FINE with the free version.  Why is Premium kicking up such a fuss?!

[pbust]

Please attach your logs Hyncharas. Instructions in the "readme first" link of my signature.

[Hyncharas]

Sorry for the delay; another system we use has got Windows 10's WiFi bug and we've had huge trouble solving it.

I will forward the MBAE logs for the affected system later today.