Hi,
I had been enjoying and using FXSound on Windows 11. I had a custom settings file. I was alerted to a new version and clicked install. Now neither this version nor the old one will get past “settings file not found”. Not sure how to proceed. Thank you for any assistance including complete uninstall instructions. I looked in the registry and I really don’t know what to do.
1 Like
Hi Scott,
opened 12:42AM - 09 Dec 23 UTC
bug
**1. "Failed to enumerate objects in the container. Access is denied."
2. "Set… tings file not found!" (AppData)
3. "Source file not found!" (fxsound1.cab in AppData \ Roaming)
4. "Invalid digital signature." (fxsound1.cab in AppData \ Roaming)**
_________________________________________________
**1. Installation fails and the error "Failed to enumerate objects in the container. Access is denied." appears**
Description:
"Error Applying Security
An error occurred while applying security information to:
C: \ ProgramData \ FxSound
Failed to enumerate objects in the container. Access is denied."
Reported by:
Forum member fevglikbgjhs
https://forum.fxsound.com/t/settings-file-not-found-when-trying-to-launch-fxsound/1542/12
Possible cause(s):
Elaboration by @bvijay74:
This error means that the user account does not have any access permission to the folder C: \ProgramData\FxSound. The default settings are stored in C: \ProgramData\FxSound during installation and copied to %APPDATA%\FxSound for each user on application launch. So, the user launching the application should have permission to read settings from C: \ProgramData\FxSound.
Possible solution(s):
* Confirm if the logged-in user has permission to the required folder with the command "icacls"
* Log in with a different user account;
* Change the folder permissions;
* Uncheck Read-only under Properties > Attributes;
* Run FxSound as Administrator.
_________________________________________________
**2. Installation seems successful, but launch fails and the error "Settings file not found!" appears (AppData)**
Description:
Reported by:
Forum member Plide
https://forum.fxsound.com/t/settings-file-not-found-when-trying-to-launch-fxsound/1542
Possible cause(s):
The absence of permission to access the AppData folder.
Possible solution(s):
* Confirm if the logged-in user has permission to the required folder with the command "icacls"
* Change the folder permissions;
* Copy the file manually - elaboration by @bvijay74:
Check if the file FxSound.settings file is present in the %APPDATA%\FxSound directory. FxSound installation should normally create the defaults settings file in this directory. If the file is not created due to any permission issue, then you can copy FxSound.settings from %PROGRAMDATA%\FxSound to %APPDATA%\FxSound.
* Run FxSound as Administrator - elaboration by @bvijay74:
If the FxSound.settings file is not present in %APPDATA%\FxSound, then upon FxSound launch the file gets created. User will get the error only if FxSound does not have the permission to create the file. So, running FxSound as an Administrator is another option to overcome the issue. Subsequent launches can be as standard user, but the settings changes will not get saved. Application launch error can be avoided this way and this does not require any manual changes to the settings file.
* Tutorial for fixing the "Settings file not found!" error on Windows 11 by forum member justinfoHowto:
https://www.youtube.com/watch?si=iUpOVhBwpGPK7iFX
_________________________________________________
**3. Installation fails and the error "Source file not found!" appears (fxsound1.cab in AppData \ Roaming)**
Description:
Reported by:
Forum members JaspaR,
https://forum.fxsound.com/t/cant-install-source-file-not-found-fxsound1-cab-in-roamingappdata/896
LolplayerYT
https://forum.fxsound.com/t/it-says-that-i-need-to-verify-the-files-but-i-dont-know-how-to-fix-it/2412
Possible cause(s):
Usually on old versions of Windows (7, XP) with outdated root certificates. If the root certificates are out of date, then there may be problems checking the valid digital signatures of files.
Possible solution(s):
* Update certificates or system;
* Install from the [Microsoft Store](https://apps.microsoft.com/store/detail/fxsound/XP8JK4TBQ03LZ4);
* Solution shared by @bvijay74:
Extract the installer by running fxsound_setup.exe /extract
Once the files are extracted, you can verify the cab file signature by running
signtool verify /pa fxsound1.cab
Then run fxsound.x64.msi on 64 bit systems or fxsound.msi on 32 bit systems, to install FxSound.
_________________________________________________
**4. Installation fails and the error "Invalid digital signature." appears (fxsound1.cab in AppData \ Roaming)**
Description:
"A file that is required cannot be installed because the cabinet file [...]fxsound1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt."
Reported by:
Forum members Zipper,
https://forum.fxsound.com/t/corrupt-cab/1613
Ayman,
https://forum.fxsound.com/t/error-when-installing-on-windows-7-x86/1923
salvofogliani
https://forum.fxsound.com/t/installation-problem/1915
Possible cause(s):
Usually on old versions of Windows (7, XP) with outdated root certificates. If the root certificates are out of date, then there may be problems checking the valid digital signatures of files.
Possible solution(s):
* Update certificates or system;
* Install from the [Microsoft Store](https://apps.microsoft.com/store/detail/fxsound/XP8JK4TBQ03LZ4);
* Solution shared by @bvijay74:
Extract the installer by running fxsound_setup.exe /extract
Once the files are extracted, you can verify the cab file signature by running
signtool verify /pa fxsound1.cab
Then run fxsound.x64.msi on 64 bit systems or fxsound.msi on 32 bit systems, to install FxSound.
Alternatively, you can try uninstalling the driver manually:
Since the FxSound driver can be removed with relative impunity, you could try performing a manual driver uninstall ;
Let me know if this helps.
Thank you. I tried the suggestions as best as I could and still have the same result. I wonder if there is something left in the registry that keeps this error coming that many others are having too. Unfortunately I am not a registry guru though I can find references to fxsound in the registry. I think that what I learned is that upgrading was not a good idea, I should have left well enough alone. Pity, I really liked the program.
1 Like
There was a similar thread posted yesterday.