# Monitor upgrade killed FXSound

**URL:** <https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632>\
**Category:** Get Help\
**Tags:** bug-fixed\
**Created:** [June 28, 2025, 6:41am UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632 "2025-06-28T06:41:31Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![DarkSky](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@DarkSky](https://forum.fxsound.com/u/DarkSky)\
**Post date:** [June 28, 2025, 6:41am UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/1 "2025-06-28T06:41:31Z")

</div>

I recently upgraded my external monitor from Acer XR382CQK (38" 3840x1600) to an Asus ROG Swift PG38UQ (38" 3840x2160) on Windows-11 24H2, thereby somehow breaking FxSound which I normally use to profile sound on my eoteck NTK059 USB to headphone jack external pre-amp to Audioengine A5+ bookshelf speakers. FYI, this is using the latest installer. I had to disable FxSound to select headphones as the output.

---

<div class="post-metadata">

**Author:** ![james](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/james/32/2294_2.png) [@james](https://forum.fxsound.com/u/james)\
**Post date:** [June 30, 2025, 3:14pm UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/2 "2025-06-30T15:14:18Z")

</div>

Sorry about this. Can you explain what you mean when you say that FxSound has been killed by this monitor upgrade? Does the app no longer open?

---

<div class="post-metadata">

**Author:** ![DarkSky](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@DarkSky](https://forum.fxsound.com/u/DarkSky)\
**Post date:** [June 30, 2025, 7:50pm UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/3 "2025-06-30T19:50:25Z")

</div>

When attempting to select FxSound as the output device, Windows ‘bounces’ your attempted selection to something else. I do have the monitor’s USB connected to the notebook - maybe that was my mistake?

---

<div class="post-metadata">

**Author:** ![DarkSky](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@DarkSky](https://forum.fxsound.com/u/DarkSky)\
**Post date:** [June 30, 2025, 7:51pm UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/4 "2025-06-30T19:51:17Z")

</div>

And, the app opens just fine.

---

<div class="post-metadata">

**Author:** ![james](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/james/32/2294_2.png) [@james](https://forum.fxsound.com/u/james)\
**Post date:** [July 3, 2025, 5:24pm UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/5 "2025-07-03T17:24:39Z")

</div>

So you’re trying to select FxSound as the output device but Windows is selecting a different one instead? When FxSound is running we do automatically switch the output device to FxSound and instead ask that you change your output device through the FxSound app.

---

<div class="post-metadata">

**Author:** ![DarkSky](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@DarkSky](https://forum.fxsound.com/u/DarkSky)\
**Post date:** [July 4, 2025, 12:01am UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/6 "2025-07-04T00:01:31Z")

</div>

Yes, Windows Settings ‘bounces’ you to another device.

---

<div class="post-metadata">

**Author:** ![DarkSky](https://avatars.discourse-cdn.com/v4/letter/d/f08c70/32.png) [@DarkSky](https://forum.fxsound.com/u/DarkSky)\
**Post date:** [July 4, 2025, 4:20pm UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/7 "2025-07-04T16:20:59Z")

</div>

James,

Update: I’m not sure what I did that mattered, but all is good now. I rebooted Win-11 (24H2) and enabled FxSound in the control panel which you still need to (re)enable devices in Win-11, apparently. I tend to avoid rebooting like The Plague because a reboot posts so many error events that I tend to need two reboots, each one taking around 2.5 hours (tons of DCOM waits, for example). Something that was stuck is now unstuck. Sincere apologies for not going the extra mile (rebooting) before crying wolf.

-Mike Landis

 ![image.png](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/d/db38cf8e767f12bbc43768dd9eccc7b7bf4a7f97.png)

---

<div class="post-metadata">

**Author:** ![james](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/james/32/2294_2.png) [@james](https://forum.fxsound.com/u/james)\
**Post date:** [July 9, 2025, 9:33pm UTC](https://forum.fxsound.com/t/monitor-upgrade-killed-fxsound/5632/8 "2025-07-09T21:33:20Z")

</div>

Closed on July 9, 2025, 9:33pm UTC


