Jump to content

frozen

Honorary Members
  • Content Count

    257
  • Joined

  • Last visited

Community Reputation

0 Neutral

About frozen

  • Rank
    True Member

Recent Profile Visitors

5,070 profile views
  1. Two more apparent false positives MbamFlasePositives.zip MBamFalsePositives.txt
  2. Yet more false positives on old files on my hard drive. I think in the future I will just delete these files from my drive and stop reporting these false positives. Its a never ending battle with MBam these days. WinToUSB39-db38su.zip reatogo-25-6a.rar FPReport.txt FPReport2.txt
  3. Updated to Start up scan still reports the zip file in this report as: Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 4/5/21 Scan Time: 10:43 AM Log File: a0603eae-9625-11eb-ad29-90e6ba57cdd5.json -Software Information- Version: 4.3.0.98 Components Version: 1.0.1249 Update Package Version: 1.0.39111 License: Premium -System Information- OS: Windows 10 (Build 19042.867) CPU: x64 File System: NTFS User: greg_i5\gregg -Scan Summary- Scan Type: Custom Scan Scan Initiated By: Manual Result: Completed Objects Scanned: 1
  4. POssible false positives in 3 old files that have been on my hard drive for years that have not been used and without any detections until now. FPReport.txt _FalsePositives.zip
  5. It was just a file sitting in my downloads folder. I probably downloaded years ago and there it sat all these years and which I could of just deleted/quarantined instead.
  6. FalsePostivie Report.txtWinsockxpFix.zip Have had this file on my hard drive since 2009
  7. Yet again another false positive Malware.AI https://www.virustotal.com/gui/file/14e67c39fc99c315480f3e916c17fde6df5952bde763ef0c9f44cdc0bdabfec3/detection ipscan25.zip
  8. Another day another false positive of a file I have had on my hard drive since 2008 Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 2/11/21 Scan Time: 2:36 AM Log File: 3a8d9690-6c44-11eb-a771-90e6ba57cdd5.json -Software Information- Version: 4.3.0.98 Components Version: 1.0.1157 Update Package Version: 1.0.36957 License: Premium -System Information- OS: Windows 10 (Build 19041.804) CPU: x64 File System: NTFS User: System -Scan Summary- Scan Type: Threat Scan Scan Initiated By: Scheduler Result: Completed Objects Scanned: 3577
  9. Over the past several months Malwarebytes has been flagging decades old files as malware during its scheduled scans. Rather than report the issue I simply told MBAM to quarantine or delete the file and get on with my day. Today I downloaded an update to a piece of software I used regularly QuickAccess Popup https://www.quickaccesspopup.com/ and the download was fine. I unzipped the file and ran the EXE. No problem. Then the scheduled scan popped up the following detection. Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 2/8/21 Scan Time: 8:04 AM Log File: 98
  10. It is still flagging putty.exe here today. I has not done so in the past with me. Malwarebytes www.malwarebytes.com -Log Details- Scan Date: 9/1/20 Scan Time: 8:11 AM Log File: 95487764-ec54-11ea-8acc-90e6ba57cdd5.json -Software Information- Version: 4.2.0.82 Components Version: 1.0.1025 Update Package Version: 1.0.29307 License: Premium -System Information- OS: Windows 10 (Build 18362.1016) CPU: x64 File System: NTFS User: System -Scan Summary- Scan Type: Threat Scan Scan Initiated By: Scheduler Result: Completed Objects Scanned: 331590
  11. Adding "C:\Program Files\Mozilla Firefox\firefox.exe" as an exclusion to Ransomware and re-enabling Ransomware detection in MBAM allows me to run FIreofox even from the profile on D Drive. That is probably until the the next firefox update I guess.
  12. I just noticed that MBAM is still blocking FIrefox.exe from running. The EXE is still there on the hard drive. I had to close MBAM to run the program. There is s of course nothing inin quarantine. THis is because MBAM did a RTP detection on it. I guess I will have to disable Ransomware altogether in MBAM. If I do then Firefox is allowed to run, Same thing happens if MBAM is closed altogether.
  13. Same thing here. I have been updating FIrefox without issues until April this year and was always using the profile on D drive. Only since then have I had to use the C profile to do the update I bet if I leave FIrefox alone for a day or so I will again be able to use the profile on D drive again without any repercussions from MBAM. At least that was what I experienced earlier this month.
  14. What is weird is that if I perform the update while using the D drive profile MBAM first flags Updater.exe when FIrefox is restartred after the update. Then MBAM simply terminates FIrefox upon restarting Firefox. None of this behavoir occurs when I use the C drive profile.
  15. The problem occurs in my case when I use my normal profile which is stored over on D drive. If I use the profile that is over on C drive (which is a copy of the files I made from the D drive profile) the problem does NOT occur.
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.