Scenario #1

In one instance, user has both Cybereason Ransom Free and Malwarebytes applications running in the background. The issue is that one of the applications detected AutoPIPE sending out a request for a license (Access violation - code c0000005)  and flagged it as a malicious application and shuts it down immediately. We are not sure exactly what the security application detected (ex. checked out license if it detects a network call and this is what it is being blocked)

Workaround:

Typically security applications have an option to add certain processes to their safe, ignore, or trusted list so they can work. After IT department at this specific company made some unknow changes to these applications, AutoPIPE was able startup without an issue. 

Otherwise, suspend security application, start AutoPIPE, and then enable the security application again. Your IT department should be able to help with this.  

Scenario #2

In this case, the application could not start because of problems with Malwarebytes Corporate (which is a secondary and not visible AV product).

Workaround:

Again, user's IT department made some unknown changes to the application, and since then AutoPIPE is able to start up with out crashing / freezing.