Our application uses WCF over named pipes to communicate between two processes (note: neither process is a Windows Service.) Our application has been running in the field w
I have found a method to display which applications use net.pipe(though not necessarily which are using it incorrectly).
First download the Handle application from sysinternals:
https://technet.microsoft.com/en-us/sysinternals/handle.aspx?f=255&MSPPError=-2147217396
Then open a command prompt as administrator, and run "Handle.exe net.pipe" (minus quotes). This will list all applications using net.pipe that are currently running. From there, you can kill or disable one at a time, until your culprit is discovered. I almost never have more than 4-5 processes using it. If you fail to run command prompt as administrator, it may give 0 results.
Below are all the applications I've found that interfere with net.pipe:
Procore Drive (Procore DriveService.exe). Uses net.pipe://+/:
Procore DriveService.exe pid: 4204 type: Section 43C: \BaseNamedObjects\net.pipe:EbmV0LnBpcGU6Ly8rLw==
Keynetix.Cloud.Launcher.Service.exe. Uses net.pipe://+/:
Keynetix.Cloud.Launcher.Service.exe pid: 5524 type: Section 4B8: \BaseNamedObjects\net.pipe:EbmV0LnBpcGU6Ly8rLw==
I support an application that requires net.pipe, so I'll update this list as I find more services that do this.