Jump to content

mightaswell

Members
  • Content count

    105
  • Joined

  • Last visited

About mightaswell

  • Rank
    Advanced Member

Recent Profile Visitors

799 profile views
  1. mightaswell

    Notifications Bell

    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.
  2. 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.
  3. mightaswell

    Rootkit setting confusion

    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.
  4. 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.
  5. 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?
  6. mightaswell

    It's Baaaaccckkkkkk!

    Don't have any issue with memory leak or high CPU usage here with update package 1.0.3838.
  7. mightaswell

    no icon in notification area

    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.
  8. mightaswell

    Nothing on Taskbar?

    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.
  9. mightaswell

    Nothing on Taskbar?

    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.
  10. mightaswell

    MB3, LibreOffice on W10 FCU errors

    Internet Explorer is available under Windows > Accessories of the start menu program list (Win 10) . No need to install.
  11. @ArtF I have experienced very similar issues you have described on one older laptop running Win 7 Home edition. The Mbamtray.exe fails to start (is not listed in the Process explorer) at least 50% of the time and maybe more. No re-installs clean or otherwise help. I even suspected a clash between Avast behaviour shield and Malwarebytes but disabling the shield did not help either . I have used your suggestion of adding mbamtray to the start up as a temporary fix and it now appears consistently. The mbamtray and icon not running issue appears to have worsened after the CU 1.0.212 update. IT is reassuring to see the icon present but inconvenient when it doesn't. There is that nagging doubt if an expected icon does not appear that all is not well and I'm sure the folks at Malwarebytes are not unaware of that.
  12. mightaswell

    MBAM3 prevented upgrade to CCleaner

    An update to Googleupdate.exe handle. After updating to Component package 1.0.207 Googleupdate.exe remained locked continuously even with daily shutdown and reboot sequences. After turning off ransomware protection today and rebooting it finally disappeared from the handle list and has not reappeared after turning ransomware back on. So is fixed.
  13. mightaswell

    Malwarebytes randomly locking files

    An update to Googleupdate.exe handle. After updating to Component package 1.0.207 Googleupdate.exe remained locked continuously even with with daily shutdown and reboot sequences. After turning off ransomware protection today and rebooting it finally disappeared from the handle list and has not reappeared after turning ransomware back on. So is fixed.
  14. mightaswell

    MBAM3 prevented upgrade to CCleaner

    @dcollins no I had not rebooted. I have now forced the update to Component package 1.0.207 and that has released all the exe file handles I had problems with except for googleupdate.exe. Should that handle be released? That was after rebooting with the new CP.
  15. mightaswell

    Malwarebytes randomly locking files

    @dcollins I just forced the update to Component package 1.0.207 and that has released all the exe file handles I had problems with except for googleupdate.exe. Should that handle be released? That was after rebooting with the new CP.
×

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.