Jump to content

rumptybum

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rumptybum

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I will consider scanning with Sophos, but I think the topic is otherwise resolved.
  2. I'm sorry, but I'm not sure why I should. The whole thread was about determining if that Riskware was a false positive, and it was. And I managed to complete a full MB scan otherwise. My computer works fine. I think having MB are Windows Defender are enough, though AdwCleaner and the Safety Scanner are nice. But that's too many programs on my plate. Even if I go to download Sophos, it's asking me for my info like I'm a potential customer. I'm not. I just wanted to have possible malware dealt with, and as far as I can tell when looking up details online, it isn't going to be as suffi
  3. The scan has finished. I did not get the Riskware detection. I did get three detections, however; they were all of Malware.Ai variety, and I feel like they too might be false positives. But it's not like I've been using the detected files at all as of late, so I still quarantined them. mbscanfull.txt
  4. I already started a scan with Malwarebytes hours ago with rootkits disabled. It is still scanning.
  5. I can't get a hold of the file. As soon as I try quarantining it it doesn't appear in the Quarantine List, nor is it there when I reboot the system. The tmp folder never has any files shown throughout the scan and after, either. That said, I did find a forum thread that seems to document similar experiences. It is worth noting that this detection only occurs if I configured a scan (which is what I had been doing here) to have the entire C:\ drive scanned w/ all scanning options enabled, including rootkits.
  6. It keeps getting detected when I do this kind of scan, though. So I imagine the tmp folder is generating files as the scan is going on.
  7. It's not in Quarantined Items. I think I'll just run the scan again to catch it.
  8. Yes, I open the folder and there's nothing in it. Hence the zip error message.
  9. Thing is, that detection may be from a file that only shows up as Malwarebytes was scanning. I tried zipping the tmp folder now, but the computer claims nothing is in there, so it can't.
  10. As in matter of fact, wouldn't it be possible this is a false positive? This detection is for a file found in MBamservice's TMP folder, which I imagine is for temporary files relating to Malwarebytes. That would explain why it leaves quarantine upon rebooting the system. The file ends in .dll-k.mbram, after all
  11. The detection came up again. All that, and it came up again. -Scan Summary- Scan Type: Custom Scan Scan Initiated By: Manual Result: Cancelled Objects Scanned: 331739 Threats Detected: 1 Threats Quarantined: 1 Time Elapsed: 3 hr, 49 min, 58 sec -Scan Options- Memory: Enabled Startup: Enabled Filesystem: Enabled Archives: Enabled Rootkits: Enabled Heuristics: Enabled PUP: Detect PUM: Detect -Scan Details- Process: 0 (No malicious items detected) Module: 0 (No malicious items detected) Registry Key: 0 (No malicious items detected)
  12. I have done the fix, and I've done further scans through the other programs. The logs for them are attached. The computer seems to be fine. I did notice AdwCleaner still identified two pre-installed HP items, but I decided to leave them alone since they're from HP. However, in the first place, I found that riskware detection by trying to do a full scan with Malwarebytes. I think I will try doing a full scan (or as full as I can make it be) tomorrow to see if the detection would still pop up. msertnew.log AdwCleaner[S02].txt NewMBscan.txt Fixlog.txt
  13. Here is what I've got MBscan.txt Fixlog.txt Cleaner.txt msert.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.