Jump to content
Due to inclement weather in Southwest Florida, our Clearwater support team is offline. Our other offices are available to assist you, however their responses may be delayed. We appreciate your patience and understanding during this time. ×

MBAE 1.12 Build 37 - issues with Windows XP


Recommended Posts

I use Panda Dome with Windows XP. I use a .bat file which is run from a shortcut in a startup folder. The contents of the file are attached. The problem is that since MBAE was installed, the DOS window that .bat runs in will not close. It did close with MBAE

The job of the .bat file is to delete Panda Dome temporary files from the Temp folder in C:\Windows. This untidy arrangement only applies to Windows XP. In later Windows versions the storage is managed invisibly.

Apart from this annoyance, the new MBAE beta works in Windows XP and Windows 7 without raising any other issues.


Link to post
Share on other sites

  • Staff

Hi hake,

Thanks for reporting this. While we take a look at this, Can you please try out the following:

1. Provide MBAE logs with the version

  • ZIP the entire contents (ALL the files, not just .LOG) of the MBAE user data directory and attach them to your post. The directory is hidden by default so you might have to click on "View -> Hidden items" in Explorer to see it. You can find the logs in the following locations:
    • Windows XP: C:\Documents and Settings\All Users\Application Data\Malwarebytes Anti-Exploit
    • Vista, Windows 7 and Windows 8: C:\ProgramData\Malwarebytes Anti-Exploit
  • ZIP the entire contents of the folder C:\Program Files (x86)\Malwarebytes Anti-Exploit (in case of a 64-bit system) or C:\Program Files\Malwarebytes Anti-Exploit (32-bit system)

2.Uninstall and install again and see if the issue persists or not.


Edited by Arthi
Link to post
Share on other sites

Requested files sent by PM. Frustratingly the issue seems to happen only once or twice after the new MBAE beta has been installed. I will persist with the use of this version and report any further occurences.

I can confirm that on reinstating MBAE after first observing the issue late last week that no further occurence of this issue arises.

Link to post
Share on other sites

Just a final comment on the issue. While MBAE was installed, the issue did not always occur at startup. In the chaos of startup, timing probably matters so the intermittency suggests to me that any interference between two or more processes did not happen at every startup. Before and since MBAE was installed and then uninstalled and replaced by MBAE, the issue with the behaviour of the .bat initiated cmd.exe process did not and does not occur at all.

Link to post
Share on other sites

  • 2 weeks later...

After several false dawns, MBAE has been installed and the Windows XP batch/cmd.exe issue has  been resolved on both affected systems.

Edited by hake
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
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.