Jump to content

iFlame

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by iFlame

  1. Thanks for the logs iFlame. Have you tried to see if a fresh re-install fixes it? This happens sometimes under Windows 10 due to a new behavior of Windows 10 which we're still investigating.

     

    https://forums.malwarebytes.org/index.php?/topic/171634-anti-exploit-not-started-under-windows-10/

     

    No problem, I just reinstalled, so far I don't face any issues, but rebooting has always fixed the cmd error temporarly, so I will report back should it occur again.

  2. On initial check could not replicate. We'll continue trying.

     

    Can you attach or PM me an FRST log to try to simulate your environment as much as possible?

     

    Thanks!

     

    Sorry to have bothered you with this report, probably is not caused by MBAE. ESETs HTTPS scanner causes issues even without MBAE installed, but since disabling MBAE fixed the cmd.exe error described in the other thread, I assumed that it also caused the HTTPS errors. I disabled ESETs HTTPS scanner for now, seems to fix the problems. Will report back if there should be crashes as described by another ESET user on this thread.

  3. Hello,

    having the 0x18 cmd problem too, running Windows 10 x64. Initially I suspected it was a problem with ESET conflicting with MBAE, but it turned out the problem persists after uinstalling ESET. I'm not 100% sure, but I do think that I did not upgrade my windows but installed fresh Windows 10 a few months ago. Also Edge is closing itself on start when MBAE activated. Experienced the same issues on another notebook (which still has ESET installed and was upgraded from Windows 8) but with completely different hardware. I'm also running MBAM Premium.

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.