Thanks for your reply Tim. Here is my detailed information for your advise, I have interface physical PC which that run an interface application to 'talk' 2 ways between appA and appB via serial cable, so now I have converted this interface physical PC to VM and it is up and running well but my interface application is not connected.
![Windows Windows](/uploads/1/2/5/5/125513034/616049550.png)
I have checked by connected a serial cable to my hyper-V manager host's COM port and using PuTTY by telnet serial (COM1) to a managed switch and it is connected okay. Then I try do a same with my VM (interface VM mentioned above) but cannot connect to my switch (here is just a testing of COM port case then I can test with my interface app as well) I am trying to search your instruction: ' Hyper-V uses the COM port to establish a named pipe to another program'. Here is an explanation of a named pipe - In order to use it, you would need to develop a program that communicates across that interface. Shows how to use a serial port for debugging purposes. Maybe you could use that as an example to accomplish your goal. There are third party devices that give your VMs access to serial devices. These generally are network devices that present the serial device to the VM via a network protocol.
Mar 9, 2018 - Proxmox Serial Port Pass Through Windows Sliding. We cannot afford to buy the latest and greatest CPUs and systems just to run a home.
![Proxmox Serial Port Pass Through Windows For Sale Proxmox Serial Port Pass Through Windows For Sale](/uploads/1/2/5/5/125513034/491014246.png)
Note that the above products are not Microsoft products and are not recommended or supported by Microsoft. Your support would come from the third party providing the product. Or, you can upgrade to the latest version of Hyper-V.
Hyper-V 2016 added a feature called discrete device assignment. See for more information.