OK, not a solution you were looking for but totally working workaround, even with some benefits.
You can use the dev vm's VHDX file in native boot, dual boot your real physical hardware to it instead of using it as a vm. See this tutorial for really fast and easy setup: Hyper-V - Native Boot VHD - Windows 10 Forums
Dual booting, using the virtual hard disk in native boot allows it to use your native hardware directly. You will have full access to your host drives, and it functions faster than a vm.
If you decide to give it a go, please notice the following:
- Be sure to install Macrium as told in tutorial step 1.3, and setup Macrium boot entry as told in steps 2.7 to 2.9, to be able to reset the boot records if something goes unexpected (steps 4.1 through 4.3)
- Although the VHDX file is seen by host as just over 40 GB, it is in fact a dynamically expanding 127 GB virtual hard disk. This means that the drive where it is stored when mounted and added to native boot must have at least 128 GB free space; if selected from boot menu when the storage location has not enough space for the VHDX to expand to its full size, you will get a BSOD
- When used in native boot, the pre-installed Windows dev environment VHDX tells you that the Windows license is expired. Simply open an elevated command prompt and give this command to get trial license rearmed / activated:
I was sure this works but wanted to test it before posting. Please take the suggestion about setting up Macrium recovery environment seriously! This quote from the end of the mentioned tutorial:
One third joking, two thirds seriously:
If something happens when you are playing with native boot and you come back posting "Help! I can't boot to Windows anymore!", my only advice will be to boot to Macrium rescue system as told in the tutorial and reset boot records. It works every time being a life saver when PC can't boot to any operating system.
In case you will then reply with "It's not there, I forgot to add Macrium to boot menu!", I don't even bother to respond!
I will continue searching for possible reasons for your remote connections failing when remote host plays audio.