Oops! There's an issue with you playback device settings

Get Help
1

i just factory resetted my pc and i downloaded fxsound for the first time and this shows up i already went to my sound settings and cant find a fxsound option to enable

image
image364×187 7.23 KB

2

Sorry about this. What version of FxSound are you running? Can you make sure you’ve got the latest version downloaded?

3

im using the latest one, i just got a fresh start on my pc.

4

@bvijay got any troubleshooting ideas?

5

Hi @ilovemysuad,
This error can occur only if the FxSound Audio Enhancer device could not be installed.
Can you please check device manager if FxSound Audio Enhancer device is listed in device manager as I have shown below,

image
image976×715 102 KB

If the device is not listed, or if any error is displayed on the device instance, please try re-installing FxSound.
If the device is not installed even after reinstalling FxSound please share the log file - "%SystemRoot%\inf\setupapi.dev.log,

6

Hi! I have a similar problem, I tried every support troubleshoot, I updated Windows, I completely removed FxSound drivers, uninstalled and reinstalled multiple times, but the device still gives the same yellow triangle, and error 52 in the drivers. I will write out my setupapi file because I can’t upload. I also checked the .\DfxSetupDrv.exe in terminal, and it just says “DFX driver not found”. What do I even do?
The FxSound setupapi part after reinstalling it the last time

[Device Install (UpdateDriverForPlugAndPlayDevices) - Root\FXVAD]
Section start 2025/01/29 11:59:34.631
cmd: “C:\Program Files\FxSound LLC\FxSound\Drivers\win7\x64\fxdevcon64.exe” install “C:\Program Files\FxSound LLC\FxSound\Drivers\win7\x64\fxvad.inf”
ndv: INF path: C:\Program Files\FxSound LLC\FxSound\Drivers\win7\x64\fxvad.inf
ndv: Install flags: 0x00000001
ndv: {Update Device Driver - ROOT\MEDIA\0004}
ndv: Search options: 0x00000080
ndv: Searching single INF ‘C:\Program Files\FxSound LLC\FxSound\Drivers\win7\x64\fxvad.inf’
dvi: {Build Driver List} 11:59:34.649
dvi: Searching for hardware ID(s):
dvi: root\fxvad
sig: {_VERIFY_FILE_SIGNATURE} 11:59:34.652
sig: Key = fxvad.inf
sig: FilePath = c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf
sig: Catalog = c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvadNTAMD64.cat
! sig: Verifying file against specific (valid) catalog failed.
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 11:59:34.684
sig: {_VERIFY_FILE_SIGNATURE} 11:59:34.684
sig: Key = fxvad.inf
sig: FilePath = c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf
sig: Catalog = c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvadNTAMD64.cat
sig: Success: File is signed in Authenticode™ catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode™ catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 11:59:34.699
dvi: Created Driver Node:
dvi: HardwareID - Root\FXVAD
dvi: InfName - c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf
dvi: DevDesc - FxSound Audio Enhancer
dvi: Section - DFX_Device.NT
dvi: Rank - 0x00ff0000
dvi: Signer Score - Authenticode
dvi: DrvDate - 03/22/2021
dvi: Version - 14.2.0.0
dvi: {Build Driver List - exit(0x00000000)} 11:59:34.701
dvi: {DIF_SELECTBESTCOMPATDRV} 11:59:34.701
dvi: Default installer: Enter 11:59:34.702
dvi: {Select Best Driver}
dvi: Class GUID of device changed to: {4d36e96c-e325-11ce-bfc1-08002be10318}.
dvi: Selected Driver:
dvi: Description - FxSound Audio Enhancer
dvi: InfFile - c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf
dvi: Section - DFX_Device
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 11:59:34.703
ndv: Force Installing Driver:
ndv: Inf Name - fxvad.inf
ndv: Driver Date - 03/22/2021
ndv: Driver Version - 14.2.0.0
sto: {Setup Import Driver Package: c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf} 11:59:34.705
inf: Provider: FxSound
inf: Class GUID: {4d36e96c-e325-11ce-bfc1-08002be10318}
inf: Driver Version: 03/22/2021,14.2.0.0
inf: Catalog File: fxvadNTAMD64.cat
sto: {Copy Driver Package: c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf} 11:59:34.708
sto: Driver Package = c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf
sto: Flags = 0x00000007
sto: Destination = C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}
sto: Copying driver package files to ‘C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}’.
flq: {FILE_QUEUE_COMMIT} 11:59:34.715
flq: Copying ‘c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvadNTAMD64.cat’ to ‘C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvadNTAMD64.cat’.
flq: Copying ‘c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.inf’ to ‘C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvad.inf’.
flq: Copying ‘c:\program files\fxsound llc\fxsound\drivers\win7\x64\fxvad.sys’ to ‘C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvad.sys’.
flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 11:59:34.722
sto: {Copy Driver Package: exit(0x00000000)} 11:59:34.722
ump: Import flags: 0x00000000
pol: {Driver package policy check} 11:59:34.736
pol: {Driver package policy check - exit(0x00000000)} 11:59:34.736
sto: {Stage Driver Package: C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvad.inf} 11:59:34.736
inf: Provider = FxSound
inf: Class GUID = {4d36e96c-e325-11ce-bfc1-08002be10318}
inf: Driver Version = 03/22/2021,14.2.0.0
inf: Catalog File = fxvadNTAMD64.cat
inf: Version Flags = 0x00000003
inf: {Query Configurability: C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvad.inf} 11:59:34.747
inf: Driver package ‘fxvad.inf’ is configurable.
inf: {Query Configurability: exit(0x00000000)} 11:59:34.753
flq: {FILE_QUEUE_COMMIT} 11:59:34.754
flq: Copying ‘C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvadNTAMD64.cat’ to ‘C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}\fxvadNTAMD64.cat’.
flq: Copying ‘C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvad.inf’ to ‘C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}\fxvad.inf’.
flq: Copying ‘C:\Users\Utente\AppData\Local\Temp{75dea123-bdc8-3a4e-96a8-73519deb97b3}\fxvad.sys’ to ‘C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}\fxvad.sys’.
flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 11:59:34.773
sto: {DRIVERSTORE IMPORT VALIDATE} 11:59:34.776
sig: Driver package catalog is valid.
sig: {_VERIFY_FILE_SIGNATURE} 11:59:34.788
sig: Key = fxvad.inf
sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}\fxvad.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}\fxvadNTAMD64.cat
! sig: Verifying file against specific (valid) catalog failed.
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 11:59:34.817
sig: {_VERIFY_FILE_SIGNATURE} 11:59:34.819
sig: Key = fxvad.inf
sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}\fxvad.inf
sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}\fxvadNTAMD64.cat
sig: Success: File is signed in Authenticode™ catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode™ catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 11:59:34.837
sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 11:59:34.849
sig: Signer Score = 0x0F000000 (Authenticode)
sig: Signer Name = FxSound, LLC
sto: {Core Driver Package Import: fxvad.inf_amd64_7cdb1634ab01cbd9} 11:59:34.850
sto: {DRIVERSTORE IMPORT BEGIN} 11:59:34.850
sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 11:59:34.850
cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp{8e9b246a-06d9-ec4c-aec8-4f211fc3509d}} 11:59:34.851
cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\fxvad.inf_amd64_7cdb1634ab01cbd9
cpy: {Copy Directory: exit(0x00000000)} 11:59:34.852
idb: {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\fxvad.inf_amd64_7cdb1634ab01cbd9\fxvad.inf} 11:59:34.856
idb: Created driver package object ‘fxvad.inf_amd64_7cdb1634ab01cbd9’ in DRIVERS database node.
idb: Created driver INF file object ‘oem116.inf’ in DRIVERS database node.
idb: Registered driver package ‘fxvad.inf_amd64_7cdb1634ab01cbd9’ with ‘oem116.inf’.
idb: {Register Driver Package: exit(0x00000000)} 11:59:34.857
idb: {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\fxvad.inf_amd64_7cdb1634ab01cbd9\fxvad.inf} 11:59:34.858
idb: Activating driver package ‘fxvad.inf_amd64_7cdb1634ab01cbd9’.
cpy: Published ‘fxvad.inf_amd64_7cdb1634ab01cbd9\fxvad.inf’ to ‘oem116.inf’.
idb: Indexed 3 device IDs for ‘fxvad.inf_amd64_7cdb1634ab01cbd9’.
sto: Flushed driver database node ‘DRIVERS’. Time = 0 ms
sto: Flushed driver database node ‘SYSTEM’. Time = 0 ms
idb: {Publish Driver Package: exit(0x00000000)} 11:59:34.866
sto: {DRIVERSTORE IMPORT END} 11:59:34.867
dvi: Flushed all driver package files to disk. Time = 5 ms
sig: Installed catalog ‘fxvadNTAMD64.cat’ as ‘oem116.cat’.
sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 11:59:34.877
sto: {Core Driver Package Import: exit(0x00000000)} 11:59:34.877
sto: {Stage Driver Package: exit(0x00000000)} 11:59:34.878
sto: {Setup Import Driver Package - exit (0x00000000)} 11:59:34.911
dvi: Searching for hardware ID(s):
dvi: root\fxvad
dvi: Class GUID of device changed to: {4d36e96c-e325-11ce-bfc1-08002be10318}.
ump: {Plug and Play Service: Device Install for ROOT\MEDIA\0004}
dvi: Install flags: 0x00010211
dvi: {Core Device Install} 11:59:34.932
dvi: {Configure Device - ROOT\MEDIA\0004} 11:59:34.933
dvi: Device Status: 0x01802001
dvi: Parent Device: HTREE\ROOT\0
sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\fxvad.inf_amd64_7cdb1634ab01cbd9\fxvad.inf} 11:59:34.935
sto: Source Filter = root\fxvad
inf: Config Options = IsolationCompat
inf: Class GUID = {4d36e96c-e325-11ce-bfc1-08002be10318}
inf: Class Options = Configurable
inf: {Configure Driver: FxSound Audio Enhancer}
inf: Section Name = DFX_Device.NT
inf: {Add Service: FXVAD}
inf: Flags = 0x2
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\system32\drivers\fxvad.sys
inf: Display Name = FxSound Audio Enhancer
inf: Updated service ‘FXVAD’.
inf: {Add Service: exit(0x00000000)}
inf: Hardware Id = Root\FXVAD
inf: Compatible Id = *FXVAD
inf: {Configure Driver Configuration: DFX_Device.NT}
inf: Service Name = FXVAD
inf: Included INFs = ks.inf
inf: wdmaudio.inf
inf: Include Scope = Services
inf: Config Flags = 0x00000000
inf: {Configure Driver Configuration: exit(0x00000000)}
inf: {Configure Driver: exit(0x00000000)}
flq: {FILE_QUEUE_COMMIT} 11:59:34.977
flq: Hardlinking ‘C:\WINDOWS\System32\DriverStore\FileRepository\fxvad.inf_amd64_7cdb1634ab01cbd9\fxvad.sys’ to ‘C:\WINDOWS\system32\drivers\fxvad.sys’.
cpy: Existing file ‘C:\WINDOWS\system32\drivers\fxvad.sys’ remains unchanged.
flq: Hardlinking ‘C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_7b6470789d81fb6c\drmk.sys’ to ‘C:\WINDOWS\System32\drivers\drmk.sys’.
cpy: Existing file ‘C:\WINDOWS\System32\drivers\drmk.sys’ remains unchanged.
flq: Hardlinking ‘C:\WINDOWS\System32\DriverStore\FileRepository\wdmaudio.inf_amd64_7b6470789d81fb6c\portcls.sys’ to ‘C:\WINDOWS\System32\drivers\portcls.sys’.
cpy: Existing file ‘C:\WINDOWS\System32\drivers\portcls.sys’ remains unchanged.
flq: {FILE_QUEUE_COMMIT - exit(0x00000000)} 11:59:34.988
sto: Driver configuration complete.
sto: {Configure Driver Package: exit(0x00000000)} 11:59:34.989
dvi: Install Device: Configuring device. 11:59:34.989
dvi: Configuration: oem116.inf:root\fxvad,DFX_Device
dvi: Install Device: Configuring device completed. 11:59:34.994
dvi: Device Status: 0x01802001
dvi: Install Device: Starting device ‘ROOT\MEDIA\0004’. 11:59:34.994
dvi: Install Device: Starting device completed. 11:59:35.005
!!! dvi: Device not started: Device has problem: 0x34 (CM_PROB_UNSIGNED_DRIVER), problem status: 0xc0000428.
dvi: {Configure Device - exit(0x00000000)} 11:59:35.006
dvi: {Core Device Install - exit(0x00000000)} 11:59:35.007
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Update Device Driver - exit(00000000)}
ndv: {Install Related Drivers} 11:59:35.014
ndv: {Install Related Drivers: exit(0x00000000)} 11:59:35.015
<<< Section end 2025/01/29 11:59:35.017
<<< [Exit status: SUCCESS]

1 Like
7

Hi @iwakiri
I see the error in digital certificate validation failure,
Are you installing on Windows 7?

Can you please install the certificate from the driver file.
From the installation folder, select fxvad.sys file properties,

image
image506×636 45.8 KB

Click Details,
image
image506×604 51.5 KB

Click View Certificate,
image
image506×644 65.4 KB

Click Install Certificate

8

Are you serious ?! , please renew the certificate , 2022 BRO

9

If the driver is signed with a timestamp, then the driver is still valid even if the certificate has expired.

1 Like
10

I’m installing on Windows 11! I noticed this problem too! Should I follow your process still?

11

Well mister,

it seem’s you don’t know what a valid signature of a driver mean ? and the potential of exploitation of the driver by any one ? Even the timestamp is valid, it mean’s the last time you have patched the driver could not be over the 01-09-2022 officialy.

If you want some detail, please have a seat and go see this link …

https://signmycode.com/blog/whats-the-difference-between-signed-and-unsigned-drivers

as it said : “The signing of a driver refers to the software going through a verification process and its integrity being confirmed. It stops malware injection or any code tampering that could be done by a hacker.”

have a signed driver as you told and put it on a sharing plateform without any garanty of a hash algorithm of the visible code of this driver (today we are on SHA 3) , is a high compromise of the legemity of your organisation, because anyone could inject code on this github plateform, and forget to see it, compromising all the computers who has install the software.

that is why it is bannish for me to install a driver with an expery date.

good luck to explain this to your followers !

just to inform you !

12

Thank you for sharing your knowledge from the blog.
Our Windows 7 and Windows 10 drivers are signed as per Microsoft defined driver signing policy,
Driver Signing Policy - Windows drivers | Microsoft Learn

image
image892×622 27.1 KB

You can verify the validity of the signed driver by running sigverifcommand which will verify all the driver installed on your PC, or by running
signtool verify /v /kp <driver file path>

Here is a link for you keep yourself educated on what is timestamping in codesigning.
What Is Timestamping in a Code Signing & What’s Its Importance?

13

Well, thanks …

but…

fxvad.sys 15-04-22 14.1.0.0 SignĂŠ fxvadntamd64.cat Microsoft Windows Hardware Compatibility Publisher

this is the last version you have, for an AMD X64 architecture (mine)

also please note , that people use now the stable Windows 11 24H2 , sha 2 algorythme signature is incompatible with the protected Mode enable !

" SHA-3 support

Support for the SHA-3 family of hash functions and SHA-3 derived functions (SHAKE, cSHAKE, KMAC) was added. The SHA-3 family of algorithms are the latest standardized hash functions by the National Institute of Standards and Technology (NIST). Support for these functions is enabled through the Windows CNG library.

  • Supported SHA-3 hash functions: SHA3-256, SHA3-384, SHA3-512 (SHA3-224 isn’t supported)
  • Supported SHA-3 HMAC algorithms: HMAC-SHA3-256, HMAC-SHA3-384, HMAC-SHA3-512
  • Supported SHA-3 derived algorithms: extendable-output functions (XOF) (SHAKE128, SHAKE256), customizable XOFs (cSHAKE128, cSHAKE256), and KMAC (KMAC128, KMAC256, KMACXOF128, KMACXOF256)."

So if someone temper your driver and sign in with a SHA 3 before you, i do not know what people will think next…

bye !

14

Ok, guess I’m going to uninstall FxSound then.

15

Windows 11 OS has added support for SHA-3, but the drivers should be signed with SHA-2 particularly because the drivers should be backward compatible with Windows 10.

When Microsoft revises the driver signing policy we will definitely update our driver and sign it according to the new signing requirements in a new release.

1 Like
16

Hey guys, I’ve seen where some of you are having this error message. I do get it too, once in a blue, and just earlier it popped up for me again. What should I do?

Screenshot 2025-02-11 101219
Screenshot 2025-02-11 101219645×673 123 KB

17

Hi @myFxSound,
I have made code changes in places where I suspected exceptions can occur. Will share a release soon which has the fixes.

1 Like