IsoQuantic

Looks like my last fix above has worked. Although I now have this odd problem that when I create a new folder I cannot change the name of the folder with the error message that the folder does not exist. I can only rename the New Folder using a command prompt and ren oldname newname Not sure this is related to the fix, but wanted to note it in case anyone else has the same problem.

Used the batch file for removing all traces of MWB AE and reinstalled it anew. So far it is working. Stay tuned.

Do the MWB folks monitor these forums actively? I have not got a response from a submitted support request for the issue as well.

I spoke too soon. The above fix lasted for one day then the problem re-appeared. The MWB Anti-Exploit service stops and refuses to be restarted.

Very disappointed that a request submitted to support about this issue over a week ago has yet to be responded to. No matter, I sorted this all out by myself. Uninstall MWB Ani-Exploit. Use a tool like Registry First Aid and search for and delete all registry entries containing the "Anti-Exploit" string. Delete left over start menu program folders for the program that were not removed by the uninstaller. Download the trial version of MWB AE from the MWB site. Install and enter ID and license strings. Problem solved. Really sad to see how customer-centric claims made at the MWB site are apparently but marketing hype.

Bumping this for consideration.

I have the same issue. Thinking there was some licensing issue, I purchased a new Anti Exploit license (I had just purchased a license on July 14) today and uninstalled the current Anti Exploit program. Rebooted and deleted the Anti Exploit folder in the Programs Data folder. Installed the new downloaded version. Rebooted. It worked for a few minutes then the service stopped and attempts to restart it fail. Hate that I spent an additional $40 for another license I did not need. This did not start happening until a few days after the Windows 1607 version was installed. The only new thing I had done was enable self-protection and self protection early start for MWB. Disabled these settings and the problem still exists.