Audio crashes - Microsoft Remote Desktop (RDP)
Posted: 20 Nov 2022 14:47
Hello all,
I was running ProppFrexx on Windows 8.1 for years and I decided to migrate to Windows 10 because Windows 8.1 support will stop in January 2023.
Because ProppFrexx is installed on my server, I use Microsoft Remote Desktop (RDP) to control the PC. The problem is since I migrated to Windows 10, every time I CLOSE the RDP, audio crashes. The RDP settings are set correctly ("Play sound on remote computer"). I can reproduce that "bug" on multiple machines with different hardware so it is not related to my setup.The "best" workaround I found it so set the audio device to WDM, which make an audio interruption of 1-2 sec, which is still not good.
On Windows 8.1 it was running fine with any device settings (WDM/WASAPI).
Note : this bug is not directly related to ProppFrexx. I tested with other apps like AIMP or Winamp, and the behaviour is the more or less the same. This is the reason why I did not post this into the Bug Reports section.
So, I would like to know if someone here is experiencing the same issue in Windows 10, and if you know how to solve it.
Thank you,
Quentin
I was running ProppFrexx on Windows 8.1 for years and I decided to migrate to Windows 10 because Windows 8.1 support will stop in January 2023.
Because ProppFrexx is installed on my server, I use Microsoft Remote Desktop (RDP) to control the PC. The problem is since I migrated to Windows 10, every time I CLOSE the RDP, audio crashes. The RDP settings are set correctly ("Play sound on remote computer"). I can reproduce that "bug" on multiple machines with different hardware so it is not related to my setup.The "best" workaround I found it so set the audio device to WDM, which make an audio interruption of 1-2 sec, which is still not good.
On Windows 8.1 it was running fine with any device settings (WDM/WASAPI).
Note : this bug is not directly related to ProppFrexx. I tested with other apps like AIMP or Winamp, and the behaviour is the more or less the same. This is the reason why I did not post this into the Bug Reports section.
So, I would like to know if someone here is experiencing the same issue in Windows 10, and if you know how to solve it.
Thank you,
Quentin