Jump to content

lmod

Members
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lmod

  • Rank
    New Member

Recent Profile Visitors

1,030 profile views
  1. No fresh install, I had installed 3.7.0 the day it was issued. I have also installed the new W10 build on my Surface Pro 4 which is enrolled in the "Skip Ahead flight" ([so the W10 was delayed for a few hours] later than the desktop.) Again, no fresh install of Malwarebytes 3.7.0. All protections are enabled on that system also. and a Threat Scan, with Root Kit check, has completed successfully.
  2. Malwarebytes 3.7.0 has all protections enabled on the "just issued this morning" W 10 build 18329. A Threat Scan with Root Kit checking enabled ran successfully. 😃
  3. I've just updated to version 3.7 on my Surface Pro 5 running W10 V 1809 build 17763.292. All protections enabled, and a Thread Scan ran to completion (RootKit scan included.)
  4. The Update to Version 3.7.0.2831; Component Package 1.0.535; Update Package 1.0.9028 (which was notified today) has both Exploit and Malware protection enabled. But it only opens a (mainly) blank window when attempting to run a 'Threat Scan', so no change there. This is on Windows 10 Insider build 18323, on two different machines. If I run a Hyper Scan that runs (apparently) OK. Attempting to run a 'Threat Scan' after running a Hyper Scan results in the Scan window showing the result of the Hyper Scan. The update to version 3.7.xxxxx installs extremely slowly. I realize these issues
  5. Here is the Support tool log mbst-grab-results.zip. Attempting to run a scan still results in a blank window. A Hyper Scan appeared to run to completion, reporting no threats. But a Custom Scan (C: Drive only) resulted in this report. I strongly suspect the "Items Scanned" number is a carry over from the Hyper Scan.
  6. Hmm, when I try to run a scan on my desktop system, I get this more or less blank window. I rebooted the system after attempting a scan and getting this blank window, but the reboot hasn't changed the situation. A scan ran when I first logged onto the system this morning, and reported that no threats were detected. That was before I ran " run_procmon.bat " A scan has just ran to completion, including scanning for rootkits, on my Surface Pro 4
  7. I followed the instructions in post #31 above, but didn't get any notice about the DDA error. This has been the case with system reboots over the last few days, both on my desktop and my Surface Pro 4. Both systems are running Insider build 18323.1000. I get the message about protection being turned off on both systems. https://we.tl/t-vYvWtnoQ9R
  8. I opened a ticket ( 2522848 ) yesterday about this problem, after running the support tool, which I understand collected some data and transmitted it to Malwarebytes. and offered to create a ticket. If someone is working on that it may be worthwhile consolidating the efforts.
  9. I also had a problem with Malwarebytes 3.0.6 and Office 365 apps. Both on Windows 10 Version 1703 (build 15063.138 on my Surface Pro 4 and on the Windows 10 Insider Preview on my 'home-brew' desktop. As far as i can ascertain this problem began with the upgrade to Office 365 Version 1702 (Build 7870.2038). I therefore suspect that there is a change in that build that doesn't play nice with Malwarebytes. Symptom: Opening Word, Excel or Publisher,then using the 'Open" function to browse to a file to open it results in the Office app going in a "Not responding" state. The app has to be c
  10. I'm running MBARW Beta 9.16.484 and at each system restart the GUI launches, and remains in the centre of the Primary monitor. An icon is also placed in the system tray. I have been manually closing the GUI (not minimizing) as the Malwarebytes anti-Ransomware process shows as a running process in Task Manager. My OS is Windows 10 Insider build 14388
  11. Thanks for the replies - yes , I gathered from Google that Starnet.md hosts what I think are undesirables. But I would like to know why I am seeing these pop-ups now - is it something on my system that is calling out? I have blocked that IP in my firewall, but I'm still getting these pop-ups from MalwareBytes. While I'm glad that MalwareBytes is preventing the connection, I'm puzzled! thanks, lmod
  12. Hi, I am running Windows 7 Ultimate RTM as my OS, ESET Smart Security as AV, Anti-spyware & Firewall and MalwareBytes Anti-Malware. In the last week or so I have been getting frequent pop-ups from MalwareBytes that it has blocked access to IP 89.28.44.137, also 89.28.21.50. These IPs resolve to starnet.md I have never visited that site. MalwareBytes reports (today) that my machine is clean - ViprePCRescue, which I ran last night, found a suspicious entry in Recycle Bin, which it cleaned. I'm starting to wonder if this message should read that MalwareBytes has blocked access FROM (rather
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.