Jump to content
John A

CMD.EXE App error has returned

Recommended Posts

I installed 1.08.1.1031 a couple of days ago on Windows 10 and the first thing I checked was cmd.exe - it worked OK then.

 

But on restart, the old error is back and I have to Stop MBAE protection in order to get cmd to work.

 

post-14642-0-08134800-1444508404_thumb.j

 

Share this post


Link to post
Share on other sites

I corrected it by using the procedure advised previously, but this issue needs to be fixed.

 

Uninstalled MBAE

Restarted

Installed MBAE

Share this post


Link to post
Share on other sites

I've got the same problem.  After installing MBAE, I get the following error when trying to start cmd.exe

The application was unable to start correctly (0xc000018). Click OK to close the application.
If I stop MBAE, then cmd.exe works ok.  If I restart MBAE, I get the above error when I try to restart cmd.exe
I'll try the above suggestion of uninstalling, restarting and re-installing.  I'm running Windows 10 on an Asus laptop.

Share this post


Link to post
Share on other sites

I tried uninstalling MBAE using the uninstall tool on the MB website.  The uninstall tool ran and then requested a restart.  After the restart MBAE was still there but at least cmd.exe is working again with MBAE running.

Share this post


Link to post
Share on other sites

Hi:

 

I tried uninstalling MBAE using the uninstall tool on the MB website.  The uninstall tool ran and then requested a restart.

 

Just curious: what "uninstall tool" did you use?  Do you have a link to that?

 

I did not know about an uninstall/removal tool for MBAE (Malwarebytes Anti-Exploit).

There *is* a removal tool for MBAM (Malwarebytes Anti-Malware).  It is called mbam-clean. But AFAIK, it will not remove MBAE, as it is only designed to remove MBAM.

 

Or did I miss something? :unsure:

 

Thanks,

Share this post


Link to post
Share on other sites

I just uninstalled from Control Panel - then all the settings were kept and CMD now works.

 

I have tried unsuccessfully to reproduce this by reinstalling the production version, restarting, installing the latest Beta, restarting.

 

This issue initially seemed to occur only on versions of Windows 10 that were upgraded from 7/8 with MBAE installed.

 

I thought that once the error was cleared it wouldn't occur again, so I was surprised to see it after installation of the new Beta.. 

Share this post


Link to post
Share on other sites

Hi:

 

 

Just curious: what "uninstall tool" did you use?  Do you have a link to that?

 

I did not know about an uninstall/removal tool for MBAE (Malwarebytes Anti-Exploit).

There *is* a removal tool for MBAM (Malwarebytes Anti-Malware).  It is called mbam-clean. But AFAIK, it will not remove MBAE, as it is only designed to remove MBAM.

 

Or did I miss something? :unsure:

 

Thanks,

 

Hmmm, well noticed - I missed that.  I have the same curious question.  It seems that "New member" removed MBAM, not MBAE.  If so, does that broaden the focus of this issue? 

 

It appears that "New member" needs to reinstall Malwarebytes Antimalware

Share this post


Link to post
Share on other sites

I did use the mbam-clean tool instead of the method described at https://support.malwarebytes.org/customer/portal/articles/1833611-how-do-i-uninstall-malwarebytes-anti-exploit-?b_id=6440 that I should have.  It's interesting that even though I used the wrong tool, it did seem to fix the problem for now.  I did upgrade to Windows 10 from Windows 8 but didn't have MBAE running on Windows 8.  It was a new install that I just did a few days ago and I did the Windows 10 upgrade several months ago.

Share this post


Link to post
Share on other sites

I think you have inadvertently supplied some very useful information.  It will be interesting to see what Pedro thinks is going on.

Share this post


Link to post
Share on other sites

No issues here in WIn 10 (upgraded from win 8 and not felt need for clean install, so far)..

 

CMD.exe works fine.. Keep RAM usage around 50-60%..

Share this post


Link to post
Share on other sites

It's interesting that not all Windows 10 installations are being affected.  I checked my RAM usage and MBAE is showing as:

.. Services .. 1.6 MB and .. 64bit .. 0.4 MB.   cmd.exe uses only 0.6 MB.  Total RAM usage is 55% so this doesn't seem to be the problem here.  MBAE and cmd.exe are still running ok today.  I'm using v. 1.07.1.1015 of MBAE.

Share this post


Link to post
Share on other sites

We tried to replicate this problem but could not after much trying. We will continue trying.

Share this post


Link to post
Share on other sites

Btw are you all running 32 or 64bit Windows 10?

 

Also please post your MBAE logs.

 

Thanks!

Share this post


Link to post
Share on other sites

How are you running CMD.EXE when the error occurs? Is it as admin or as your regular user account? Is your user account limited or admin?

Share this post


Link to post
Share on other sites

I'm running 64bit Windows 10.  My MBAE logs are empty.  I just installed MBAE a few days ago and it says the number of blocked exploit attempts is 0.  As I mentioned above, since I ran mbam-clean, I've been able to run cmd.exe with MBAE active without any problems.  I run cmd.exe by starting to enter cm... in the Search the web and Windows box in Windows 10.  When the Command Prompt pops up at the top of the list, I click on it.  I've been running it with my regular admin level account.

Share this post


Link to post
Share on other sites

Hi Cajon, please post your MBAE logs. You can find instructions in the "readme first" link in my signature.

 

Thanks!

Share this post


Link to post
Share on other sites

 

Btw are you all running 32 or 64bit Windows 10?

 

Also please post your MBAE logs.

 

Thanks!

 

64 bit here

Share this post


Link to post
Share on other sites

How are you running CMD.EXE when the error occurs? Is it as admin or as your regular user account? Is your user account limited or admin?

All my accounts are admin.  This event occurred when using my local account

Share this post


Link to post
Share on other sites

@cajon & @John A, please do the following test:

 

1- Stop the MBAE service

2- Delete the files inside the C:\ProgramData\Malwarebytes Anti-Exploit\ directory (not the directory itself)

3- Extract the file inside the attached RAR to the above directory.

4- Start the MBAE service and run the MBAE.EXE program from C:\Program Files (x86)\Malwarebytes Anti-Exploit

5- Test to see if the problem reproduces.

6- Have Process Explorer ready (open/minimized). If/when the error occurs again, open Process Explorer, right-click on cmd.exe and choose Create Dump -> Create Full Dump.

7- Compress the dump and upload it here or send it to me via PM.

 

Thanks!

 

mbae-config.rar

Share this post


Link to post
Share on other sites

Unfortunately this procedure didn't bring up the error

Share this post


Link to post
Share on other sites

OK let's do this then (restoring to original mbae-config file):

 

1- Stop the MBAE service

2- Delete the files inside the C:\ProgramData\Malwarebytes Anti-Exploit\ directory (not the directory itself)

3- Start the MBAE service and run the MBAE.EXE program from C:\Program Files (x86)\Malwarebytes Anti-Exploit

4- Test to see if the problem reproduces.

5- Have Process Explorer ready (open/minimized). If/when the error occurs again, open Process Explorer, right-click on cmd.exe and choose Create Dump -> Create Full Dump.

6- Compress the dump and upload it here or send it to me via PM.

Share this post


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.

×
×
  • 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.