mightaswell

Members
  • Content count

    96
  • Joined

  • Last visited

About mightaswell

  • Rank
    Regular Member

Recent Profile Visitors

605 profile views
  1. 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.
  2. @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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. ADWcleaner 7.0.3.0 wrong version

    @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!
  8. MBAM3 prevented upgrade to CCleaner

    @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.
  9. Malwarebytes randomly locking files

    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.
  10. MBAM3 prevented upgrade to CCleaner

    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
  11. MBAM3 prevented upgrade to CCleaner

    @Metallica yes good news and I believe it only affected 32bit systems - mine 64X. Malwarebytes 3.2.2.2018 CP 1.0.188
  12. MBAM3 prevented upgrade to CCleaner

    @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.
  13. (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?
  14. 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.
  15. 7.0.2.0 beta 2 - FP's

    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