Jump to content

Thankful

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Thankful

  • Rank
    New Member
  1. @pbust, If I do a clean install, is it OK if I delete the ProgramData\MalwareBytes Anti-Exploit folder before installing the experimental build? Thanks.
  2. First I installed production version OK. Installed new experimental build on top. Had to reboot twice before icon appeared in taskbar. Seems OK now. I would prefer to be able to do fresh install of experimental builds rather than installing over top of existing version without losing "premium" content.
  3. Glad I found this thread. I'll install the latest beta. Thanks.
  4. Here is the entire log file: 2013-08-01 19:50:54 - The Malwarebytes Anti-Exploit task scheduler has been successfully created 2013-08-01 19:50:54 - Malwarebytes Anti-Exploit Driver Installed successfuly 2013-08-01 19:50:54 - Malwarebytes Anti-Exploit Driver is running 2013-08-01 19:50:54 - Starting Injection with: C:\Program Files\Malwarebytes Anti-Exploit\MBAE.dll 2013-08-01 19:50:54 - DLL Injection has been successfully started C:\Program Files\Malwarebytes Anti-Exploit\MBAE.dll 2013-08-01 19:52:45 - The Malwarebytes Anti-Exploit task scheduler has been successfully created 2013-08-01 19:
  5. In order to recognize FireFox, I had to stop and start protection for MBAE again.
  6. After stopping and starting protection from the MBAE GUI (General Tab), Internet Explorer is now protected. However, Shielded applications remains 0.
  7. Sorry, the topic should be : "MBAE still not recognizing IE 10 with new version WSA" Shielded applications - 0 No log entries.
  8. Running version 0.9.2.1400 Beta with new version WSA. 2013-08-01 19:50:54 - The Malwarebytes Anti-Exploit task scheduler has been successfully created 2013-08-01 19:50:54 - Malwarebytes Anti-Exploit Driver Installed successfuly 2013-08-01 19:50:54 - Malwarebytes Anti-Exploit Driver is running 2013-08-01 19:50:54 - Starting Injection with: C:\Program Files\Malwarebytes Anti-Exploit\MBAE.dll 2013-08-01 19:50:54 - DLL Injection has been successfully started C:\Program Files\Malwarebytes Anti-Exploit\MBAE.dll 2013-08-01 19:52:45 - The Malwarebytes Anti-Exploit task scheduler has been successfu
  9. pBust, You are correct. WSA is interfering with ExploitShield. It affects it during installation as well as after installation. I disabled WSA during ES installation and fired up IE 10. ES appeared in the log tab and shielded application = 2. I then enabled WSA and fired up Firefox. Firefox did not appear in the log tab of ES and shielded applications reverted back to 0. Exlie360, My shields tab looks exactly like yours with padlocks locked. The problem is with 'shielded applications' on the general tab and log tab entries.
  10. I reinstalled after removing and deleting directory. Only stop protection button is enabled. Buttons seem to be working fine. Same problems with shielded applications = 0 and no log entries in log tab. mbae-default text file: 2013-06-22 00:05:59 - The Malwarebytes Anti-Exploit task scheduler has been successfully created 2013-06-22 00:05:59 - Malwarebytes Anti-Exploit Driver Installed successfuly 2013-06-22 00:05:59 - Malwarebytes Anti-Exploit Driver is running 2013-06-22 00:05:59 - Starting Injection with: C:\Program Files\Malwarebytes Anti-Exploit\MBAE.dll 2013-06-22 00:05:59 - DLL Injecti
  11. Fired up IE 10 and FireFox. Shield applications remains 0, with no log messages. Windows 7 32 bit, WSA 8.0.2.155, Admuncher.
  12. My problem with IE10 was with 32 bit. I hope that is corrected as well.
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.