Windows 10: No audio input picked up in RDP session (win10)

Hello,


My PC's audio input is not being picked up by the remote machine. Checked the usual suspects i.e. connection settings, group policy, fDisableAudioCapture, remote desktop services (like port redirection). All seems to be as you'd expect and the remote audio device input is visible in 'Sounds' panel, however it's not actually picking up any input from my microphone (local audio recording works fine). Both machines are running win10 pro 1803, not experiencing any other issues.

Would welcome help with this issue as I'm a bit stuck troubleshooting.


Cheers!

:)

 

Server 2016 Essentials RDP session - no keyboard or mouse

After installing the latest build 14393.rs1_release_inmarket.161014-1755 I'm having this problem.

When reconnecting to a previously disconnected but running desktop session, after authentication I receive a black screen and shortly thereafter the session quits with the following error:

"Failed to reconnect to your remote session.

Please try to connect again."

This behavior is the same with MS RDP client in both Windows 10 and Android MS RDP client version 4.2.

If I connect from Linux the behavior is slightly different. Here I am able to connect to the session and see the desktop but I'm not able to get a response from keyboard or mouse. It's as if the session is not listening for input. The session remains
alive (animations continue to update e.g. clock) until I disconnect.

So far the only way I'm able to restore normal RDP session behavior is to reboot the server.

 

RDP session

I have a video wall with 10 screens and I am using windows 10 enterprise, I can't span an RDP session to another screen it seems to be locked to the main screen

 

Windows 10 1709; host sleeps during active RDP session

I am reporting a bug/oversight.

HOST OS:

Windows 10 64-bit Version 1709 (OS Build 16299.192)

HOST SETTING:

Set to sleep after 2 hours of inactivity

PROBLEM:

Host computer sleeps after 2 hours of inactivity even when a client is connected via RDP (Remote Desktop)

DESCRIPTION:

In previous versions of Windows and even in Win10 before the Fall Update an active RDP session has always prevented the host computer from entering a sleep state even when set to do so after X minutes of inactivity. Since the Fall Update the host computer
of an active RDP session will sleep during an active RDP session when there is lack of activity on the client computer. There should never be a reason for the host of an active RDP session to enter sleep mode when there is a client connected. If the client
computer is set to sleep after X minutes of inactivity it seems natural it should do so even during an active RDP session, but then, and only then, should the inactivity timer start for the host computer.

HISTORY:

There was a bug introduced in Remote Desktop sometime prior to Win10 Fall Update wherein a host computer would not sleep when set to do so after a period of inactivity after a client had connected and subsequently disconnected to the host via RDP. This
was finally fixed in Fall Update, but I have a sneaking suspicion the fix was too aggressive and this is what led to the problem I am reporting.

Sean