Windows 10: SECCNH pipe name: \\.\pipe\{68327F92-4C65-4484-860D-DA80B61FCDBA}.SoundResearch_CoCL_0.

Hello, I have a problem when I start my computer, this code appears SECCNH pipe name: \\.\pipe\{68327F92-4C65-4484-860D-DA80B61FCDBA}.SoundResearch_CoCL_0., this code not only opens applications that I don't want there to be, but also when I connect my Bluetooth headphones and for example I open Enlisted it automatically disconnects, what should I do?

:)

 

game crashing, pipe error, multiple applications opening themselves

It seems to pop up when I open and close games, or right now CP2077 is crashing at boot but also other games that aren't on steam do it as well (WoW, etc)

Console opens with "SECCNH pipe name: \\.\pipe\{68327F92-4C65-4484-860D-DA80B61FCDB"

Then a slew of applications open themselves, AMD software, Overwolf, Steam, and file explorer as well as Windows Edge main page (I use chrome as my default).

I already spoke with Windows tech support, they took remote access and made the problem worse. I have googled with no luck as to what's going on.

Please help!

 

Named pipe and Symbolic link to it

That's the situation: I've a program that sends data to a text file (those are just information about lights state of an arcade machine). I need to redirect those informations to a COM port, so I've replaced the txt file with a symbolic link to a pipe. I
don't have access to the source code of this main program. The only way I've found to do that in Windows 10 is creating a symbolic link using pipes like this:

Code:

mklink SymlinkName \\.\pipe\pipename

Then I've create a program that create/reads the pipe and send it to the COM port. It works fine on Windows 10 without any kind of problem and I've worked on that OS for my development.

Today I've tried all this stuff on the arcade machine (windows 7 Ultimate based) but the Symlink doesn't work. For debug purpouse I try to send data to my COM port simpy using command line, for example

Code:

echo foo > COM1 

and this works fine (so the problem is not in the serial line), but if I try to do that throught the Symlink, it sais:

Code:

echo foo > SymlinkThe data present in the reparse point buffer is invalid.

Any suggestion?

 

Error 1450 when writing to Named Pipe

I'm coding a simple server for a C++ client, connected by a named pipe.
Writes and reads on the named pipe work fine when both ends are on the same machine.
When on two machines on a local network, the very first write on the pipe (about 60 bytes) causes a 1450 - insufficient resources error.
Both machines have lots of RAM, both are Win10 Pro, both were just rebooted.
The pipe connects every time, and the Read/Write handle appears valid.
I've tried creating the pipe with small and large buffers and always get the 1450 error when on two machines, but no error when on one machine.
I've tried the registry adjustments mentioned in a number of articles. Didn't help.
Any advice would be greatly appreciated. Thanks.