Jump to content

Fedup

Members
  • Content Count

    14
  • Joined

  • Last visited

About Fedup

  • Rank
    New Member
  1. Where do I download the last version 1.10 as I cannot find the update.
  2. OK, a copy of what's in the x86 program files. The tmp folder is empty.
  3. 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.
  4. 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
  5. Hi MBAE started ok when I started the PC . Don't know how it was not running in services. Thank you for the input.
  6. 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.
  7. Just another thought how can I check if MBAE is running ? and is there any problems of contention between MBAE and any other programs.
  8. 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???
  9. I have re-installed MBAE and all is running now. thanks for the replys
  10. Hope this ok last update 11-May-17 version 1.9.1.1403 Malwarebytes Anti-Exploit.zip
  11. 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
×

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.