# Getting help with running Fxsound **URL:** \ **Category:** Get Help\ **Created:** [May 27, 2024, 12:44pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143 "2024-05-27T12:44:48Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Sam225](https://avatars.discourse-cdn.com/v4/letter/s/d78d45/32.png) [@Sam225](https://forum.fxsound.com/u/Sam225)\ **Post date:** [May 27, 2024, 12:44pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/1 "2024-05-27T12:44:48Z")
Hi guys I got a problem with running Fxsound on my old laptop running windows 7. Installed successfully (I think) I get this error ![image](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/b/b7b51a6db4efea343a44a7719857e3f9ac7fadd0.png) I changed the “Local Group Policy Editor” settings as well. (Code signing for device drivers) Not successful. ☹ Getting that infamous "Oops! There’s an issue with… " error. I would appreciate any help from you guys. Thank you Sam ---
**Author:** ![raddy](https://avatars.discourse-cdn.com/v4/letter/r/e0b2c6/32.png) [@raddy](https://forum.fxsound.com/u/raddy)\ **Post date:** [May 27, 2024, 1:00pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/2 "2024-05-27T13:00:35Z")
> [@Sam225](#): > > I would appreciate any help from you guys. You need to install some updates for SHA-2 code sign support. > **[2019 SHA-2 Code Signing Support requirement for Windows and WSUS - Microsoft...](https://support.microsoft.com/en-us/topic/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus-64d1c82d-31ee-c273-3930-69a4cde8e64f)** > > 2019 SHA-2 Code Signing Support requirement for Windows and WSUS. ---
**Author:** ![raddy](https://avatars.discourse-cdn.com/v4/letter/r/e0b2c6/32.png) [@raddy](https://forum.fxsound.com/u/raddy)\ **Post date:** [May 27, 2024, 1:03pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/3 "2024-05-27T13:03:05Z")
> [@Sam225](#): > > I changed the “Local Group Policy Editor” settings as well. > (Code signing for device drivers) Don’t use gpedit, if you don’t understand what you are doing. ---
**Author:** ![Sam225](https://avatars.discourse-cdn.com/v4/letter/s/d78d45/32.png) [@Sam225](https://forum.fxsound.com/u/Sam225)\ **Post date:** [May 27, 2024, 1:18pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/4 "2024-05-27T13:18:02Z")
Hey @raddy Thank you man. I edited “gpedit” because it has mentioned on one of these threads. I will keep that on mind. Let me get back to you with the update 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:** [May 27, 2024, 3:34pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/5 "2024-05-27T15:34:04Z")
Hi Sam, welcome to the forum. When did you download the program, from what source, and which version? Installing the latest version - currently **v1.1.22.0** - is always recommended. Besides a regular Control Panel uninstall, you can also remove the driver from Device Manager manually if necessary; the instructions on that are linked [here](https://forum.fxsound.com/t/echo-due-to-fx-and-the-original-playback-device-playing-at-the-same-time/2112/2). The solution offered by @bvijay under the fourth category of the issue linked below also seems worth a try: > > > \*\*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: > !\[Settings file not found\](https://github.com/fxsound2/fxsound-app/assets/151672060/3eded61f-3414-4fd5-a3ff-87a74a81c103) > > 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: > !\[Source file not found\](https://github.com/fxsound2/fxsound-app/assets/151672060/e9c14a0c-b3a8-438f-9166-4d26dce4d05a) > > 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." > !\[Invalid digital signature\](https://github.com/fxsound2/fxsound-app/assets/151672060/22dee529-ece0-4f6d-ad6f-6945d78a0514) > > 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. ---
**Author:** ![raddy](https://avatars.discourse-cdn.com/v4/letter/r/e0b2c6/32.png) [@raddy](https://forum.fxsound.com/u/raddy)\ **Post date:** [May 27, 2024, 3:52pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/6 "2024-05-27T15:52:48Z")
> [@doolhoofd](#): > > The solution offered by @bvijay under the fourth category of the issue linked below also seems worth a try: add this to the list of solutions, if you really want to help: > [@Driver problem win7](https://forum.fxsound.com/t/driver-problem-win7/2395/3): > > If installing the latest version does not help, check for OS updates. Support for SHA1 (file signature format, including drivers) has been discontinued and certificates are no longer issued. FxSound uses the current SHA-256 format, so Windows 7 requires updates to SHA-2 (sha-256). Here is some supporting information: [https://support.microsoft.com/topic/10b58bd9-5ba2-b23d-498b-139ce5c709af](https://support.microsoft.com/topic/10b58bd9-5ba2-b23d-498b-139ce5c709af) > > > **Information from another major developer** > > > > The Microsoft security updates that support SHA-256 must be inst… ---
**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 27, 2024, 4:32pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/7 "2024-05-27T16:32:54Z")
> [@raddy](#): > > add this to the list of solutions, if you really want to help: > > > \*\*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: > !\[Settings file not found\](https://github.com/fxsound2/fxsound-app/assets/151672060/3eded61f-3414-4fd5-a3ff-87a74a81c103) > > 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: > !\[Source file not found\](https://github.com/fxsound2/fxsound-app/assets/151672060/e9c14a0c-b3a8-438f-9166-4d26dce4d05a) > > 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." > !\[Invalid digital signature\](https://github.com/fxsound2/fxsound-app/assets/151672060/22dee529-ece0-4f6d-ad6f-6945d78a0514) > > 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. ![frodo-its-done](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/c/c81fe8e895c0769164dfa5d33cab7e787472d890.gif) ---
**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 28, 2024, 11:55pm UTC](https://forum.fxsound.com/t/getting-help-with-running-fxsound/3143/8 "2024-05-28T23:55:41Z")
> [@Sam225](#): > > I would appreciate any help from you guys. Sam, If it’s not too much to ask, could you look in: _C: \> Program Files \> FxSound LLC \> FxSound_ And check the “Digital Signatures” tab in the Properties of FxSound.exe? I might be wrong, but I’m guessing this would provide certainty on the certificate issue regarding SHA-1 / SHA-2. ![SHA-256](https://canada1.discourse-cdn.com/flex030/uploads/fxsound/original/2X/d/d04380212b0a9a511de187d30767f8a7f7fc2f44.png)