none
Windows audio service crashing

    General discussion

  • We had been having issues since a patch was applied to our servers on 20th feb kb4487006.  We can prove this as we have a snapshot from 15th feb which does not experience this issue.  We are also using windows server 2016 and citirix xenapp 7.15cu3.  Since that patch windows audio service hangs intermittently sometimes its fine then we may get one or two broken servers a day with up to 20 concurrent sessions.  When it breaks there is no speaker symbol on the taskbar and skype will not load, only the splash screen apears, also trying to use mstsc does not work as these are all hooked in to svchost for the audio service.  

    We rolled back to 15th feb and applied updates last week from march.  The original kb above is no longer on the server and has been replaced with kb4489889.  We had this running for 4 days happily then yesterday the issue came up again on 6 servers.  With. Multi user you can attempt to restart audio but it will fail and then seems to recover after a while.  Attempting to restart it while its broken results in a duplicate endpoint error.  Once its restarted the audio comes back and skype will work again as does rdp from the desktop using mstsc.  

    We’ve been troubleshooting this for the past 3 weeks but need to open a case with MS now as it appears to be a common issue which is a very serious problem

    has anyone found a solution for this issue?

    Saturday, April 6, 2019 8:23 PM

All replies

  • I'm having the same issue here. Seems like something is causing the Windows Audio service to crash randomly. This happens about once a week. We have to force kill the service and start it again. I would like to find a solution for this problem as well.

    (KB4487006)(KB4489889) updates that are on the server.

    Friday, April 19, 2019 6:15 PM
  • Did you ever manage to find a fix for this issue? 
    Tuesday, May 14, 2019 12:47 PM
  • We have also been experiencing this exact same issue and have not had any success tracking down the cause. Did you ever find a way to resolve it? or a workaround at least.
    Wednesday, May 22, 2019 1:19 PM