Audio in Remote Desktop Sessions: Why Your Microphone Stops Working
A microphone that works perfectly on the local desktop can be invisible the moment the same machine is accessed over Remote Desktop. The reason is that RDP does not pass audio devices through by default, and the ones it does pass behave differently from local devices.
How RDP handles audio
Remote Desktop has two independent audio directions. Audio redirection sends remote system sound to the local speakers. Microphone redirection sends local capture devices into the remote session. They are separate checkboxes, and enabling one does not enable the other.
- Remote audio playback: on by default in most clients
- Microphone redirection: off by default, must be enabled per session
- Virtual audio drivers often do not support redirection at all
Enabling microphone redirection
In the Remote Desktop client, open Show Options, then Local Resources, then Remote audio settings, and set the microphone to follow the session. On the remote side, confirm the redirection device appears under Recording devices.
| Client | Path | Setting |
|---|---|---|
| mstsc | Local Resources > Remote audio > Settings | Record from this computer |
| Windows App | Devices & audio | Microphone: this computer |
| Third-party clients | Varies | Check redirection support first |
Why virtual drivers disappear
Virtual audio drivers install a kernel-mode endpoint on the local machine. RDP redirection enumerates physical capture devices through a different path, so a virtual microphone frequently does not appear in the remote session at all, regardless of the checkbox.
- Physical USB microphone: usually redirects
- Virtual driver endpoint: often does not
- Workaround: run the capture application locally and send the audio over the network
The architecture that avoids the problem
If the goal is to use a phone as a microphone for a remote session, run the phone client on the local machine, capture locally, and forward the audio through the conferencing application rather than through RDP. This removes redirection from the path entirely.
| Approach | Works over RDP | Notes |
|---|---|---|
| Phone mic on remote host | Rarely | Virtual driver is not redirected |
| Phone mic on local host | Yes | Audio travels as application data |
| Hardware mic on local host | Yes | Standard redirection |
Group policy and permissions
In managed environments, microphone redirection can be disabled by policy. If the checkbox is greyed out, the decision was made by an administrator, not by a driver fault. Check the Remote Desktop Services policy for audio and video playback redirection.
- Computer Configuration > Administrative Templates > Remote Desktop Services
- Allow audio and video playback redirection
- Allow audio recording redirection
Diagnosing in five minutes
Confirm the device exists locally, confirm the session has microphone redirection enabled, then check whether the device appears inside the session. If it exists locally and not remotely, it is a redirection limitation. The virtual audio driver setup covers the local driver side, which is worth verifying first because a broken local endpoint fails in both contexts.
Frequently Asked Questions
Does RDP support USB microphone passthrough?
Not natively. Redirection handles standard capture devices; raw USB passthrough needs third-party software.
Why does audio work but the microphone does not?
Playback and capture are separate redirection settings. Enabling playback does not enable the microphone.
Can I use a virtual cable over RDP?
Usually not. Virtual cables are local endpoints and are not enumerated by the redirection layer.
Does the same apply to VDI?
Yes, and VDI platforms often add their own policy layer on top, which is worth checking separately.