# You ruined all my sound!

**URL:** <https://forum.fxsound.com/t/you-ruined-all-my-sound/2935>\
**Category:** Get Help\
**Created:** [March 29, 2024, 9:33pm UTC](https://forum.fxsound.com/t/you-ruined-all-my-sound/2935 "2024-03-29T21:33:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![opsvixen](https://avatars.discourse-cdn.com/v4/letter/o/d07c76/32.png) [@opsvixen](https://forum.fxsound.com/u/opsvixen)\
**Post date:** [March 29, 2024, 9:33pm UTC](https://forum.fxsound.com/t/you-ruined-all-my-sound/2935/1 "2024-03-29T21:33:00Z")

</div>

Dear FX:

1. It would have been nice if you would have said somewhere that when re-downloading the update, you will have to reboot. Otherwise, it took ALL my sound out when I didn’t have FX on, and when FX was on, you could barely hear it even at full blast. This was the NEW update .22 from .20

2. I hope there is some help that if FX is removed, it doesn’t take your sound along with it.

3. When there is another update available (eg .20 to .22) the OLD v. does NOT work, or open up. Also, the regular update button never works. even when an update is available, it just says there’s an “error”.

---

<div class="post-metadata">

**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:** [March 30, 2024, 1:18am UTC](https://forum.fxsound.com/t/you-ruined-all-my-sound/2935/2 "2024-03-30T01:18:42Z")

</div>

On behalf of the entire team, our apologies for the problems you experienced.  
And thank you for editing your post and providing further details to help us improve.

> [@opsvixen](#):
>
> When there is another update available (eg .20 to .22) the OLD v. does NOT work, or open up.

My experience is different. As a moderator on the forum, I’ve switched versions successfully many times in the past.

> [@opsvixen](#):
>
> Also, the regular update button never works. even when an update is available, it just says there’s an “error”.

Which button are you referring to? The “Check for updates” link in the Settings?  
This is a known issue, and it is actively being worked on, see the most recent commits to the issue below.  
When a new version is released, downloading the installer .exe and running it, does the trick for me 90% of the time.

> <https://github.com/fxsound2/fxsound-app/issues/2>
>
> Steps to reproduce the behavior:
> 1. Go to Settings;
> 2. Click on Help;
> 3. Scro…ll down to Maintenance;
> 4. Click on Check for updates;
> 5. Browser opens https://www.fxsound.com/changelog 
> 
> Desired behavior: 
> Clicking Check for updates updates FxSound to the latest version.

> [@Want to help us beta test V1.1.20.0?](https://forum.fxsound.com/t/want-to-help-us-beta-test-v1-1-20-0/2297/33):
>
> @doolhoofd I checked the code change history. The “Check for updates” link in the settings dialog has always been set to [Changelog - FxSound](https://www.fxsound.com/changelog). From the application we have not implemented an update feature, so we have set the link to the Changelog. For installer to update to new version, use “Check for FxSound updates” in Start menu.

---

<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:** [April 1, 2024, 11:21pm UTC](https://forum.fxsound.com/t/you-ruined-all-my-sound/2935/3 "2024-04-01T23:21:02Z")

</div>

@opsvixen sorry about the troubles with your sound. I just issued you a refund for the donation.

---

<div class="post-metadata">

**Author:** ![Fakename70](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/fakename70/32/2797_2.png) [@Fakename70](https://forum.fxsound.com/u/Fakename70)\
**Post date:** [December 7, 2025, 12:48am UTC](https://forum.fxsound.com/t/you-ruined-all-my-sound/2935/4 "2025-12-07T00:48:57Z")

</div>

I also had an issue for about a year with nothing happening after clicking “update” until a month or so ago when it finally worked. I figured it had to have been a device issue. But, after scrolling the forums I discovered that others were having the same low volume issue after successfully “updating” as I had. I uninstalled and re-installed multiple times, but, it still didn’t work as before installing the latest update.

Found a link in another forum to a list of previous versions that hopefully will take me back to how I had it before when the app worked perfectly.
