To restore sound in Windows Remote Desktop Connection on Windows 10 or Windows 11, open Show Options > Local Resources > Remote audio > Settings, select Play on this computer, and reconnect. If you also need your local microphone inside the remote session, select Record from this computer separately. These instructions cover the built-in Remote Desktop Connection client, not Windows App or browser-based remote desktops. Lenovo documents the playback procedure for both Windows versions, and Microsoft documents the recording setting.

A desktop setup illustrates secure cloud connectivity between computers, headphones, a microphone, and audio settings. Identify which computer needs attention​

Use these names throughout the guide:

Quick walkthrough

56ca0473e513-exact.webp
  • Local computer: The PC in front of you, with the speakers, headphones, or microphone you want to use.
  • Remote computer: The PC whose desktop you access through Remote Desktop.
  • Playback redirection: Sound from the remote session plays through your local computer.
  • Recording redirection: Your local microphone becomes available to applications in the remote session. Microsoft treats playback and recording as separate RDP settings.

This guide assumes you can already connect and sign in. Windows Home can be the connecting computer, but it cannot act as the built-in Remote Desktop host. Microsoft’s consumer setup instructions specify Windows Pro for the remote PC. Windows 10’s free support ended on October 14, 2025; applicability of these troubleshooting steps does not mean every Windows 10 installation remains supported.

Start with the client settings and a simple playback test. Reserve policy and service changes for cases where those checks fail. Have an administrator handle managed computers, and record existing settings before changing them.

1. Confirm that local sound works​

Before adjusting Remote Desktop, test the speakers or headset on the local computer.

  • Minimize the remote desktop window.
  • Play a known-working audio file locally.
  • Check the headset’s physical mute and volume controls.
  • Open Start > Settings > System > Sound and check that the intended output device is selected.
  • If local playback is silent too, fix that problem before continuing. Check the output selection, connections, and volume rather than changing remote-session policies. Microsoft’s audio troubleshooting guidance starts with these checks.

For microphone problems, establish the same local baseline:

  • Connect and unmute the microphone.
  • Open Settings > System > Sound.
  • Under Input, select the microphone you intend to use.
  • Test it:
  • Windows 11: Open the microphone’s properties and use Start test.
  • Windows 10: Speak and watch the indicator under Test your microphone.

Do not continue with recording-redirection troubleshooting until Windows can detect speech locally.

2. Enable playback and recording in Remote Desktop Connection​

Make these changes on the local computer, before connecting.

  • Close the existing remote connection window.
  • Open Start, search for Remote Desktop Connection, and launch it.
  • Select Show Options if the tabs are hidden.
  • Open Local Resources.
  • Under Remote audio, select Settings.
  • Under Remote audio playback, select Play on this computer.

The other choices serve different purposes:

  • Play on remote computer leaves playback at the remote machine.
  • Do not play disables playback for the connection.

For sound through the speakers or headset in front of you, use Play on this computer.

Privacy warning: Enable microphone redirection only when you need it and trust the remote computer. It makes local audio capture available to the remote session.

  • Under Remote audio recording, choose:
  • Record from this computer to use your local microphone remotely.
  • Do not record if you only need playback.
  • Select OK.
  • Return to General, confirm the destination, and select Connect.
  • Sign in and retest.

Microsoft documents recording as a separate client option; enabling playback alone is not the microphone fix. To undo microphone sharing, return to this dialog, choose Do not record, and reconnect.

3. Verify playback and recording separately​

For the first playback test, use a known-working audio file in an application inside the remote session. Avoid using a Teams call or a multimedia-redirected webpage as the only test: Microsoft specifically excludes those from its basic audio-redirection verification because they can use a different media path.

Check each direction independently:

  • Playback: Start the remote audio file. Confirm that you hear it through the local speakers or headphones.
  • Recording: If you enabled microphone redirection, open a recording application inside the remote session, record a short sentence, and play it back.
  • Application selection: If one application fails while another works, inspect the failing application’s selected speaker or microphone rather than immediately changing system policies.

Successful playback does not prove recording works, or vice versa: RDP controls them independently. A remote recording test is Microsoft’s recommended way to verify redirected microphone input.

Check volume on both sides​

If playback remains silent, inspect the local Remote Desktop client’s volume and the remote application’s volume.

  • Windows 11: Open Settings > System > Sound > Volume mixer. Under Apps, check the relevant application’s volume and output device.
  • Windows 10: Right-click the taskbar Volume icon and select Open Volume mixer. Check that the relevant application is not muted.

Perform the check locally for the connecting application and inside the session for the application producing sound. Microsoft notes that application volume and output-device choices can differ from the system default.

4. Check microphone permissions if playback works but recording does not​

Windows 11 Settings on the Privacy & security > Microphone page with the microphone access toggle and the per-app 'Let apps access your microphone' list

Do this only for missing microphone input. Microphone privacy settings are not a remedy for missing speaker output.

Privacy warning: Desktop microphone access can affect more than one application. Note the original settings and enable only the access needed for your task; restore them afterward if you enabled access temporarily.

Windows 11​

  • On the local computer, open Settings > Privacy & security > Microphone.
  • Confirm Microphone access is on.
  • Check Let apps access your microphone for applications that need it.
  • Check Let desktop apps access your microphone for desktop applications.
  • Inside the remote session, inspect the same page if the remote recording application is blocked.

Windows 10​

  • Open Settings > Privacy > Microphone.
  • Under Allow access to the microphone on this device, use Change if needed and enable access.
  • Check Allow apps to access your microphone.
  • Check Allow desktop apps to access your microphone.
  • Inspect the remote computer’s permissions too if the recording application cannot capture audio.

Microsoft documents these version-specific paths and distinguishes application access from desktop-application access. After correcting permissions, reopen the recording application and repeat the short recording test.

5. Check remote-session audio policies​

The Local Group Policy Editor with the Computer Configuration and User Configuration trees.

If client settings are correct but redirection still fails, an administrator should inspect policy on the remote computer. A client preference cannot override a host policy that blocks redirection. Microsoft documents this as a most-restrictive-setting relationship.

Before changing policy: Obtain approval on work or school systems. Record whether each setting is Enabled, Disabled, or Not Configured. Allowing recording expands access to local microphones; do not enable it merely to troubleshoot playback.

  • On the remote PC, open Start, search for Edit group policy, and open it.
  • Navigate to:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection

  • Open Allow audio and video playback redirection.
  • If playback should be permitted, set it to Enabled, then select OK.
  • If microphone input is needed, open Allow audio recording redirection, set it to Enabled, and select OK.

A Disabled setting blocks the corresponding redirection. Not Configured means that setting does not specify a restriction at that Group Policy level; it is not evidence that no other management layer applies. Microsoft documents both policy names and their behavior.

For domain-managed computers, the administrator should modify the policy targeting the host rather than relying on a local edit. In Group Policy Management, the equivalent path includes Computer Configuration > Policies > Administrative Templates. Microsoft’s configuration procedure calls for applying the policy and restarting the host before testing. Save work, arrange an appropriate restart window, and confirm you can reconnect before proceeding.

Rollback: Restore each policy’s recorded original value, apply the policy, and restart again. Restore Not Configured where that was the original state rather than leaving a troubleshooting override behind.

If this is Azure Virtual Desktop, ask the administrator to inspect the host pool’s RDP Properties > Device redirection settings as well. Host settings and connection properties must both permit the requested direction.

6. Inspect Windows audio services​

Use this check when client configuration and policy have not restored sound.

Warning: Restarting audio services interrupts playback and recording on the affected computer. Stop calls and recordings first. On a shared host, coordinate with its administrator.

  • Begin on the remote computer if local audio already works.
  • Open Start, type services.msc, and press Enter.
  • Locate Windows Audio and Windows Audio Endpoint Builder.
  • Check their status.
  • For a running service, right-click it and select Restart.
  • Reopen the audio application and test again.

Microsoft documents restarting these two services as an audio recovery procedure. Its driver guidance also states that both must run for audio to work correctly. If a service is stopped or cannot restart, record its status and the exact error for the administrator rather than changing its account or permissions.

If local audio also fails, perform the service check locally. Do not change service logon accounts, grant services administrator membership, or edit audio registry entries as part of this procedure.

No configuration rollback is needed for a successful service restart. If it fails, stop and resolve the service error before making further redirection changes.

7. Inspect a saved connection’s audio properties​

Use this alternate check if the problem appears tied to a particular saved .rdp connection. Inspect a copy; leave organization-issued or signed connection files unchanged unless the administrator authorizes an edit.

Microsoft documents these properties for remote PC connections:

Code:
audiomode:i:0
audiocapturemode:i:1

Their meanings are:

PropertyValueMeaning
audiomode0Play sound on the local computer
audiomode1Play sound on the remote computer
audiomode2Do not play sound
audiocapturemode0Disable local audio capture redirection
audiocapturemode1Enable local audio capture redirection

For playback alone, audiomode:i:0 is the relevant setting; microphone capture need not be enabled. These properties express connection preferences, not permission to bypass host policy. Prefer the client dialog for changes, and use the original file to roll back any authorized test edits.

Narrow down a remaining failure​

Use the test results to choose the next action:

  • Local playback fails too: Continue local speaker, output-device, and volume troubleshooting before investigating RDP.
  • Remote playback works, but microphone input fails: Recheck recording redirection, microphone permissions, and the recording policy—not playback settings.
  • One remote application is silent: Check its volume and output device. Working playback in another application points toward application-specific configuration.
  • A basic audio test works, but a meeting application fails: Investigate that application’s audio or media-optimization configuration separately; Microsoft’s basic RDP test deliberately avoids optimized media paths.
  • A host policy blocks redirection: Escalate to the administrator. Changing the client setting cannot override the block.

If the problem remains, provide IT with the local and remote Windows editions and builds, the client name, whether playback or recording fails, the local test results, the remote test application, the relevant policy states, and any service error text. Ask them to verify the effective host policy and reproduce the same simple playback or recording test before making broader system changes.

 

Last edited by a moderator: