Jump to content

SandyWood

Members
  • Content Count

    9
  • Joined

  • Last visited

About SandyWood

  • Rank
    New Member

Recent Profile Visitors

472 profile views
  1. Thanks for the note back on my question. I did run the offline updater but it failed to update any of my clients. They seem happy to be up to date in 2017. I have a support case open to help troubleshoot the issue.
  2. We have a handful of clients that are not updating to the latest database versions. They're all stuck at v2017.11.30.08 oddly enough. If we login to the client and force and manually try and update, it tells us we're current. Anyone seen this before?
  3. How long should I let it run? Since we got the alert on this user, we haven't had any from them. (There have been a few others in our environment, however). If it takes weeks, will that affect the end-user? Will the debug logs grow very large?
  4. Getting a few of these alerts in our environment. They are new Win 10 1607 machines and in each case, the user has several instances of microsoftedgecp.exe running in Task Manager. What can I check to verify that nothing is still lurking about? Exploit threat detected, see details below: 4/20/2018 2:20:53 PM 10-87502 10.17.210.82 Exploit attempt blocked BLOCK jcool microsoftedgecp.exe C:\windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe Attacked application: C:\windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe; Parent process name: RuntimeBroker.exe; Layer: Application Behavior Protection; API ID: 900; Address: ; Module: ; AddressType: ; StackTop: ; StackBottom: ; StackPointer: ; Extra: 4/20/2018 2:22:12 PM 10-87502 10.17.210.82 Exploit attempt blocked BLOCK jcool microsoftedgecp.exe C:\windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe Attacked application: C:\windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe; Parent process name: RuntimeBroker.exe; Layer: Application Behavior Protection; API ID: 900; Address: ; Module: ; AddressType: ; StackTop: ; StackBottom: ; StackPointer: ; Extra:
  5. Just upgraded our MB console to 1.8.0.3443. Deployed two client updates and they appear to have gone well. The only issue I have is that when I try to launch Anti-Exploit I get a message, "The Malwarebytes Anti-Exploit service is taking too long to start. Please reboot your computer to restart protection." Rebooting doesn't fix the issue. Is there anything more I need to do for the service to start? I'd love to upgrade the remaining systems in our office.
×

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.