Jump to content
Stevie D

[SOLVED] Browsers not opening with MBAE & Kaskpersky 16 (Firefox XPCOM)

Recommended Posts

Hello Channah,

I am understanding that the issue you have is about the Malwarebytes Anti-Exploit and Chrome.

I am moving your thread to the Anti-Exploit support forum.

Share this post


Link to post
Share on other sites

:welcome:

Hi Channah,

Could you tell us the version number of your Malwarebytes Anti-Exploit, and the version number for Google Chrome?

 

 

Share this post


Link to post
Share on other sites

MBAE Premium on Windows 10. Also running Kaspersky 2016 and MBAM.

 

Problem: Chrome will not launch, MBAE says "I am protecting chrome" and that's it, chrome exits silently at that point. It does not show up in the task scheduler. Nothing. No error dialogues. 

 

Things I Tried:

 

  1. Uninstall MBAE/MBAM, reboot, download latest, turn off all applications, turn off protection, reinstall MBAE.
  2. Uninstall Chrome, download latest, MBAE, MBAM, reboot, reinstall all.
  3. Starting chrome in incognito mode.
  4. Starting chrome with extensions disabled.

No Joy. This is what I do notice:

  1. Turn on MBAE protection, everything works but chrome.
  2. Turn off MBAE protection, everything works including chrome.
  3. Turn on MBAE, explicitly deactivate chrome shield, chrome works.

So obviously this is sub-optimal because my main browser is chrome. The event viewer is similarly unhelpful, indicating that chrome failed in an unknown module:

 

Log Name:      Application
Source:        Application Error
Date:          10/6/2015 7:59:03 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Andy-Desktop
Description:
Faulting application name: chrome.exe, version: 45.0.2454.101, time stamp: 0x56034380
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x017f6074
Faulting process id: 0xab0
Faulting application start time: 0x01d100a3bdc6f88d
Faulting application path: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Faulting module path: unknown
Report Id: d31dd8e1-bb0a-435d-a5fe-c6e9b75d2aa2
Faulting package full name: 
Faulting package-relative application ID: 
 

Share this post


Link to post
Share on other sites

Also, mbae-test works as expected.

Renaming mbae-test to chrome and turning the shield back on works as expected.

Share this post


Link to post
Share on other sites

This is a known issue that was introduced in Kaspersky 16.

 

The solution is included in MBAE 1.08:

https://forums.malwarebytes.org/index.php?/topic/172363-mbae-108-beta-preview/

 

Ahh, I see I got merged, two questions then:

 

  1. How stable is 1.08? I don't generally run beta software because there isn't enough hours in a day, plus I figure I'm not losing anything and it will get fixed eventually.
  2. I know the marketing folks at Kaspersky consider me one of their product evangelists, and I was noticing part of the issue was a lack of response from Kaspersky.I might have some influence with them, so I am going to write them to basically say "you are infosec guys, so you know layering is a good thing, malware gets more sophisticated, so I'm advocating for desktop layering as well, why don't you support these people better and help me help you." Anything specific that I might add that would make their marketing folks say "maybe I should talk to the tech manager."

Share this post


Link to post
Share on other sites

MBAE 1.08 is pretty stable as you can see in the Experimenta/Beta sub-forum. As for Kaspersky, there's no urgency anymore for them to fix their hook. We've fixed it in 1.08 from our end.

 

As for HelpDesk Automate, do you get an alert from MBAE? If so send me the logs and create a new thread for this issue.

Share this post


Link to post
Share on other sites

I think the problem is back with KIS 2016.

After their last update 15.10.2015 15:30, I could not open Chrome nor IE with MBAE enabled,

only the balloon about the protection was showing up.

After disabling mbae, chrome worked again.

My version of mbae is : 1.08.1.1023.

 

Please look into it.

 

Thanks.

Share this post


Link to post
Share on other sites

It seems the Kaspersky update re-introduced the problem.

 

We're currently investigating. In the meantime please deactivate the shield for the browsers or switch AV. We'll post back here asap.

Share this post


Link to post
Share on other sites

It seems the Kaspersky update re-introduced the problem.

 

We're currently investigating. In the meantime please deactivate the shield for the browsers or switch AV. We'll post back here asap.

Thank you so much.

I already deactivated.

Share this post


Link to post
Share on other sites

I'm seeing the same here with KTS installed.

However, for me on W10 I have to 'Stop Protection' to get FF latest or IE11 to work.

Deacitvating Browser shield doesn't help.

 

No issue with MS Edge though.

 

Unfortunately for me, switching AV at this point isn't an option.

I will watch intently hoping a fix is applied to MBAE.

Share this post


Link to post
Share on other sites

I removed MBAE due to repeated compatibility issues with Kaspersky products. Switching AV is not an option for me, either. Maybe I will reinstall MBAE if/when it is fully compatible with KIS/KAV/KTS. :unsure:

Share this post


Link to post
Share on other sites

Please stay tuned. We'll be releasing a new build today if possible, or Monday at the latest.

Share this post


Link to post
Share on other sites

Will do, As always thanks Pedro :)

Share this post


Link to post
Share on other sites

Please report back your findings.

The new version solved my problem with KIS2016 and Firefox.  Browser opens normally now.  Thanks to the MBAE folks for a quick fix!

Share this post


Link to post
Share on other sites

Please stay tuned.

OK, Pedro, I do like MBAE, so  I do think I should give MBAE one more try. Thanks for the quick fix, my friend. :) 

Share this post


Link to post
Share on other sites

Thanks Pedro

For me, I think this 'begs the question', Will Kaspersky keep throwing a wrench into things as updates come?

Only time will tell.

I hope the fix is universal; permanently resolves this issue.

Share this post


Link to post
Share on other sites

For me, I think this 'begs the question', Will Kaspersky keep throwing a wrench into things as updates come?

Only time will tell.

I hope the fix is universal; permanently resolves this issue.

Yes this is a more universal fix. The previous one was too version dependent.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • 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.