Windows 11 24h2 & 25h2 update not working with the Microsoft WDA

Question

After staff have updated from Win 11 Enterprise 23h2 to the newer versions the audio is no longer working through the Wireless Display adapters. The surfaces are detecting it as an Audio output but still plays through the surface speakers when the adapter is selected, or it doesn't play at all.

I have reinstalled all the audio drivers and this has not resolved the issue.

Has anyone else noticed this problem? And is there a known fix that would be able to deploy remotely?

Answer 1

There have been other reports like this. Please open a support case with Surface for Business https://learn.microsoft.com/en-us/surface/contact-surface-business-education-support - 23H2 will stop receiving security updates next week, and I do not recommend you go back to this build.

Answer 2

We have found that it is the Dolby APPs that are the problem.

Possible solution: In Services disable the Dobly DAX API service and dolby Fusion API service.

Uninstall the Dolby APPs in terminal using:

Get-AppxPackage dolby | Remove-AppxPackage -AllUsers

Answer 3

PowerShell Rollback Script

This script resets the Miracast audio render policy and restarts the Wireless Display service:

# Remove Miracast AudioRender policy key
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\WdFilter\Parameters"
if (Test-Path $regPath) {
    Remove-ItemProperty -Path $regPath -Name "AudioRenderPolicy" -ErrorAction SilentlyContinue
}

# Restart Wireless Display service
Write-Host "Restarting Wireless Display service..."
Stop-Service -Name WdSvc -Force
Start-Service -Name WdSvc

# Optional: Restart audio service
Restart-Service -Name Audiosrv

Write-Host "Rollback complete. Miracast audio policy reverted to default."

Answer 4

PowerShell Script for Registry Fix + Service Restart

This script resets the Miracast audio render policy and restarts the Wireless Display service:

# Reset Miracast AudioRender policy
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\WdFilter\Parameters"
if (!(Test-Path $regPath)) {
    New-Item -Path $regPath -Force
}
Set-ItemProperty -Path $regPath -Name "AudioRenderPolicy" -Value 0 -Type DWord

# Restart Wireless Display service
Write-Host "Restarting Wireless Display service..."
Stop-Service -Name WdSvc -Force
Start-Service -Name WdSvc

# Optional: Restart audio service
Restart-Service -Name Audiosrv

Write-Host "Miracast audio policy reset and services restarted successfully."

Answer 5

Thanks for reaching out, Connor. I understand that after updating to the W11 Enterprise 22H2 the audio for Wireless Display no longer worked. Upon researching, this issue has been reported by several admins after upgrading to Windows 11 24H2 and 25H2. It seems to be related to changes in Miracast/Wireless Display handling and audio routing in these builds.

Surface devices see the Wireless Display Adapter as a sound output, but sound either goes back to the device's speakers or stops working.

Reinstalling sound drivers doesn’t solve things because the issue is with the operating system, not the drivers.

Here are some workarounds and suggestions:

Miracast settings: Sometimes, turning off and then on Allow input from keyboard or mouse in Wireless Display settings makes the sound work as it should.

Wireless Display Adapter update: Ensure the adapter has the newest software by using the Microsoft Wireless Display Adapter app.

Registry fix: Some IT folks have fixed this by resetting the AudioRender policy for Miracast. You’ll need to edit HKLM\SYSTEM\CurrentControlSet\Services\WdFilter\Parameters and restart the Wireless Display service.

Go back to 23H2: If sound over WDA is a must-have and nothing else works, going back to version 23H2 is the best bet until Microsoft fixes this.

Fix it remotely: To fix this from afar, you can use PowerShell to script the registry fix or the Miracast input toggle. Then, push it out through Intune or Group Policy.