vincent

Thanks for the suggestion pbust, as I mentioned earlier I had fixed this by adding exceptions for both the folder and the process in Bitdefender. For a few days I had no issues, but then yesterday I installed the new Windows 10 updates: http://www.ghacks.net/2015/08/27/microsoft-releases-windows-10-patches-kb3081452-kb3081448-and-kb3081449/ And rebooted into the same 0135 error when opening cmd/iexplore. Interestingly enough the trick that jord mentioned works, but he's wrong about something, SysWow64 is the 32-bit folder (I know, confusing right? But hey that's Microsoft) so I think you're definitely right that there's some kind of hooking conflict going on with the 64-bit part of Windows, MABE and Bitdefender. I then followed your uninstall/reinstall steps and it works fine again, it's really weird but I guess I'll just be wary of Windows updates from now on, seems like they reset something? In your tests, do you have UAC activated? That might be something to look into as well, I personally have UAC on. Also, I noticed something interesting in the mbae-service.log: "2015-08-28T16:14:46.612-05:00";"SYSTEM";"1";"1.07.1.1015";"";"" "2015-08-28T16:46:05.798-05:00";"SYSTEM";"1";"1.07.1.1015";"";"" "2015-08-29T11:49:34.192-05:00";"SYSTEM";"1";"1.07.1.1015";"";"" "2015-08-30T10:39:11.130-05:00";"SYSTEM";"1";"1.07.1.1015";"";"" "2015-08-30T13:34:48.267-05:00";"SYSTEM";"1";"1.07.1.1015";"";"" "2015-08-30T13:35:32.671-05:00";"vincent";"2";"1.07.1.1015";"";"" "2015-08-30T13:43:24.942-05:00";"vincent";"1";"1.07.1.1015";"";"" "2015-08-30T13:43:30.897-05:00";"vincent";"2";"1.07.1.1015";"";"" I'm guessing the service should run under SYSTEM and I checked whether this was the case in services.msc but I wonder why my username instead comes up in this log file the day I installed the new Windows Updates. Again reinstallation fixed it.

Thanks for your reply pbust. I have to also add 'iexplore.exe' to the list, as I just noticed the exact same error message behaviour. Here's what I've done: So I tried disabling Bitdefender's 'Active Virus Control' (while keeping 'on-access scanning' activated) and keeping MBAE also actived. I then get this error instead: ---------------------------cmd.exe - Application Error---------------------------The application was unable to start correctly (0xc0000018). Click OK to close the application.---------------------------OK --------------------------- If Active Virus Control is working I get the 135 error. Clearly Bitdefender's AV is somehow interfering with MBAE to some extent. Using 'exclusions' in Bitdefender doesn't help either, you have to turn off the protection mechanisms completely. So that's kinda bad.. I'd rather not have to switch my Anti Virus unless you can recommend one that'll work with MBAE and overall has good detection rates etc. In any case, I then proceeded to follow the reboot/reinstall steps and after just the first reboot it seems fixed? I can open iexplore.exe and cmd.exe again, really weird. I did make exclusions in Bitdefender prior to this, so maybe that helped after the reboot as well.. I'll definitely test it out for a little while before I upgrade to the Premium version. Are they the same when it comes down to the core application? Obviously Premium offers more features, but can I be sure that if I don't have issues on the Free that I can upgrade without any core issues like this one for example? Thank you again and I hope this helps someone else if they've had the same errors.

Hello, so I heard about Anti Exploit and tried it today to see if I'd like to upgrade to premium. However with this free installation I've noticed something that definitely breaks my setup as I use cmd/powershell a lot. So far this is the only application that I've noticed that is affected. Steps to reproduce this is just starting cmd, either through 'run' or any other way (through powershell works too). You end up with this message: ---------------------------cmd.exe - Application Error---------------------------The application was unable to start correctly (0xc0000135). Click OK to close the application.---------------------------OK --------------------------- I tried changing settings in Anti Exploit but nothing worked. The only way to get cmd.exe working again is STOPPING PROTECTION entirely. I tested this on 2 Windows 10 computers, both experience this issue. Am I the only one? Windows 10 x64 MBAE version: 1.07.1.1015 I also use Bitdefender AV only