TempLost

Members
  • Content count

    152
  • Joined

  • Last visited

About TempLost

  • Rank
    Advanced Member

Recent Profile Visitors

653 profile views
  1. I was a safe driver until somebody ran into me.................
  2. Thanks, Porthos, I'll change the Windows Action Centre settings...........
  3. I'm currently running Malwarebytes Premium 3.1.2.1733 alongside Avast Free, currently at v. 17.4.2294 (build 3482.0). The two seemed to coexist happily and I've added exclusions to both programs - see this post for Porthos' excellent guide However, another problem has just surfaced for me - I carried out a repair install to Avast in the Add/Remove programs options to try to resolve some problems with the Software Updater Module and, when the repair had finished, got a message on the screen saying something like "Incompatible antivirus detected - Malwarebytes - we strongly recommend uninstalling" The two programs seem to run together nevertheless - is it perhaps best to change settings in Malwarebytes to "Never register Malwarebytes in the Windows Action Centre"?
  4. Have been running Malwarebytes Premium 3.1.2 since it was released and all seems fine so far - installed it over the top of the beta version. Haven't tried to break it yet, but seems it's nearly there. As I've posted elsewhere, no version of Malwarebytes 3 yet seems able to retain the language settings when installed over a previous version. Otherwise, well done Malwarebytes team! Windows 7 Home Premium SP1 x64, Avast Free latest version
  5. I can't see the individual drivers either - I was able to navigate to, and exclude, the drivers in an earlier (and quite recent, but can't be sure of which one) version of Avast Free but cannot do it in the latest version. Windows 7 64 bit........
  6. OK - turned off rootkit scanning and ran another scan, but got the same error message and crash. I'll wait to see what analysis of the logs brings. Should I turn off Event Log Data Collection in the meantime?
  7. OK - turned off rootkit scanning and ran another scan, but got the same error message and crash. I'll wait to see what analysis of the logs brings. Should I turn off Event Log Data Collection in the meantime?
  8. OK, I'll turn off rootkits scanning. I'll probably be out of the loop for a bit as my evening meal will be on the table soon (I hope). Could be 12 hours or so before I get back to this thread - could be earlier if the TV is lousy........
  9. Jekko, OK, MB crashed on a different file this time - I couldn't get a screen grab as Snipping Tool wouldn't work. I've got the two sets of logs but, even zipped, they are too big to upload to the forum - can you give me another location? Everything runs fine until the scan crashes, then a lot of things go awry with Windows. Couldn't open Snipping Tool, sound card is turned off, probably other things as well. I'm pretty sure the laptop is clean - it's been running pretty sweetly of late - virtually no problems shown in Reliability Monitor of late - it just seems to be this beta that's thrown things adrift.......
  10. Will do, Jekko.........
  11. Sami1953 Here you are.......
  12. Additional Info. If I carry out an individual scan of MANAGE-BDE.WSF in Windows Explorer by right clicking with Avast, I get "No Threat Found". If i carry out the same with Malwarebytes, I get the report below:- This shows 0 files scanned........ Malwarebytes doesn't crash on the individual file scan.
  13. OK, curiouser and curiouser - I carried out a clean uninstallation using mb-clean-2.4.1.1021.exe. I followed all the steps in the instructions except did not opt to download and install the latest MB 3.0 version after reboot but again installed the beta version 3.1.0.1716. After adding password and ID, updating, setting up exclusions and changing the language to UK English I ran a full scan which again failed while scanning files. I managed to do a screen grab this time and it appears to have failed scanning WINDOWS\SYSTEM32\MANAGE-BDE.WSF I've never had a scan fail like this under earlier versions of MB - any ideas?
  14. I've decided to do a clean uninstallation with the clean tool and try to reinstall 3.1.0.1716 beta. I'll report back.