Jump to content

OrangeSour

Members
  • Content Count

    28
  • Joined

Community Reputation

0 Neutral

About OrangeSour

  • Rank
    New Member
  1. Attaching Zipped File: 3ae96.zip
  2. Attaching logs: Putty.txt
  3. Malwarebytes just detected the installer for PuTTY in c:\windows\installers as malware. I've quarantined the file. How can I get it (and the log) out of quarantine and to you to check for a false positive? Thanks!
  4. EXCEL.EXE does not show up in quarantine. Adding it to allowed does nothing. I cannot delete it or rename it, I cannot reinstall office over it, I cannot restore a previous version of the file from backup because MBAM appears to be blocking my ability to take ownership of the file. WHAT HAVE YOU DONE TO MY COMPUTER?
  5. This is not helpful, and does not address my issue.
  6. After hours working in excel, MBAM just blocked the excel executable itself as "Malware.Ransom.Agent.Generic" This has to be a false positive. I have only been working with self-generated csv files. How do I unblock this? I have things due tonight.
  7. Running Win 10 1903 Enterprise with Avast AV installed. MBAM worked fine until updating to v.4. V.4 spikes WMI Provider Host Service at widlly high CPU usage until all four active protection modules are turned off. Turning off all four modules (Web, Malware, Ransomeware and Exploit) results in CPU usages immediately returning to normal.
  8. Got it - I didn't know if there was some distinction in functionality (say, I'm on a domain, or running Win Enterprise, etc).
  9. What is the "Personal" vs "Work" computer distinction about in the 3.7.1 installer? Thanks!
  10. Weird, I did have notify checked, but I'm doing the manual install as suggested. Anywho, zip attached! calibre.zip
  11. Been using the well-known Calibre E-Book software, along with MBAM, for years. Today, MBAM picked it up as ransomware - has it been infected, or it this a false positive? Malwarebytes www.malwarebytes.com -Log Details- Protection Event Date: 8/26/18 Protection Event Time: 12:29 PM Log File: 21e67fe2-a94d-11e8-9182-bc83850463af.json Administrator: Yes -Software Information- Version: 3.5.1.2522 Components Version: 1.0.391 Update Package Version: 1.0.6513 License: Premium -System Information- OS: Windows 10 (Build 17134.228) CPU: x64 File System: NTFS
  12. I'd had this problem before, and it had gone away - but it's popped up again. Interestingly, although I have two machines with virtually identical configurations - it only happens on one of them - and the difference between them is this: the computer running Office 2016 is fine, but the one running O365 has the error.
  13. You're right - it was Avast - despite being "updated" to allow this patch. Removing and reinstalling Avast did the trick.
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.