# Suspend rather than crash for RDP **URL:** \ **Category:** General Discussion\ **Created:** [May 29, 2026, 8:00pm UTC](https://forum.fxsound.com/t/suspend-rather-than-crash-for-rdp/6613 "2026-05-29T20:00:03Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dmcdivitt](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@dmcdivitt](https://forum.fxsound.com/u/dmcdivitt)\ **Post date:** [May 29, 2026, 8:00pm UTC](https://forum.fxsound.com/t/suspend-rather-than-crash-for-rdp/6613/1 "2026-05-29T20:00:04Z")
I often remote in to my PC with RDP. Instantly a pop up appears generated by FxSound that it has crashed. This is a handled error. This is a severe nuisance because when I use the PC through the console again I never remember to relaunch FxSound. Since the error is handled, why can’t FxSound simply suspend operation instead of crashing? Following that, if a connection event occurs, it can test to see if it’s the console to either resume or remain suspended. If there is no event for this, test every couple of minutes to see if resuming is possible. The tray icon might show a suspended status. ---
**Author:** ![coreywillei](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@coreywillei](https://forum.fxsound.com/u/coreywillei)\ **Post date:** [June 8, 2026, 2:28am UTC](https://forum.fxsound.com/t/suspend-rather-than-crash-for-rdp/6613/2 "2026-06-08T02:28:36Z")
never used RDP, my half-cent no-fact-based guess is it could be platform incompatible. maybe an application can crash in VM or remote control due to platform-not-supported? (but again, not sure how you use rdp in your case just cooked up a theory) * * * another cooked up idea: if you forget to never remember relaunch fxsound, try make a schedule task with conditional trigger or just a schedule to periodically relaunch fxsound (every hour starting the moment pc’s loged in, for example). I do this with some other stuffs that I absolutely needed them to not offing-themselves 💀 while I’m in middle of a task ---
**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:** [June 15, 2026, 4:55am UTC](https://forum.fxsound.com/t/suspend-rather-than-crash-for-rdp/6613/3 "2026-06-15T04:55:20Z")
@dmcdivitt In RDP FxSound Audio Enhancer device will not be available for FxSound to function. We can consider detecting RDP session and disable FxSound. ---
**Author:** ![dmcdivitt](https://avatars.discourse-cdn.com/v4/letter/d/3d9bf3/32.png) [@dmcdivitt](https://forum.fxsound.com/u/dmcdivitt)\ **Post date:** [July 8, 2026, 5:15am UTC](https://forum.fxsound.com/t/suspend-rather-than-crash-for-rdp/6613/4 "2026-07-08T05:15:48Z")
Howdy! I’m wondering if you gave anymore consideration to RDP detection and pausing FXSound rather than crashing it. This is a big nuisance for me. As a programmer myself and considering the issue, you would not have to do much. You already have code to display the crash message to the user. At that point instead of crashing see if RDP connected on the console session. If so, pause instead. About resuming FXSound, to avoid having to see what event would work, use a 60 second timer and test for RDP on the console session. There may be multiple sessions simultaneously each with a logged in user so the test would be whether RDP is still present on the console session. Occasionally I will do a second login and use RDP for that. I always get the FXSound crash message with that. Before displaying that you could test to see if it is the console session. FXSound should always work if the console session with hardware monitor compared to virtual for RDP. If not the console session you maybe can skip displaying the crash message. Have a happy day! ---
**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:** [July 10, 2026, 6:45pm UTC](https://forum.fxsound.com/t/suspend-rather-than-crash-for-rdp/6613/5 "2026-07-10T18:45:02Z")
We will have fix for this in the next version. In RDP session we will prevent FxSound processing, but do not exit the application. When the user logs in to the console session FxSound can resume processing.