At the first moment you might think that the named pipes in Hyper-V are designed to redirect the host’s devices to the guest OS.
But, in reality they are implemented to allow you to redirect the Guest COM ports to the Host.
So for example, If you are interested in allowing a VM to use USB device that is attached to your Host. And you were seeking to do this via Named pipes, I’m sorry to tell you this is not the right way to accomplish what you need. In this case you may find one of my previous blogs is the suitable guide for you: https://amagsmb.wordpress.com/2015/04/18/accessing-usb-devices-in-a-hyper-v-virtual-machine/.
So, let’s define what Named Pipes are (as provided by J.R. Cipriano on https://ciprianoconsulting.wordpress.com/2014/06/03/connect-to-virtual-machine-via-named-pipe)
Named pipe is an option that connects the virtual serial port to a Windows named pipe on the host operating system or another computer on the network.
A named pipe is a portion of memory that can be used by one process to pass information to another process, so that the output for one is the input for another.
The second process can be local or remote.
Additional Information is available at: https://msdn.microsoft.com/en-us/library/aa365590%28VS.85%29.aspx
One common usage of Named Pipes is Kernel Debugging of VM
More details available at: http://blogs.msdn.com/b/ntdebugging/archive/2011/12/30/configuring-a-hyper-v-vm-for-kernel-debugging.aspx
So, do you say that there is no way to use named Pipe from the Host OS to the guest OS?
No, there is a way but requires some efforts to get it work. More info at: http://www.goodjobsucking.com/?p=214
Update: PipeToCom allows you to couple your Hyper-V namedpipe comport to a real one. – https://github.com/albertjan/PipeToCom