Jump to content


  • Content Count

  • Joined

  • Last visited

About dagar74

  • Rank
    New Member

Recent Profile Visitors

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

  1. I see nothing about version 3.8.3 but posts with problems with licensing after the upgrade. Thought someone might like to get some assurance that upgrades should not be a problem if your licenses are OK. I upgraded all 3 of my computers and it went smoother than any previous upgrades. All of my Exclusions and Settings were retained and my lifetime licenses were kept. I do have to say that I did have a license problem about a month ago on one computer, but Malwarebytes Support fixed it for me after I forwarded purchase records. Getting your licenses correct in My Account at Malwarebytes website is worth the effort.
  2. Since there may not be too many people running Windows 10 version 1903, I installed Malwarebytes on my test machine that was clean installed to 18362.53 via an ISO from UUP Dump and then updated to 18362.86 via Windows Update to provide some additional experiences. I did use the settings recommended by Maurice Naggar in post 27, above, and there are no performance problems or Window Security Issues on this machine. Defender works fine and was enabled as soon as I selected Never Register Malwarebytes in the Action Center.
  3. I would like to make it clear that my original post was not because I was having problems running Kaspersky Total Security and Malwarebytes Premium. They are functioning together well for me. When I was doing a clean system install, I found a couple of files I hadn't seen in earlier versions and wanted some clarification on excluding them. I was also trying to be sure that I was doing the right thing regarding using System32 folder or Synsnative (I had actually been entering both in Exclusions for insurance). I also wanted to ask about excluding the .exe files as Trusted Applications. I have not been having any problems due to running Kaspersky and Malwarebytes together on all 3 of my computers that are so equipped..
  4. Davidtoo I read your list of Exclusions and note than you have all of the Malwarebytes executables (.exe files) listed under Exclusions. Have you tried listing those files under "Trusted Applications" as discussed in Posts 4 and 5, above.
  5. Thanks exile360. I will continue adding the executables. It seems like it would be good for Malwarebytes to update the Support Article mentioned in your first post to include the executables for programs like Kaspersky that have a Trusted Applications exclusion.
  6. Thanks for the reply exile 360. I have changed my drivers to list the Sysnative folder instead of System32 and also excluded the MbamElam.sys file that I found in my System32 folder. Kaspersky settings for Exclusions includes two categories of Exclusions: "Manage exclusions" and "Specify trusted applications". The Manage Exclusions option is where the items you recommended go. It may be overkill, but for the last couple of years I have also been clicking on "Specify trusted applications" and adding 8 Malwarebytes executables like "C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe" as Trusted Applications, just to be sure that Kaspersky leaves Malwarebytes alone. Do you think that adding the executables to Trusted Applications is a waste of time? Thanks again
  7. Reinstalling Windows 10 1809 and all software, I ran into a problem setting up Exclusions for Malwarebytes Premium version 3.7.1, in Kaspersky Total Security 2019. This is probably due to the new version 3.7.1, which I had not used before. I tried to set the exclusions using previous guidance that I had found on this forum but could not find all of the drivers. I found a support DOC 1123 that says it was updated on 2/14/2019, but it does not include two new files mentioned in a post by 1PW on 12/22/2018, which are present in my system (mbamwow.exe and malwarebytes_assistant.exe) and I did exclude these. Previous guidance on excluding drivers has flip flopped over a couple of years between using them in the C:\Windows\Sysnative folder or the System32 folder and the above mentioned DOC 1123 uses the Sysnative folder which is is not visible in Explorer regardless of viewing options. I only found mbae64.sys and MbamElam.sys (not in the previous list) in the System32\drivers folder, but none of the remaining 5 .sys drivers previously excluded in my version 3.6.1 Malwarebytes installation. I would really appreciate some updated guidance on the exclusions to be set in Kaspersky to include mbamwow.exe, malwarebytes_assistant.exe, and MbamElam.sys, plus clarifying whether we use the Sysnative or System32 folders. Thank You
  8. At about 10:00 am Pacific time, I started computer for the second time this morning. I immediately ran in to problems. Chrome would not open even with 3 instances in Task Manager, Firefox would not open, Word 2013 would not open. Explorer and Task Manager would run but it took a couple of minutes for them to open. In Task Manager, the APPs section had a "Not Responding" message and it would not display the data graphs for CPU or Memory. I tried to run your Support Tool at that point, but it would not run. I finally got the computer to shut down. I restarted again and had the same problems, so I again shut down the computer, which takes a very long time. Computer has Intel Core i7_7700K and 16 GB of memory and the things that would work took an extremely long time. Upon restart of the computer the third time, I immediately quit Malwarebytes Pro (latest version) and then everything is now working properly with Malwarebytes off. I ran the Support Tool and am attaching the zip folder. For now, I am going to keep Malwarebytes off until I hear that the problem is resolved or a fix is offered. mbst-grab-results.zip
  9. Great help. Thanks very much. I tried both methods and Autoruns identified an additional driver not in the System32 folder: C:\ProgramData\Kaspersky Lab\AVP19.0.0\bases\klids.sys Should this one also be excluded? Thanks again.
  10. Thanks for the reply. I have had full Exclusions and Trusted Applications listed for Malwarebytes in Kaspersky for a long time and updated them in Malwarebytes recently when I updated Kaspersky to the 2019 version. I have the six Malwarebytes executables in Kaspersky Trusted Applications and the Malwarebytes folders plus 6 drivers in Exclusions. As to the Exclusions in Malwarebytes for Kaspersky, I have only been excluding the Program Files folder and the Kaspersky executables listed in the Program Folder. I just now added C:\ProgramData\Kaspersky Lab and Kaspersky Lab Setup Files folders. I apparently need to add the Kaspersky\system32\drivers you refer to but I will need to find a list of which ones to add. If you have a link to that information, I would appreciate it. I will let you know if it occurs again.
  11. After about an hour of normal operation this morning, I noticed that Web Protection had turned off. Malwarebytes is fully up to date with version 3.5.1, Component 1.0.374, and update 1.0.5556. I quit Malwarebytes and restarted it, but got a message notification that Malwarebytes is unable to load the Anti-Rootkit DDA Driver. This error may be due to rootkit activity --- and recommended rebooting. After reboot, web protection was back on and a Threat Scan found nothing. A full scan with Kaspersky Total Security 2019 also found nothing wrong. No problem currently but I am attaching the mbst-grab-results for your information. mbst-grab-results.zip
  12. Web protection turned off after about 1 hour running normally. Malwarebytes 3.5.1 and Windows 10 Pro Version 1803 Build 17134.48. I ran the Support Tool before doing anything else and then ran the SC DELETE MBAMWebProtection command posted by exile360 and got the following results. After restarting Malwarebytes Web Protection was turned on and all protections appear normal. The mbst-grab results are attached. Microsoft Windows [Version 10.0.17134.48] (c) 2018 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>SC DELETE MBAMWebProtection [SC] OpenService FAILED 1060: The specified service does not exist as an installed service. mbst-grab-results.zip
  13. Computer with Windows 10 vs 1803 Build 17134.48. The MB 3.5 Beta was installed a couple of days ago and working properly. I attempted to update to the new 3.5.1 release by going to Settings > Install Application Updates (Kaspersky Total Security was already paused). The update started but almost immediately asked for a reboot. After the reboot, MB was completely gone (uninstalled but not reinstalled). There was only one file left in Program Files\Malwarebytes\Anti-Malware folder. I tried two more reboots with no success. I then downloaded the new 3.5.1 version from your the link in this forum and installed it. The good news is that it actually installed and it included my License ID and Key, plus my Exclusions were also present. I was glad to not have to re-add my Exclusions and License. No problems now, but posted for others information
  14. I just updated to version 3.4.4 from the previous latest non-Beta. I clicked in Settings to allow installing the latest update. Unfortunately, it completed the update OK but wiped out all of my Exclusions that I had set for Kaspersky and the Utilities folder on my PC. I am turning off Malwarebytes until I have time to redo the exclusions. Posted as a caution to others getting the update - check to see if your previous exclusions are still there.
  15. The mb-check results are attached. Unfortunately, the full C:\WINDOWS\Memory.dmp file is no longer present on the computer. I am also attaching a zip of the mini dump file, however, based on the WhoCrashed analysis of the two dump files, only the full dump file analysis, which was in the original post, showed the issue with farflt.sys. I will try to do some more testing in the next day or so and if I have the problem again, I will save a copy of the full dump file mb-check-results.zip 111017-4750-01.7z
  • 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.