Rsullinger

Staff
  • Content count

    426
  • Joined

  • Last visited

About Rsullinger

  • Rank
    Staff

Recent Profile Visitors

4,529 profile views
  1. Hey Iambry, It seems like the tool didn't gather the logs which is strange since there should have been an alert generated for this. I apologize for this, but can you collect the C:\ProgramData\Malwarebytes Anti-Exploit directory for me so I can be sure the logs are collected. If an alert was indeed created, it should be in that directory.
  2. Hey Iambry, You may need to run the tool as an admin, however it will collect the logs from the C:\Programdata which is shared by all users. So you don't need to run it on the user that had the issue.
  3. Hello Iambry, I want to have you collect some logs from the event so I can look into this further. To do this: Please download our diagnostic tool, MB-Check to your Desktop from this link: https://downloads.malwarebytes.com/file/mb3_check Double-click it to run it. A black command prompt window will appear momentarily and you will see a message appear telling you to locate the zipped log files. A zip file named mb-check-results.zip will be saved to your Desktop. Please attach this file to your next reply.
  4. Hello dfkosek, Do you mind collecting the logs found from this post: https://forums.malwarebytes.com/topic/191468-readme-first-posts-here-need-to-include-mbae-logs/ I want to see if this has to do with the issue that is fixed in our latest version.
  5. Hello PC22, Please collect the logs found from this post: https://forums.malwarebytes.com/topic/144403-readme-first-posts-here-need-to-include-mbae-logs/ This may be due to a browser addon so please make sure you get the FRST logs from the instructions at the bottom of that post along with the anti-exploit logs!
  6. Hey Billmobile1 and all, There will be a new update pushed out for mbae later today through our automatic updates. It will include the fix for this issue reported in this thread. If you have automatic update enabled, your clients will receive this build as well.
  7. Hello @spnkzss, Did you just recently upgrade to 1.8.0.3443? If so, did you push out the updated managed client to the machines that were having this problem yet? This seems like it may be an issue caused by the managed client not using the policy you currently set. It is recommended you upgrade the managed client if you have not done so already. If this has already been done, then I want to see some logs from a client in question to see why our policy is not applying that auto upgrade setting. To do this: -Locate the this folder on the client computer: C:\Program Files (x86)\Malwarebytes' Managed Client -In this folder, right click the 'CollectClientLog.exe' utility and run it as admin. -Save these logs to the desktop of the computer. -Zip up this folder and attach it here. @StewOMC A new version has not been released yet unfortunately. Our Technical product manager for anti-exploit responded on this post with an update. I do apologize for the delay in that and the frustration it is causing:
  8. Hey ZZyzx, We have been getting a few reports of this. I am going to reach out to you in a PM to collect some debug logs from you. Please go ahead and send them back in the PM so I can get this over to the team!
  9. Hey KippyKip, That may have something to do with it. I am going to see about having the team reproduce it with the information you provided. I am also going to send you a PM to collect some debug logs. Go ahead and send them back int he Pm!
  10. Hey Hake, I unhid the post in the experimental link. I usually hide them when a new build is out and ready to be tested. You can find the download link here however: https://malwarebytes.box.com/s/ax18zkhp0mg1me96m28kpi3fh5suw1l2
  11. Hey REGITDept, I would at least confirm on one pc if possible. We had a few customers that even after using that last build it was not fixed or the issue came back. So we made a minor change to help as well and we want to make sure everyone is good with this now.
  12. New build 1403: https://malwarebytes.box.com/s/0rohgfvc3hl7mq83aygye6gvoya2nqz7 -Additional fixes for IE freeze issue
  13. Hey everyone, We have a new build we would like to have everyone test: https://malwarebytes.box.com/s/iu4ii7jafj05cdktv1hqkzghkuzja7jj 1403. This build is to fix the IE issue on some use cases where the last build did not fix it. We would like to get your feedback if this build still fixes the issue. Also, if the last build did not fix it, we want a confirmation if this build does. Let me know if you run into any issues with this build!
  14. Hey Kippykip, I want to have you collect me a couple of logs so I can look into this issue further. Can you please collect the files in this folder location: C:\ProgramData\Malwarebytes\MBAMService\logs\ and C:\ProgramData\Malwarebytes\MBAMService\mbae-default.log Along with that, I want to have you run a tool called FRST to collect some information on the computer. To do this: 1: Please download FRST from the link below and save it to your desktop: FRST 32-bit version: https://downloads.malwarebytes.com/file/FRST FRST 64-bit version: https://downloads.malwarebytes.com/file/FRST64 2: Double-click the purple FRST icon to run the program. Click Yes when the disclaimer appears. 3: Click the Scan button 4: When the scan has finished, it will make 2 log files in the same directory the tool is run, FRST.txt and Addition.txt. Please attach both files in your reply.
  15. hello Jwoodskitsap, So the files in that tmp directory are the new update files. If the files cannot be swapped out on an upgrade, we will place the files there and create an entry to swap out those files on reboot. So those files look like they were not swapped in this case. If you stopped the service and swapped the files it would work, but wouldn't fix it for all of your other users. Do you mind looking at another computer having this issue an confirm if it is the same two files in question?