Jump to content

td47

Members
  • Content Count

    22
  • Joined

  • Last visited

About td47

  • Rank
    New Member
  1. I just rebooted the same desktop as the previous test I posted, to ensure a fair test, with no cache "primed" by any previous test, but this time with the "Use expert system algorithms to identify malicious files." set to OFF. The elapsed time was 25 Minutes, 20 Seconds, for 388,598 objects, so this was a difference of 2 Minutes 43 Seconds. There were 139 less files, most likely a few small temp files removed by Norton during it's daily perfomance checks. Most users with more modern desktops/laptops with SSD disk, DDR4 memory and faster CPU should see MUCH quicker timings than posted above. I forgot to include the Windows and Malwarebytes Versions in the first test post: Windows 10 Pro version 19041.423, MalwareBytes 4.1.2.73 with UPV 1.0.28147 and CPV 1.0.1003.
  2. FYI: Earlier today, I ran a full manual scan, with "Use expert system algorithms to identify malicious files." set to ON. I suspect this is a newer/better version of what the "Heuristic" scan section was, under the 4.0 and earlier MWB versions. It ran just fine, with no issues, and found no extra items needing quarantine. It took 28 minutes 3 seconds, to scan 388,737 items, on a 50% full Seagate 500GB HDD drive. It did hang a 2 points, 3 minutes at 289,954, and another 3 minutes at 312,991 then continued normally to completion. This test was on a Homebuilt Desktop ASROCK Z68 Pro3-M with Intel Core i3 2100 @ 3.10GHz Sandy Bridge 32nm, Seagate HDD 500GB, 50% capacity. This would take a LOT less time on a system with an SSD, and DDR4 memory rather than the HDD/DDR3 I used for this test. I think that the extra setting added about 8 minutes to the scan, as they are normally around 20 minutes, but I will reboot and retest with the "Use expert system algorithms to identify malicious files." set to OFF next time, and confirm the time in my next post.
  3. Hello @exile360 No problem, and thanks for the additional useful information, I will bear it in mind. I will try the settings, and attempt to do some timings and post them here when I get time, as it might be useful to others with similar interest in this excellent MWB product.
  4. Hello @exile360 thanks for the quick reply, and for taking the time to put in all that very useful feedback and resource links. I will certainly look at the resource links when time permits, and might have a "test run" with it set on to see what it does, and if it detects any (possibly) false positives.
  5. MWB Premium - under Security settings, what is the effect of: "Use expert system algorithms to identify malicious files." ? Does the product have these algorithms in-built, or does it have to go online to an external server to check suspicious items? I see it is set off as default, but what percentage (on average) does it add to the system scan time? I have not yet tried it, but I would hope that the "normal" scan algorithgm would pick up most malicious files? I would be grateful for any information or experience users have had, using this setting, and any effects on system running, CPU % etc, or hangs, BSOD etc.
  6. My MWB Premium has been flagging an outbound connection from an email received from Hyundai as regards servicing. The email itself is genuine, but it contains some non-displayed tracking code, that I can see in the email source, that goes to the tracking site at clicksapp.net. This is what is being flagged by MWB. I have attached an export of the MWB event log, in a text file. As the abuse reports in the ABUSEIPDB database are very sparse, and are only at 8% confidence rating, so my question is: Is this report a false positive? CLICKSAPP_NET_ERROR_BLOCK.txt
  7. Hi @Exile360 - thanks for the info. Maybe I am thinking of a much earlier release of MWB, possibly prior to 4.1. As you say, the DOUBLE left-click does open the UI. I have done another tray app review, and compared the desktop with the laptop, and actually there is more inconsistency within the various tray quick-start apps stubs than I originally thought. It just seems "odd" comparing with, say Norton Security, or Windows Defender tray stub. There are 4 other tray icon/apps that do react the same as MWB. As the laptop with the same MWB installation is working the same way as the Desktop PC, I don't think it is a bad install, so I will leave things as they are right now. If there DOES appear to be any issue in the future, I will certainly take your advice and run the latest MST, run the clean up, and re-install.
  8. I noticed that after one of the recent updates (forget which) the main MWB UI does NOT now open directly using a left-click on the Tray Icon like it used to. The left AND right clicks now act the same, that is, they BOTH provide the Context (options) menu. Most other tray driven apps provide a main UI open for left click, Context with Right Click. Does any one on here know WHY this design change was made? OK, it is only an extra click to get the main UI, but it just "feels" a bit odd. Were there complaints for the more "standard" way?
  9. I have read this topic with interest, as I have had a lot of issues with Windows 10 2004 update. I WAS seeing the100% System Interrupts issue, with and without MalwareBytes running (I am making the assumption here that exiting with the System Tray MWb GUI Does stop everything, and certainly the Task Manager Sevices view DOES show the MWB Servis as "stopped" when the exit is done). I have also had the issue with browsers taking a long time to startup, and Firefox 78 startup in with a blank window, and not start the 60+ tabs from last session. The worst issues were with File Explorer hanging during saving files, either on its own, or as part of MS WORD files saves, or Notepad files saves, and general lagginess of the whole system. Most of the issues cleared up after I stopped and disabled the SysMain and Windows Search services (also might need to stop and change to manual the Windows Media Player Network Sharing Service first, if running, as it has a cooperative link with Windows Search, and might hold up the initial "stop", causing a watchdog timer to go off). I also saw a reccommendation to turn off (untick) the Fast Startup option in the Control Panel -> Power Settings -> "Choose What The Power Buttons Do" section (you may need to click on the "Change Settings that are currently unavailable" blue link to allow the untick for that). After doing those things above, the high "Sytem Interrupts" percentages for 30-40 seconds when Task Manager started, seemed to stop (about 12% for a few seconds, then dropped to around 1% or less), AND the system seemed to go back to normal, as regards the File Explorer and saving and browser issues. Note that I am using both Norton Security AND MalwareBytes together (as I have always favoured this layered approach to security). Windows Defender is NOT active in this scenario, as Norton is registered with the system. Other users have found that the latest updates KB4565503 and KB4565627 have fixed many issues, BUT I only found them to have made the system slightly more responsive. I have not experimented with turning on those stopped services, as I don't need Windows Search anyway, I use Agent Ransack if I want to find where I put an old PDF for example. HOWEVER: today I saw the issue with Firefox and File explorer return, as I have not rebooted for over a week. I DID exit Malwarebytes, and Firefox was still stuck, and File Explorer was still not responding again. Many of the reports I see on Microsoft Answers, do NOT mention MalwareBytes users, just the odd one or 2. So, my take on all the above is that the issues seem to be caused by some Feature Update 2004 design changes in the OS Kernel, with File Explorer and Windows Search not interacting seamlessly with Windows Explorer, and other internal stuff (like thread and process creation) getting stalls because of it. I cannot vouch for the IPV6 issues, as I don't THINK I have seen any, and my impression is that MalwareBytes may be just an "innocent bystander" in some of the issues reported. On a closing note: I DID see that an update to MWB (don't know which one) set ON the setting : "Collect Advanced Event Log Settings for Support", so I turned that off, as it said "Not Recommended" to be ON anyway. That initial 12% System Interrupts when Task Manage starts seemed to halve with that off.
×
×
  • 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.