Jump to content

mightaswell

Members
  • Content Count

    111
  • Joined

  • Last visited

About mightaswell

  • Rank
    Advanced Member

Recent Profile Visitors

1,196 profile views
  1. @LAVA Component Update 3.6.1 v1.0.508 was released on December 7th. The Tensforums article you linked described issues back in November before the offending CU update had been released to the general public so would appear to be unrelated. However I agree with @abs7125 and @mkaz that it does appear likely to be more widespread than they could know. When a computer freezes and needs a hard reboot or is simply powered off normally how is that sort of data differentiated?
  2. Ever since Component Update 3.6.1 v1.0.508 was released on December 7th there has been a steady stream of users complaining of frozen systems , crashing or slow systems attributable to that specific CU update . Malwarebytes is aware of the issue which they are trying to fix. As the update propagates more systems are being affected. That said the folks at MB insist that only a minor percentage of machines are affected. I have taken the step of preventing the Component package updating to the 508 version and have none of the above problems on either the win 7 x64 or Win X x64. If you still have the older installer then revert to that version and turn off the automatic downloading of the application component updates till the issue has been resolved. (Go to Settings then the Application tab) It seems that those symptoms have been "prevented" when users (1) turn off MB web protection or (2) turn off exploit protection module in MB. Also suggested as There is also an add on for Chrome to provide online protection similar to the main MB. None of the above is a real solution but till MB fixes the issue that the CU 508 has reintroduced or introduced it is a work around to prevent crashing and freezing. I would suggest it prudent to have another antivirus ie Avast or AVG free installed alongside in any event.
  3. It isn't OS specific. This laptop is running Win 7 and has a similar error report. It is described as APPCRASH . The crash is not very obvious as occurs on shutdown so easy for many users to be unaware. Win 7 does have the action center flagging the error and offering "checking for solutions". I imagine that would be fruitless exercise anyway.
  4. No problem at all. You are wise to be careful and if in doubt check.
  5. The version you have is 3.4.5 and the latest version of Malwarebytes is 3.5.1 so it is probably a correct notification. There is indeed a new version to the one you have. So I would say it is legitimate. What makes you think it isn't?
  6. That bell is just a part of the dashboard and shows a red alert when there is a notification as below. Yours shows no notification so all is good. If a notification is shown click on the bell and you'll see details about the notification and then the alert clears automatically.
  7. Maybe the issue @lock is one of veracity and robust proof of purchase linked to an email account. Having a screen shot of keys installed and providing an email may not provide MAlwarebytes with the kind of linkage they require for the account.
  8. Hi @Benequest , There is nothing wrong with Malwarebytes but you'll need to change a setting in the scheduled scan option. In order for the regular scheduled scans to perform the rootkit scan you need to open Malwarebytes and then select "settings" and then click on the "scan schedule" tab. Then tick the box next to the scan you wish to add the rootkit scan for (there might only be one listed) then you'll notice the "edit" button will become active. Click on the "edit" button and a window will open with details of the scheduled scan. Click on "advanced" button and the options to include a rootkit scan will appear along with a few other scheduled scan options. Select the "scan for rootkits" option and a tick will appear in the box next to the option. Click the "okay" button and you should then have scheduled scans which include the rootkit scan option.
  9. Select "close" on the scan window (if it shows the scan and quarantine is complete window), then select dashboard before reselecting the scan option which then should show the custom scan window. Choose Custom Scan and then configure.
  10. The latest stable Avast version 18.1.2326 has just been released. Amongst other things it spruiks "What's new: - We've added a new Anti-Exploit module for better protection against exploits, shellcode, and other malicious executable files" Before jumping in and updating Avast does anyone know if Malwarebytes anti exploit module and the "new" Avast anti-exploit module play nicely together? Or should one be disabled?
  11. Don't have any issue with memory leak or high CPU usage here with update package 1.0.3838.
  12. Hi @Arsenal123 I had a similar issue with a Win7 which was fixed with the latest component package version 1.0.262. You seem to have an earlier version . If you open Malwarebytes GUI through the desktop icon , go to "settings" then "Application " and then click on "Install Application Updates" Malwarebytes should update to the latest component package. That did at least fix the no icon on my laptop - it did take a few reboots for the icon to become stable but now works all the time. It might just help you also. You might need to update to the latest version 3.3.1 first though as Porthos has suggested.
  13. After some further investigation on the affected laptop I discovered that the boot sequence was set to selective start-up (system drivers and start up items only). So I changed it back to normal, deselected protection early start in Malwarebytes and after two restart sequences both Malwarebytes and Avast (with all exclusions) are functioning with all protection layers turned on and the icon is in taskbar. Checked a few more cold boots from turn off and all okay. So it looks like the selective start up was the issue and not Malwarebytes! So can happily report that Malwarebytes is working perfectly on all my PCs and laptops. Hope that continues.
  14. I can confirm this issue of no taskbar icon ( mbamtray not running) and layers turning off on one laptop(Win 7) out of three PCs. Another family member uses it. To get all protection layers of mbam to turn on consistently I have turned on self protection early start. To get the tray icon to appear and have it running I have manually added mbamtray to the startup programs. Otherwise it just doesn't show up and cant tell if all the layers are on or some off etc. Been like this for months through all the recent component upgrades etc etc. Got sick of clean reinstalling and as it is a very slow laptop to bootup it was very time consuming to do that. Anyway the above has fixed it and now the icon always appears after shut down and boot up and all layers are on consistently. I always had the exclusions to Avast free but by itself did not help. I simply haven't mentioned this before as any logs and reboots take way to long on the affected machine and the machines I use work perfectly and consistently and also have Avast free etc and the same exclusions. But there is clearly an issue with some machines.
×
×
  • 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.