# \[VERIFIED BUG\] If you're getting the "Oops! There's an issue"- error, read this first. \[OOPS ERROR\] **URL:** \ **Category:** Get Help\ **Tags:** verified-bug\ **Created:** [May 18, 2022, 8:43am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847 "2022-05-18T08:43:12Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [May 18, 2022, 8:43am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/1 "2022-05-18T08:43:12Z")
Hello kind user, Since we’ve been getting this error a lot, I thought I’d pin the troubleshooting suggestions, for the moment. Please look here for answers first before making a new thread - thanks, and good luck: > [@Oops there's an issue with your playback device settings \[OOPS ERROR\]](https://forum.fxsound.com/t/oops-theres-an-issue-with-your-playback-device-settings-oops-error/553): > > I have this issue the moment Fxsound installed which is written in the title i did as it is said in the website to troubleshoot it but no device was disabled please help [image] ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/7979b2bc1f358df05ac624db42f6480c5e8ac49c.png) ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [May 18, 2022, 8:45am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/6 "2022-05-18T08:45:28Z")
---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [July 1, 2022, 12:17pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/7 "2022-07-01T12:17:29Z")
---
**Author:** ![York\_Gonzalez](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/york_gonzalez/32/745_2.png) [@York\_Gonzalez](https://forum.fxsound.com/u/York_Gonzalez)\ **Post date:** [December 3, 2022, 1:07pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/8 "2022-12-03T13:07:26Z")
FxSound2 Pro 1.1.14.0 and FxSound2 Pro 1.1.16.0, I get the next error “Oops! There’s an issue with your playback device settings Before we can get started, please go through the troubleshooting steps here Contact us you’re still having problems” None of the tips and indications that appear on the troubleshooting web page have helped me, as indicated there, of course it indicates that the program is installed, since it can be viewed in the add or remove programs section, but not it creates the virtual audio devices of FXSOUND, which interact with the physical ones of the pc’s audio card, it is as if nothing had been installed Therefore, I appreciate your support, with a version that I praise to solve all these errors, for now I have to wait, hopefully they solve it soon and notify me, Thank you very much for listening to me, I am waiting for a solution ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [December 3, 2022, 1:28pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/9 "2022-12-03T13:28:32Z")
Hi @York_Gonzalez, There are several solutions to this problem proposed in the thread I linked above, > [@Oops there's an issue with your playback device settings \[OOPS ERROR\]](https://forum.fxsound.com/t/oops-theres-an-issue-with-your-playback-device-settings-oops-error/553): > > I have this issue the moment Fxsound installed which is written in the title i did as it is said in the website to troubleshoot it but no device was disabled please help [image] Have you tried those? ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [December 4, 2022, 9:43pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/10 "2022-12-04T21:43:34Z")
> [@York\_Gonzalez](#): > > for now I have to wait, hopefully they solve it soon and notify me, > > Thank you very much for listening to me, I am waiting for a solution No one likes having to wait… 😉 ---
**Author:** ![York\_Gonzalez](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/york_gonzalez/32/745_2.png) [@York\_Gonzalez](https://forum.fxsound.com/u/York_Gonzalez)\ **Post date:** [December 5, 2022, 12:46am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/11 "2022-12-05T00:46:03Z")
If I did but I didn’t work ☹ ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [December 5, 2022, 8:19pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/12 "2022-12-05T20:19:07Z")
---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [December 5, 2022, 8:19pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/13 "2022-12-05T20:19:41Z")
---
**Author:** ![Milincho](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Milincho](https://forum.fxsound.com/u/Milincho)\ **Post date:** [December 7, 2022, 6:55pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/14 "2022-12-07T18:55:01Z")
This happens every single time you connect to the computer with FxSound using Remote Desktop from another computer. It doesn’t even respond to the X close button and forces you to kill FxSound in the task manager. ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [December 7, 2022, 7:29pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/15 "2022-12-07T19:29:36Z")
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: > [@Crash in rdp](https://forum.fxsound.com/t/crash-in-rdp/1054/5): > > 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](https://docs.microsoft.com/en-us/answers/questions/86750/remote-desktop-connection-not-pulling-in-audio-fro.html) > [@Crash in rdp](https://forum.fxsound.com/t/crash-in-rdp/1054/14): > > 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: > [@Crash in rdp](https://forum.fxsound.com/t/crash-in-rdp/1054/16): > > 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](https://forum.fxsound.com/t/crash-in-rdp/1054/): > > 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]](https://forum.fxsound.com/t/connecting-to-machine-over-rdp-causes-this-error-oops-error/172)) but the topic is locked Unable to view, how to solve this fault? Thank you ---
**Author:** ![Milincho](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Milincho](https://forum.fxsound.com/u/Milincho)\ **Post date:** [December 8, 2022, 3:48pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/16 "2022-12-08T15:48:59Z")
I changed the Group Policy setting but the crash keeps happening. Run the Powershell command and this is the result: Availability= ConfigManagerErrorCode=0 ConfigManagerUserConfig=FALSE Description=NVIDIA High Definition Audio DeviceID=HDAUDIO\FUNC\_01&VEN\_10DE&DEV\_00A4&SUBSYS\_10DE167A&REV\_1001\5&329484F5&0&0001 DMABufferSize= ErrorCleared= ErrorDescription= InstallDate= LastErrorCode= Manufacturer=NVIDIA MPU401Address= Name=NVIDIA High Definition Audio PNPDeviceID=HDAUDIO\FUNC\_01&VEN\_10DE&DEV\_00A4&SUBSYS\_10DE167A&REV\_1001\5&329484F5&0&0001 PowerManagementCapabilities= PowerManagementSupported=FALSE ProductName=NVIDIA High Definition Audio Status=OK StatusInfo=3 Availability= ConfigManagerErrorCode=0 ConfigManagerUserConfig=FALSE Description=Realtek High Definition Audio DeviceID=HDAUDIO\FUNC\_01&VEN\_10EC&DEV\_1220&SUBSYS\_1458A0C3&REV\_1001\5&1EDA78B&0&0001 DMABufferSize= ErrorCleared= ErrorDescription= InstallDate= LastErrorCode= Manufacturer=Realtek MPU401Address= Name=Realtek High Definition Audio PNPDeviceID=HDAUDIO\FUNC\_01&VEN\_10EC&DEV\_1220&SUBSYS\_1458A0C3&REV\_1001\5&1EDA78B&0&0001 PowerManagementCapabilities= PowerManagementSupported=FALSE ProductName=Realtek High Definition Audio Status=OK StatusInfo=3 Availability= ConfigManagerErrorCode=0 ConfigManagerUserConfig=FALSE Description=NVIDIA Virtual Audio Device (Wave Extensible) (WDM) DeviceID=ROOT\UNNAMED\_DEVICE\0000 DMABufferSize= ErrorCleared= ErrorDescription= InstallDate= LastErrorCode= Manufacturer=NVIDIA MPU401Address= Name=NVIDIA Virtual Audio Device (Wave Extensible) (WDM) PNPDeviceID=ROOT\UNNAMED\_DEVICE\0000 PowerManagementCapabilities= PowerManagementSupported=FALSE ProductName=NVIDIA Virtual Audio Device (Wave Extensible) (WDM) Status=OK StatusInfo=3 Availability= ConfigManagerErrorCode=0 ConfigManagerUserConfig=FALSE Description=FxSound Audio Enhancer DeviceID=ROOT\MEDIA\0000 DMABufferSize= ErrorCleared= ErrorDescription= InstallDate= LastErrorCode= Manufacturer=FxSound MPU401Address= Name=FxSound Audio Enhancer PNPDeviceID=ROOT\MEDIA\0000 PowerManagementCapabilities= PowerManagementSupported=FALSE ProductName=FxSound Audio Enhancer Status=OK StatusInfo=3 Availability= ConfigManagerErrorCode=0 ConfigManagerUserConfig=FALSE Description=Oculus Virtual Audio Device DeviceID=ROOT\MEDIA\0001 DMABufferSize= ErrorCleared= ErrorDescription= InstallDate= LastErrorCode= Manufacturer=Oculus MPU401Address= Name=Oculus Virtual Audio Device PNPDeviceID=ROOT\MEDIA\0001 PowerManagementCapabilities= PowerManagementSupported=FALSE ProductName=Oculus Virtual Audio Device Status=OK StatusInfo=3 Availability= ConfigManagerErrorCode=0 ConfigManagerUserConfig=FALSE Description=Virtual Desktop Audio DeviceID=ROOT\MEDIA\0002 DMABufferSize= ErrorCleared= ErrorDescription= InstallDate= LastErrorCode= Manufacturer=Virtual Desktop MPU401Address= Name=Virtual Desktop Audio PNPDeviceID=ROOT\MEDIA\0002 PowerManagementCapabilities= PowerManagementSupported=FALSE ProductName=Virtual Desktop Audio Status=OK StatusInfo=3 ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [December 8, 2022, 5:46pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/17 "2022-12-08T17:46:00Z")
@bvijay: User @Milincho is experiencing problems with Remote Desktop, and has followed all of your advice (which I quoted earlier): - “Allow audio and video playback redirection” was enabled; - “wmic sounddev list full” Powershell check results have been posted above; Can you please offer further guidance and troubleshooting? **THANKS** once again. ---
**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\ **Post date:** [December 9, 2022, 2:38pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/18 "2022-12-09T14:38:27Z")
@doolhoofd I have prepared a setup to access the system running FxSound over RDP. I will debug the remote desktop problem that @Milincho has reported and update on the solution. ---
**Author:** ![York\_Gonzalez](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/york_gonzalez/32/745_2.png) [@York\_Gonzalez](https://forum.fxsound.com/u/York_Gonzalez)\ **Post date:** [December 10, 2022, 12:16am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/19 "2022-12-10T00:16:26Z")
> [@Milincho](#): > > This happens every single time you connect to the computer with FxSound using Remote Desktop from another computer. It doesn’t even respond to the X close button and forces you to kill FxSound in the task manager. 587 / 5,000 ## Resultados de traducción ### Resultados de traducción star\_border Hi @Milincho, good night, I understand the case you propose, however I believe that my case is not the same, because here the problem is that when trying to install the program, the drivers are not installed, it always generates error. On the other hand, I do use a remote -support program for support, it is the Anydesk in its 7.0.14 version, but I think it is not the failure, because I have performed all tests and indications that all the leaders and collaborators of the Me forum They have indicated but unfortunately it has not been achieved success, I also remain attentive to support with the solution Thanks a lot ---
**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\ **Post date:** [December 10, 2022, 3:25am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/20 "2022-12-10T03:25:31Z")
When connecting over RDP, if the RDP connection setting for audio is set to Play on this computer, ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/4d6d67cc2d6838ea468e7d0bfb4f475e2f950d9b.png) then only Remote Audio is available as playback device. FxSound cannot start because FxSound Audio Enhancer device is not available in this scenario. ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/3298d19e9c99ee6bd925d408b753e88ca59597a6.png) If Remote Desktop Client connection audio setting is Play on remote computer ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/4bc080a55b1b758e21c078a1bf767baae7f6ec1c.png) Then the device is available and FxSound is running ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/1X/26b07ffd0c79bd08d3cd222bcc3704e40e88d095.png) So, if playing audio on the remote PC is the requirement, then set the client option accordingly and FxSound will run on the remote PC. But, if audio has to be played on the local PC but FxSound has to run on the remote PC process the audio that plays locally then it is not possible. ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [January 7, 2023, 8:41pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/21 "2023-01-07T20:41:28Z")
---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [January 7, 2023, 8:41pm UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/22 "2023-01-07T20:41:38Z")
---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [January 13, 2023, 1:38am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/23 "2023-01-13T01:38:29Z")
Hello @bvijay; Could you please assist user @Sozo experiencing loss of sound when using FxSound through RDP (see post quoted below)? My knowledge of RDP is … limited? … No; in all honesty, it’s nearly non-existent. Thanks again! > [@FX Sound quits over RDP every few minutes](https://forum.fxsound.com/t/fx-sound-quits-over-rdp-every-few-minutes/1603/1): > > Howdy team, very cool little utility that you have here. I just found it yesterday and I am impressed by it’s capability! My laptop now has the sound of a stereo system! > > The issue I am experiencing is that when working remotely via RDP, the sound quits every few minutes. > The devices are still recognized and show that they are outputting sound both in the FX Sound GUI and in the properties of the audio device windows GUI, there just isn’t any sound. > A simple disable/re-enable of the device in the sound properties fixes it instantly, however it happens every two to five minutes so it is cumbersome nonetheless. > I did read the other persons post on here with a similar issue, but his devices were disabling and showing no activity, which as I stated is not the case for me. Also I do not get the OOPS error at all. Everythign looks good just no sound when it happens. > It works fine on my laptop alone. The issue only presents after I log into a remote workstation. > > Thanks for any help! A sweet utility nonetheless for movie’s n such! It’s just for work where it becomes difficult… > Best, > Sozo ---
**Author:** ![doolhoofd](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/doolhoofd/32/1131_2.png) [@doolhoofd](https://forum.fxsound.com/u/doolhoofd)\ **Post date:** [January 18, 2023, 9:43am UTC](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847/24 "2023-01-18T09:43:32Z")
@bvijay: User @hwiese1980 is also experiencing problems with RDP; > [@FX Sound quits over RDP every few minutes](https://forum.fxsound.com/t/fx-sound-quits-over-rdp-every-few-minutes/1603/4): > > I can confirm that FxSound has a problem when connecting to the PC via RDP. It crashes for me too and won’t let me restart it via RDP. It should be easily reproducable. [Next page](https://forum.fxsound.com/t/verified-bug-if-youre-getting-the-oops-theres-an-issue-error-read-this-first-oops-error/847.md?page=2)