Jump to content

mightaswell

Honorary Members
  • Posts

    126
  • Joined

  • Last visited

Everything posted by mightaswell

  1. 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?
  2. Don't have any issue with memory leak or high CPU usage here with update package 1.0.3838.
  3. 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.
  4. 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.
  5. 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.
  6. Internet Explorer is available under Windows > Accessories of the start menu program list (Win 10) . No need to install.
  7. @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.
  8. 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.
  9. 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.
  10. @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.
  11. @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.
  12. @fr33tux Downloaded the 7.0.3.1 version yesterday and checked the Checksum and all okay. Today when I went to "Help" and "Check for updates" it is telling me it is outdated and a new version is available.On accepting it directs me to the exact same download page for 7.0.3.1 with same checksum. So seems it isn't fixed yet!
  13. @Hawaii_Beach quite true. Even Avast Instup.exe and Avastui.exe and iexplore.exe are "locked" on the Win10 PC. Seems strange that it only seems to affect the Win 10. On Win 7 machines ProcExplorer does not find any of the non MB3 related exe files "locked" to MBAMService on the Win 10.
  14. I have come across a very similar situation in this topic. MBAMService is locking numerous exe files at different times and even those on the exclusion lists. It seems to prevent the deletion or updating of that file which is locked.
  15. An attempt to update ccleaner to latest 5.35 was blocked as above and once again after closing the mbamservice handle (Using Process explorer) on ccleaner64.exe I could update. I also noticed handles for other programs ie Acrord32, cs.exe. outlook.exe, winword.exe, adwcleaner.exe and avastUI.exe . Many of these programs were not running at the time. After updating I remembered your request to disable ransomware protection so after rebooting and ccleaner64.exe was back as locked I disabled the protection but did not remove the handle. Affected Malwarebytes version 3.2.2.2018 CP 1.0.188
  16. @Metallica yes good news and I believe it only affected 32bit systems - mine 64X. Malwarebytes 3.2.2.2018 CP 1.0.188
  17. @Metallica my CCleaner version is the latest 5.34 and I had not installed 5.33 at any stage- fortunately by what your article suggests. Also at no stage of installing CC 5.34 did MB3 or Avast (with hardened mode aggressive) raise any flags or warnings.
  18. (Win10 Pro 1703) Whilst attempting to upgrade manually to the latest version of CCleaner I received the message "error writing file to C: /........../ccleaner64" and a few options for what to do none of which was successful. Remembering that mbamservice had locked files for opening Procmon64 recently( in the temp folder) I used Process explorer and searched for a handle related to ccleaner64.exe and mbamservice was locking it. I used Procexplorer to close the handle with mbamservice and was then able to upgrade. Had not had this before. This is now the second time a known legitimate process has been locked by Malwarebytes and usual functionality prevented from working. Is this a known problem?
  19. This sounds similar to a problem I had today. I just spent hours trying to figure out why sysinternals Procmon wasn't running. Got the message "Unable to extract 64-bitimage. Run Process Monitor from a writeable directory." Eventually found that the temp file that Procmon uses was locked by Malwarebytes. Rebooting the computer did not fix the locked file. Using Process explorer was able to close the handle. Procmon ran normally after that.
  20. Version 7.0.2.0 beta 2 is finding 34 Fps related to Spyware Blaster. AdwareCleaner removes the protections that SpywareBlaster puts in place. AdwCleaner[S60].txt
  21. To @fr33tux, the 1.0.2.0 beta version 2 is running and updating the database successfully on both the win 10 PC and win 7 laptop now so well done!.
  22. Thank you @fr33tux When running Version 7.0.1.0 on Win 7 laptop for the first run of the day today the programme immediately says "updating database" but it really does not successfully do so. Running programme again immediately it will report "checking database" and then followed by "updating database" and it then correctly uses the more recent database.
  23. Further to topic: I find that sometimes 7.0.2.0 beta doesn't update database correctly especially if it warns that the programme is out of date and after declining the subsequent run will provide an earlier database. However a further subsequent run will often then update the database correctly. Still a hit or miss matter but more often than not the most recent database is being used in the beta 7.0.2.0. AdwCleaner_Debug.log
  24. Have checked again and the beta version 7.0.2.0 seems to be updating the data base correctly but only if version 7.0.1.0 isn't run also. Somehow running 7.0.1.0 affects how the beta updates subsequent to that.
  25. Have not been able to get Adwcleaner to update to the latest database. However when I run latest Beta Version 7.0.2.0 as per Step 1 # AdwCleaner 7.0.2.0 - Logfile created on Fri Aug 04 06:02:44 2017 # Updated on 2017/29/08 by Malwarebytes # Database: 07-31-2017.1 # Running on Windows 10 Pro (X64) # Mode: scan Then if I run version 7.0.1.0 afterwards as per this - the latest data base is used. Step 2 # AdwCleaner 7.0.1.0 - Logfile created on Fri Aug 04 06:04:08 2017 # Updated on 2017/05/08 by Malwarebytes # Database: 08-03-2017.1 # Running on Windows 10 Pro (X64) # Mode: scan Running 7.0.1.0 AGAIN gives this. NOT the latest data base. This is reproducible Step 3 # AdwCleaner 7.0.1.0 - Logfile created on Fri Aug 04 06:13:49 2017 # Updated on 2017/05/08 by Malwarebytes # Database: 07-31-2017.1 # Running on Windows 10 Pro (X64) # Mode: scan Adwcleaner will not use latest database till the sequence steps 1 followed by step 2 is performed This is very strange and seems to indicate a problem with the programme. AdwCleaner_Debug.log
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.