{"id":819,"date":"2026-10-12T13:00:00","date_gmt":"2026-10-12T13:00:00","guid":{"rendered":"https:\/\/vpslake.com\/blog\/?p=819"},"modified":"2026-10-12T13:00:00","modified_gmt":"2026-10-12T13:00:00","slug":"enable-audio-windows-server-2022","status":"publish","type":"post","link":"https:\/\/vpslake.com\/blog\/2026\/10\/12\/enable-audio-windows-server-2022\/","title":{"rendered":"How to Enable Audio on Windows Server 2022"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">To enable audio on Windows Server 2022, configure RDP to redirect playback to your computer and make sure the server&#8217;s audio services allow it. The setup takes about five to ten minutes and lets you hear applications running inside the remote session through your local speakers or headphones.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>A VPS running Windows Server 2022 Standard or Datacenter with the latest available updates.<\/li>\n\n\n<li>An active Remote Desktop connection and a local Windows PC with working speakers or headphones.<\/li>\n\n\n<li>A local administrator account on the server, because service and Group Policy changes require elevation.<\/li>\n\n\n<li>No special RAM, disk space, or audio hardware is required on the VPS; playback is redirected through the RDP session.<\/li>\n\n\n<li>If you need a Windows server with administrator access, see <a href=\"https:\/\/vpslake.com\/buy-windows-rdp\">VPSLake Windows RDP hosting<\/a>.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Turn on playback in the RDP client<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The RDP client chooses whether remote sound is sent to your computer, so set this before creating a new session.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On your local Windows computer, press <code>Windows key + R<\/code>, enter the following, and select <strong>OK<\/strong>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mstsc.exe<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In <strong>Remote Desktop Connection<\/strong>, select <strong>Show Options<\/strong>, then open <strong>Local Resources<\/strong>. Under <strong>Remote audio<\/strong>, select <strong>Settings<\/strong> and set <strong>Remote Audio Playback<\/strong> to <strong>Play on this computer<\/strong>. Unless you also need to use your local microphone inside the server, leave <strong>Remote Audio Recording<\/strong> set to <strong>Do not record<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Select <strong>OK<\/strong>, connect to the server, and sign in. If an RDP window is already open, disconnect from it completely rather than merely minimizing it; the audio choice is negotiated when the session starts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Microsoft describes these per-connection controls in its <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/remote\/remote-desktop-services\/remotepc\/remote-pc-connections-faq\/\" target=\"_blank\" rel=\"noopener\">Remote Desktop clients FAQ<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Start the Windows audio services<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Windows Audio and Windows Audio Endpoint Builder must be available before the remote session can expose a playback endpoint.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Inside the server, open <strong>Start<\/strong>, search for PowerShell, right-click it, and choose <strong>Run as administrator<\/strong>. Check both services first:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-Service -Name Audiosrv,AudioEndpointBuilder | Select-Object Name,Status,StartType<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output is similar to this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Name                 Status  StartType\n----                 ------  ---------\nAudiosrv             Running Automatic\nAudioEndpointBuilder Running Automatic<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If either service is stopped or has a different startup mode, run these commands in the same elevated window:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Set-Service -Name AudioEndpointBuilder -StartupType Automatic\nSet-Service -Name Audiosrv -StartupType Automatic\nStart-Service -Name AudioEndpointBuilder\nStart-Service -Name Audiosrv<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The Endpoint Builder should start before Windows Audio. If you prefer the graphical method, press <code>Windows key + R<\/code>, run <code>services.msc<\/code>, and set <strong>Windows Audio Endpoint Builder<\/strong> and <strong>Windows Audio<\/strong> to <strong>Startup type: Automatic<\/strong>. Start a stopped service with <strong>Right-click \u2192 Start<\/strong>, then select <strong>Apply \u2192 OK<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Allow audio redirection in Group Policy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The RDP client setting cannot enable audio if a server policy explicitly blocks audio and video playback redirection.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On the Windows Server 2022 VPS, press <code>Windows key + R<\/code>, enter the following, and select <strong>OK<\/strong>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>gpedit.msc<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Navigate to <strong>Computer Configuration \u2192 Administrative Templates \u2192 Windows Components \u2192 Remote Desktop Services \u2192 Remote Desktop Session Host \u2192 Device and Resource Redirection<\/strong>. Open <strong>Allow audio and video playback redirection<\/strong>, select <strong>Enabled<\/strong> (or <strong>Not Configured<\/strong> when no policy needs to enforce the setting), and choose <strong>Apply \u2192 OK<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Apply the local policy from an elevated PowerShell window:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>gpupdate \/force<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output includes:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Updating policy...\nComputer Policy update has completed successfully.\nUser Policy update has completed successfully.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you changed the policy, save your work and select <strong>Start \u2192 Power \u2192 Restart<\/strong>. A restart makes the session-host policy unambiguous. After the VPS comes back, reconnect with the client setting from Step 1. Microsoft documents this policy under <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/client-management\/mdm\/policy-csp-admx-terminalserver\" target=\"_blank\" rel=\"noopener\">Allow audio and video playback redirection<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Select the redirected playback device<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The server must send sound to the RDP-created endpoint instead of a missing physical speaker.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After reconnecting, press <code>Windows key + R<\/code> inside the server and run:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mmsys.cpl<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On the <strong>Playback<\/strong> tab, select <strong>Remote Audio<\/strong> or <strong>Speakers (Remote Audio)<\/strong>. Select <strong>Set Default<\/strong> if another device is selected, then open <strong>Properties \u2192 Levels<\/strong> and confirm the speaker is not muted. Use the <strong>Test<\/strong> button on the <strong>Playback<\/strong> tab to produce a short test tone.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the device is present, close the Sound window and test the application you actually need. Some applications cache their output device, so close and reopen that application after changing the default playback device.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify audio over RDP<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Verification must happen in a fresh RDP session; checking the service alone does not prove that redirection reached your computer.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Sign out of the server with <strong>Start \u2192 account picture \u2192 Sign out<\/strong>, then start a new RDP connection with <strong>Remote audio playback \u2192 Play on this computer<\/strong>.<\/li>\n\n\n<li>On the server, run <code>mmsys.cpl<\/code>, choose <strong>Remote Audio<\/strong> on the <strong>Playback<\/strong> tab, and select <strong>Test<\/strong>.<\/li>\n\n\n<li>Confirm the test tone comes from the speakers or headphones selected on your local computer, not from a server-side device.<\/li>\n\n\n<li>If the tone works, open the target application and check its own volume control and output-device setting.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">You can also confirm that the server services remained available:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-Service -Name Audiosrv,AudioEndpointBuilder | Format-Table Name,Status,StartType<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Successful output shows both services with <code>Running<\/code> status and <code>Automatic<\/code> startup.<\/p>\n\n\n\n<aside class=\"vl-element vl-cta-banner\" aria-label=\"Need Windows audio?\">\n\t<div class=\"vl-cta-banner__content\">\n\t\t<p class=\"vl-cta-banner__eyebrow\">Windows RDP hosting<\/p>\n\t\t<h3 class=\"vl-cta-banner__title\">Need Windows audio?<\/h3>\n\t\t<p class=\"vl-cta-banner__text\">Get a Windows VPS for remote applications, media, and administrator-controlled RDP settings.<\/p>\n\t<\/div>\n\t<a class=\"vl-cta-banner__button\" href=\"\/buy-windows-rdp\" aria-label=\"View Windows RDP\">View Windows RDP<\/a>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">No Remote Audio device appears<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The local client may be set to play audio on the remote computer, or the server policy may still block playback redirection. Reopen <code>mstsc.exe<\/code>, choose <strong>Show Options \u2192 Local Resources \u2192 Remote audio \u2192 Settings<\/strong>, select <strong>Play on this computer<\/strong>, confirm Step 3, then sign out and create a new session.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Windows Audio will not start<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Windows Audio depends on Windows Audio Endpoint Builder. Check the dependency first with <code>Get-Service -Name AudioEndpointBuilder<\/code>; start Endpoint Builder, then start <code>Audiosrv<\/code>. If the service stops again, open <strong>Event Viewer \u2192 Windows Logs \u2192 System<\/strong> and inspect entries from <strong>Service Control Manager<\/strong> before changing other services.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The test tone works, but an application is silent<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The application may be muted in the Windows volume mixer or may be using a different output device. Open <strong>Settings \u2192 System \u2192 Sound \u2192 Volume mixer<\/strong>, raise that application&#8217;s volume, select <strong>Remote Audio<\/strong> as its output, and restart the application so it rereads the device list.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Group Policy returns to Disabled<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A domain policy, security baseline, or hosting management policy can override a local setting. Run the following as an administrator and look for a policy that defines the audio-redirection setting:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>gpresult \/h \"$env:TEMP\\rdp-policy.html\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Open the generated report and ask the domain or platform administrator to allow <strong>audio and video playback redirection<\/strong>. Repeatedly editing the local policy will not defeat a higher-priority domain policy.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening and usage notes<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Audio redirection uses the existing RDP connection; enabling it does not require opening a new firewall port.<\/li>\n\n\n<li>Keep <strong>Remote Audio Recording<\/strong> disabled unless microphone input is necessary, because playback and recording are separate redirection permissions.<\/li>\n\n\n<li>Sign out when finished with an audio application. Closing the RDP window can leave the session disconnected and may not release the application cleanly.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Does Windows Server 2022 need a physical sound card?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. RDP can create a Remote Audio playback endpoint for the session, so a VPS does not need a physical speaker or sound card. The local computer still needs a working output device to hear the redirected sound.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I hear sound on both the server and my local computer?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The standard <strong>Play on this computer<\/strong> choice redirects the session&#8217;s playback to the RDP client. If an application must use a server-side audio device instead, select <strong>Play on remote computer<\/strong> in the RDP client&#8217;s <strong>Remote audio<\/strong> settings; that is a different output path.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I redirect my microphone to Windows Server 2022?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In the local RDP client, open <strong>Local Resources \u2192 Remote audio \u2192 Settings<\/strong> and choose an option under <strong>Remote Audio Recording<\/strong>. The server&#8217;s policy can separately deny recording redirection, so microphone access may require an administrator to allow it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why does audio stop after I reconnect?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The RDP client applies audio redirection when it creates the session. Sign out completely, verify <strong>Play on this computer<\/strong>, and start a new session; simply closing or minimizing the old RDP window can leave its original redirection state in place.<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does Windows Server 2022 need a physical sound card?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. RDP can create a Remote Audio playback endpoint for the session, so a VPS does not need a physical speaker or sound card. The local computer still needs a working output device to hear the redirected sound.\"}}, {\"@type\": \"Question\", \"name\": \"Can I hear sound on both the server and my local computer?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The standard **Play on this computer** choice redirects the session's playback to the RDP client. If an application must use a server-side audio device instead, select **Play on remote computer** in the RDP client's **Remote audio** settings; that is a different output path.\"}}, {\"@type\": \"Question\", \"name\": \"How do I redirect my microphone to Windows Server 2022?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"In the local RDP client, open **Local Resources \u2192 Remote audio \u2192 Settings** and choose an option under **Remote Audio Recording**. The server's policy can separately deny recording redirection, so microphone access may require an administrator to allow it.\"}}, {\"@type\": \"Question\", \"name\": \"Why does audio stop after I reconnect?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The RDP client applies audio redirection when it creates the session. Sign out completely, verify **Play on this computer**, and start a new session; simply closing or minimizing the old RDP window can leave its original redirection state in place.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Enable audio on Windows Server 2022 over RDP with client playback, Windows Audio services, policy settings, verification, and fixes for common failures.","protected":false},"author":1,"featured_media":820,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[5,11],"tags":[33,32,23,52],"class_list":["post-819","post","type-post","status-publish","format-standard","has-post-thumbnail","category-guides","category-windows-server","tag-audio","tag-rdp","tag-remote-desktop","tag-windows-server-2022","cs-entry"],"_links":{"self":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/819","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/comments?post=819"}],"version-history":[{"count":1,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/819\/revisions"}],"predecessor-version":[{"id":3045,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/posts\/819\/revisions\/3045"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media\/820"}],"wp:attachment":[{"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/media?parent=819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/categories?post=819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpslake.com\/blog\/wp-json\/wp\/v2\/tags?post=819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}