[VERIFIED BUG] If you're getting the "Oops! There's an issue"- error, read this first. [OOPS ERROR]

[doolhoofd]

Hi @Milincho,

Yes, this is a known problem, there have indeed already been multiple reports of issues while using FxSound combined with Remote Desktop; this was the advice offered by FxSound’s lead programmer @bvijay on the difficulties with RDP:

@bvijay

There is an article in Microsoft forums on RDP audio, and the solution given is to enable “Allow audio and video playback redirection” in the group policy,
Local Computer Policy->Computer Configuration->Administrative Templates->Windows Components->Remote Desktop Session Host->Device and Resource Redirection
Remote Desktop Connection not pulling in audio from local machine to remote physical machine - Microsoft Q&A

@bvijay

we need to investigate further on making FxSound device available over RDP.
Can you please run this common in powershell and share us the output:
wmic sounddev list full
It will help us debug this issue and find a solution.

It would help the troubleshooting effort if you could:

• Try the proposed solution “Allow audio and video playback redirection,” and
• Run the Powershell check,

And post back here with the results.
Also, the user who opened the thread, added this remark:

@pedoc

Noting that other people have reported that FxSound works fine when using TeamViewer, and I have VNCServer installed on the host machine and connect via VNCViewer, and FxSound also works fine. So, maybe it’s because RDP works differently and then conflicts with FxSound.

FYI, all quotes are copied from this thread:

Crash in rdp

When connecting to a host with FXSound installed via Windows Remote Desktop, FXSound will crash and exit. I saw another report here (Connecting to machine over RDP causes this error [OOPS ERROR]) but the topic is locked Unable to view, how to solve this fault? Thank you