windows 10 Creator update now MBAE won't start

[Fedup]

I have just updated windows 10 to version 1703 Creator. Since then every time the PC starts up, after about 6 minutes I get a message stating Malwarebytes Anti-Exploit is taking to long to start and telling me to restart the PC. I also get this message if I try and open MBAE manually. The program version is 1.9.1.1403

Edited July 14, 2017 by Fedup

[Rsullinger]

Hello Fedup,

 

Do you mind collecting the logs from this forum post for me:

 

Thank you,

[Fedup]

Hope this ok   last update 11-May-17 version 1.9.1.1403

Malwarebytes Anti-Exploit.zip

[Rsullinger]

Hey Fedup,

 

Sorry for the delay. I was getting the logs looked at. It looks like one of the service is not launching correctly. This may have something to do with the creator update interfering with it but I cannot be sure 100%. It may be best, in this case, to re-install the latest version as that will re-install the service and driver so the product can run correctly again. 

[Fedup]

I have re-installed MBAE and all is running now. thanks for the replys 

[ajwh]

Dear Staff, could please give some more details about the archive file here and how to proceed with it. Maybe its helpful? Thanks!

[Fedup]

I have just updated windows 10 to version 1703 Creatoron 13/07. Since then every time the PC starts up, after about 6 minutes I get a message stating Malwarebytes Anti-Exploit is taking to long to start and telling me to restart the PC. I also get this message if I try and open MBAE manually. The program version was 1.9.1.1403

I re-installed  MBAE on the 18/07 to v 1.9.1.1403 and it worked ok until this morning 22/07 and the PC starts up, after about 6 minutes I get a message stating Malwarebytes Anti-Exploit is taking to long to start and telling me to restart the PC. I also get this message if I try and open MBAE manually. 

Is v 1.9.1.1403 the latest version???

 

[Fedup]

Just another thought how can I check if MBAE is running ? and is there any problems of contention between MBAE and any other programs. 

[Rsullinger]

Hey Fedup,

 

There is a couple of ways. First way is to check the tray in the bottom right to see if you see the orange shield.  You can also open the up the services menu by pressing windows +R on the keyboard and typing in services.msc. You can then scroll through the list and see if malwarebytes anti-exploit service is started. 

As for the build, there is a newer version then that so it could be having update issues. You can find the build here ( i would recommend un-installing, rebooting, and installing it):

https://malwarebytes.box.com/s/9v3b9lw11xk3ghh5hsa1gacnaqhpohro

 

[Fedup]

Hi

No shield shown in the tray. Went to services MBaeSvc  was blank so I restarted it to running. Strange that sometimes it shows as MBaeSvc and others as Malwarebytes-Anti-Exploit Service.  The shield is now showing and when I click on it states it is running. I taken a screen shot of the log and there is nothing from the 20/07/2017 until I set it running this morning. I have not download the new version yet just to see want happens.

[Rsullinger]

Hey Fedup,

 

The actual service name is MbaeSvc like you were seeing, but the display name is Malwarebytes anti-exploit service. So seeing either is generally fine. Generally you should see mbaesvc in the services menu of task manager and you should only see the display name in the actual services menu. Let me know if after a reboot that happens again. The service should start every time the computer is started so if it is not, we can look into that. 

[Fedup]

Hi

MBAE started ok when I started the PC . Don't know how it was not running in services. Thank you for the input.

[Fedup]

Ok it worked for a day.

When the pc started this morning 27/7/2017  I got an error " The code execution cannot proceed because mbae-api.dll was not found. Reinstalling the program may fix the problem."

Looked in services.msc and it was not started so I started it and got an error "Windows could not start the Malwarebytes-Anti-Exploit services on local Computer. error 1053. The service did not respond to the Start or Control request in a timely fashion".

 

Looked at my programs and it was updated to v.1.10.1.24 26/7/2017 old won v 1.9.1.1403

Is this the new version No v.1.10.1.24

 

 

[Fedup]

Just found this in mbae-uninstall.log - Notepad

I did not install so was it the update

2017/07/26 - 19:38:41 - 141 - {Info} Parameter: /install
2017/07/26 - 19:38:41 - 203 - {Info} Getting current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\}.
2017/07/26 - 19:38:41 - 232 - {Info} The file {mbae-svc.exe} has been added to current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe}.
2017/07/26 - 19:38:41 - 203 - {Info} Getting current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\}.
2017/07/26 - 19:38:41 - 232 - {Info} The file {mbae-svc.exe} has been added to current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe}.
2017/07/26 - 19:39:02 - 797 - {Info} The command {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe -remove} has been executed. 213
2017/07/26 - 19:39:02 - 450 - {Info} UnInstallPreviousMbae - ManageMbaeService. Result: {213}.
2017/07/26 - 19:39:02 - 334 - {Info} Setting path in registry: 0.
2017/07/26 - 19:39:02 - 203 - {Info} Getting current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\}.
2017/07/26 - 19:39:02 - 703 - {ERROR} The file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae.dll} could not be deleted. 5.
2017/07/26 - 19:39:02 - 711 - {ERROR} The file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\tmp\mbae.dll} could not be moved to file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae.dll}. 5.
2017/07/26 - 19:39:02 - 736 - {Info} The file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\tmp\mbae.dll} has been marked to move to (C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae.dll).
2017/07/26 - 19:39:02 - 711 - {ERROR} The file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\tmp\mbae.exe} could not be moved to file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae.exe}. 5.
2017/07/26 - 19:39:02 - 736 - {Info} The file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\tmp\mbae.exe} has been marked to move to (C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae.exe).
2017/07/26 - 19:39:02 - 711 - {ERROR} The file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\tmp\mbae-svc.exe} could not be moved to file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe}. 5.
2017/07/26 - 19:39:02 - 736 - {Info} The file {C:\Program Files (x86)\Malwarebytes Anti-Exploit\tmp\mbae-svc.exe} has been marked to move to (C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe).
2017/07/26 - 19:39:02 - 477 - {ERROR} UpdateMbaeFiles: 5.
2017/07/26 - 19:39:02 - 203 - {Info} Getting current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\}.
2017/07/26 - 19:39:02 - 232 - {Info} The file {mbae-svc.exe} has been added to current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe}.
2017/07/26 - 19:39:02 - 203 - {Info} Getting current working directory. Result: {C:\Program Files (x86)\Malwarebytes Anti-Exploit\}.
2017/07/26 - 19:39:03 - 797 - {Info} The command {C:\Program Files (x86)\Malwarebytes Anti-Exploit\tmp\mbae-svc.exe -onlyinstall} has been executed. 0
2017/07/26 - 19:39:03 - 483 - {Info} InstallMbae: 0 - -onlyinstall.
 

 

[Rsullinger]

Hey Fedup,

 

That is correct, we just released our 1.10 version through automatic update and it looks like it couldn't remove the files so they were set to be removed. So it looks like a lot of the issues you are seeing is due to the automatic update. 

 

Can you go to the C:\Program Files (x86)\Malwarebytes Anti-Exploit\ and take a screenshot of that directory. If that tmp folder exists, can you take a screenshot of what is in that directory as well? A simple re-install with 1.10 would fix this issue, but I want to confirm what is not being moved over correctly. A reboot should have swapped those files that are having the error in the log. 

[Fedup]

OK, a copy of what's in the x86 program files. 

The tmp folder is empty.

 

[Fedup]

Better show the rest

[Rsullinger]

Hey Fedup,

 

It looks like those are good. I tried doing a test on my side to see if I could reproduce the issue but it doesn't seem like I could. This may be the similar issue you were seeing with 1.09 in that something is preventing your AE from updating properly. Have you re-installed the client since taking these screenshots? 

[Fedup]

no I will try to re-install later

[Fedup]

Where do I download the last version 1.10 as I cannot find the update.

[Rsullinger]

Hey Fedup,

That was dumb of me, I should have provided you a link at least:

 

http://downloads.malwarebytes.com/file/mbae

 

That link will have the latest version of mbae that you can download. Let me know how it goes! 

[Fedup]

Thank you . Up and running