Jump to content

Advn303

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Advn303

  1. +1 on this request for "power aware" features. MalwareBytes really needs to add settings for scheduled scans that allow delay or disable when "on battery" and/or when "power save" mode is active (Windows 10). This has been suggested multiple times and basically is a show stopper for any scheduled use of MB on a laptop. I won't be renewing my premium subscription unless this feature is added. I already disabled my real time protection, because I found it too heavy for laptop use and there are just-as-good lightweight and free real time protection options (including Microsoft).
  2. Thanks to all for the support and information and @dcollins for the information MB team's findings of the bad combinations. I did have Norton Security Suite running with exploit protection on, which I was not even aware was part of that program suite. I have now disabled Norton Security exploit protection (per above under Settings > Firewall > Intrusion and Browser Protection > Exploit Prevention > OFF), and upgraded my Google Chrome to 64-bit (was 32-bit). Chrome problem no longer occurring with MB3 Exploit Protection back on and enabled for chrome.exe (advanced exploit settings back to defaults). All seems to be working now (currently at MB 3.0.6.1469, Comp pkg 1.0.103, Update pkg 1.0.1784). I think running exploit protection in both Norton Security and MB3 simultaneously is probably bad idea, so will keep that feature disabled in Norton Security. Side note: My preferred config is to let Norton Security run real-time anti-virus/anti-malware file access scans, manage temp file cleanups, and provide log of my installs/downloads, and handle smart firewall. I'm using MB3 for scheduled daily file system scans, real-time ransomware protection, and anti-exploit protection. If MB3 added detailed logging of downloads/installs and something similar to the reputation-based "File Insight" lookup, plus firewall management (especially outgoing based on reputation), then I could just use MB3 alone. I like the new MB3 innovations for anti-ransomware (behavior-based file access monitoring) and fine grained anti-exploit protection (looks to be similar to full Microsoft EMET).
  3. I disabled Norton Security's exploit protection ( Norton > Settings > Firewall > Intrusion and Browser Protection > Exploit Prevention = OFF) and upgraded to Google Chrome 64-bit (was 32-bit) version, now issue resolved (not sure if both changes required, but I didn't intend to have exploit protection running under both Norton Security and MB3 anyway).
  4. @nickdanp , This is a recent known issue, so don't bother trying to repair. Only successful workaround so far is to disable MalwareBytes "Exploit Protection" for chrome.exe application (under MB Premium > Settings > Protection > Manage Protected applications), or can disable "Exploit Protection" completely in settings or from tray icon. I recommend using MB settings workaround instead of running Chrome with sandboxing disabled, until fix is available. See related recent threads below which include acknowledgement that this issue is being actively investigated by MB staff, expect this will be high priority for fix. Maybe your logs will be helpful as another study case @dcollins. 1 2 3
  5. FYI, cross reference to similar report of same issue from few days ago that I missed on first pass. And adding some detailed info from logs below. Looks like Comp Pkg update to 1.0.96 was not the trigger for my system, as issue didn't start until after a system reboot on 2017-04-07 in the afternoon, but "SDK/Controller package --> [mbam-c.ctlr.64bit], current version: [1.0.96]" was on my system for at least a few days prior, per "C:\ProgramData\Malwarebytes\MBAMService\logs\MBAMSERVICE.LOG" Best I can tell the MB update that happened closest most likely just prior to start of issue was the install of these just after power up around 17:15 was 04/07/17 " 17:24:47.681" 441390 0bd8 104c INFO UpdateControllerImpl mb::updatecontrollerimpl::CUpdateControllerImpl::UpdateInstalledPkgVersion "UpdateControllerImplHelper.cpp" 2203 "Successfully updated DB/ClsEng package version to: 1.0.1680" 04/07/17 " 17:24:58.025" 451734 0bd8 104c INFO UpdateControllerImpl mb::updatecontrollerimpl::CUpdateControllerImpl::UpdateInstalledPkgVersion "UpdateControllerImplHelper.cpp" 2203 "Successfully updated DB/ClsEng package version to: 1.0.1681" shortly after that Google Chrome started failing to launch...and then I rebooted my system around 17:30 to attempt to resolve. Sorry can't do the more intrusive log collection or post full MBAMSERVICE.LOG until I have time to scrub out PII, as this log contains references to user space files and paths.
  6. Adding Cross reference to similar report of same issue (Chrome extensions crash upon launch, Chrome not functional) in different thread (sorry missed this existing report on my first pass). Reports in that thread are also tracking MB component package 1.0.96 as start of the issue. Only successful workaround so far is to disable MB "Exploit Protection" for chrome.exe application (under MB Premium > Settings > Protection > Manage Protected applications). Don't bother uninstalling Chrome or MB, as this appears to be MB compatibility bug, rather than corrupted install of either program. Recommend just use the workaround to disable "Exploit protection" for affected programs until new fix from MalwareBytes.
  7. I was also unable a solution by to fine tuning settings under Anti-Exploit Protection > Advanced settings. Even turning all options off didn't work, had to disable for chrome.exe or disable entirely, same as GaryFDes. Good observation GaryFDes that problem may be dependent on Component package version, which is very believable since I think that version 57 of Chrome was out for a few weeks before this problem surfaced. I haven't tried to replicate with Firefox as reported, but if that is the case, then issue is not limited to Chrome, so I won't go reporting in Chrome user forums. I think we need to open support ticket with MB if they are not already aware (no official response here). Cheers.
  8. Today the latest version of Google Chrome started to fail upon launch when I have the MalwareBytes Premium 3.0.6 "Exploit Protection" enabled. Upon launching Chrome, all my extensions immediately report by Chrome as "crashed" (pop-up in browser) and the browser window is a black screen (but menus are normal). Unable to access Chrome settings or any Chrome features, but can close Chrome window and not much else. If I turn off MalwareBytes "Exploit Protection" or just disable protection for Chrome.exe via Manage Protected Applications > uncheck "Google Chrome (and plug-ins)", then everything returns to normal when I launch Chrome again. I've checked on multiple Windows user profiles on this same machine that have different extensions installed and behavior is identical. MalwareBytes doesn't report any issues (no explicit detection of problems). Didn't find anything interesting in Windows logs, and no different after system reboot. Chrome is Version 57.0.2987.133 Windows 10 Pro 64-bit (10.0.14393 build 14393.969 -- version 1607, latest security patches applied including KB4015438). Malware Bytes is version 3.0.6.1469, Comp pkg 1.0.96, Update pkg 1.0.1681. Using NON-DEFAULT Settings: Web Protection=OFF, Exploit Protection= ON, Malware Protection= OFF (just doing frequent scans), Ransomware protection= ON. I'm 99% sure my computer IS NOT infected with anything, as all scans (multiple tools) are clean, nothing else out of the ordinary happened lately (no likely infection vectors), and the symptoms have the feel of a Security software vs Application version incompatibility issue. Perhaps I will try to try to remove/reinstall Chrome in case Chrome install is corrupted. Could also run experiment by creating a new windows user with no Chrome extensions at all and check behavior with Exploit Protection turned back on. But BEFORE I go wasting hours debugging this, I'd like to know if anyone else is seeing this issue with same latest version of Chrome and MB 3.0.6 with Exploit Protection ON/OFF. Please post a reply if you see same issue and have success with same workaround of disabling exploit protection for Chrome.
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.