[Plesk90]

With secure boot disabled installation of the unmodified drivers with new fw 1.44 beta (DAC) went fine but still can't use the FiiO X3 II if secure boot is enabled

 

[Joe Bloggs]

With secure boot disabled installation of the unmodified drivers with new fw 1.44 beta (DAC) went fine but still can't use the FiiO X3 II if secure boot is enabled

Hello Plesk90,

Does the driver refuse to load if secure boot is enabled? What about if you install the stock 3.34 driver after a secure boot instead?

 

[Plesk90]

Same thing also with new fw 1.6 that should have fix the issue, I still get error 52 
stating that "Authentication code signature is not valid" 

 

[FiiO-Shadow]

  Same thing also with new fw 1.6 that should have fix the issue, I still get error 52 
stating that "Authentication code signature is not valid" 

 
Hi, Plesk90.
 
Your computer is running Windows 7? If so, you may need to disable the driver signature before the installation. Here is the instruction which can help you do that: click here. 
Any test result, kindly share with us.

 

[Plesk90]

I'm running Windows 10 x64 last insider build (build 14316 at the moment). I have problems only with FiiO DAC driver, all other drivers installation went just fine for both WHQL and not WHQL drivers. 

Btw at the moment I've disabled the secure boot as in any case the fast startup function that require secure boot is bugged since a few builds ago so I can use the DAC drivers, but if they will fix the fast startup problem I will re-enable secure boot and so I will be unable to use the DAC. 

Maybe something about driver verification has change since last Windows 10 stable build. 

Every time secure boot is enabled or I don't boot with driver verification signature disabled, Windows won't load the DAC drivers reporting error 52. 

 

[BetterLate]

Just upgraded to Windows 10 and trying to download new universal DAC driver - is Fiio site down or having problems? I am just getting continuous spinning wheel and the page doesn't come up.

 

[AndroidVageta]

  Just upgraded to Windows 10 and trying to download new universal DAC driver - is Fiio site down or having problems? I am just getting continuous spinning wheel and the page doesn't come up.

https://drive.google.com/open?id=0B5YWQ3E5PCkvS3lKcUxnTWVjYzg
 
This is an upload of the latest version. Hope this helps!

 

[Plesk90]

Is there anyone using FiiO X3 II with last DAC driver on Windows 10? 
On my notebook Windows won't load the drivers reporting error 52. I have to disable secure boot or boot every time with device driver signature verification disabled. 

I'm running Windows 10 last insider build. 

 

 

[BeatsWork]

  Is there anyone using FiiO X3 II with last DAC driver on Windows 10? 
On my notebook Windows won't load the drivers reporting error 52. I have to disable secure boot or boot every time with device driver signature verification disabled. 

I'm running Windows 10 last insider build. 

 

3.34 working fine with X5 Gen 2 on Win 10 64bit without disabling driver verification.

 

[Plesk90]

I know it but there are some problems with X3 II, FiiO has made a specific firmware update  v.1.6 to fix the compatibility issue with the new DAC driver but it didn't fix the problem for me.

 

[Plesk90]

Do you have any news about the compatibility problem with the X3 II? I think FiiO is still looking at the issue 

 

[FiiO-Shadow]

  Is there anyone using FiiO X3 II with last DAC driver on Windows 10? 
On my notebook Windows won't load the drivers reporting error 52. I have to disable secure boot or boot every time with device driver signature verification disabled. 

I'm running Windows 10 last insider build. 

 

 
Hi, Plesk90.
 
Thanks for your sharing the solution with us on FiiO forum.
 
"Please check on Windows update and install also the optional security updates. 

You need those updates in particular

https://www.microsoft.com/en-ca/download/details.aspx?id=46148

https://support.microsoft.com/en-ca/kb/3123479

https://support.microsoft.com/en-ca/kb/2921916

After the updates installation reboot and reconnect the player."
 

 

[Plesk90]

The solution above works only in Windows 7, on Windows 10 insider build there's probably some problem that have to be fixed by Microsoft before releasing the anniversary update as I have the same error 52 also from the last AMD display driver

 

[mehdikh423]

I installed driver in my pc windows 10 with disable driver signature but it work only 1 time..after i restarted my pc dont work at all!!

 

[Plesk90]

​You should try to disable secure boot option in the BIOS