02 July 2018 03:05 PM
USB Fault Code: 52, unsigned driver.
Please give us a signed driver.
02 July 2018 04:25 PM #1
The DUO driver for Windows 10 x64 is signed.
It may be that there is an older driver on your system.
Please make sure you fully remove the older driver and install the new one.
02 July 2018 05:21 PM #2
Thanks for the fast reply. I am able to replicate the fault:
- fresh install Windows 10 x64 latest updates as of this post, so version 1803 17134.137
- fresh DUO install using CL-DUO3D-INSTALL-18.104.22.168.exe
- plug in DOU, run dashboard, status indicated no DUO attached
- check Device Manager, see CL, see DUO with yellow icon, check with USB View, see DUO with error 52
- uninstall device with Device Manager
- unplug DUO, wait 30 seconds, plug back in
- Windows sees DUO Camera with yellow icon, install device in Device Manager pointing to .inf file from uncompressed installer CL-DUO3D-INSTALL-22.214.171.124\$PLUGINSDIR (DUO moves from being a camera to a CL device)
- During installation, fault code 48 pops up (see attached screenshot) indicating Microsoft has blocked a known driver known to have problems with Windows and to contact oem for a new driver etc.
That’s where it is with both systems now.
08 July 2018 09:55 AM #3
IF driver signing is disabled during boot (restart with advanced options), then Windows enables the driver. While I do see the driver signed, during install it is from an unknown publisher then later during a driver search, the driver is actively blocked as Windows identifies it as being potentially hostile. Something has gone awry in the signing process. Leaving the system device driver signing check disabled is to big a security hole to say that is viable.
08 July 2018 02:09 PM #4
Could you please share the screenshot during the install process showing that the driver is from unknown publisher?
We have tested the driver (DUO SDK v126.96.36.199 Setup) on the clean Windows 10 x64 1803 17134.137 install and unfortunately were not able to replicate the problem you are seeing. The drivers are signed by our code signing certificate that is valid. You can verify this by right-clicking on duodriver.sys file on your system and under ‘Digital Signature’ tab under Properties. Clicking on ‘Details’ will show that the digital certificate is valid.
08 July 2018 04:54 PM #5
Here you go and, as a bonus, an event file It is pretty sparse but may hopefully spark a thought. Oh, I did look for a registry value for upper/lower keys in USB class section to remove as that sometimes works but my Win10 doesn’t have that.
(placed several screenshots inside one image due to board attachment limitations and zipped a small event file as board rejected extension)[ Edited: 08 July 2018 04:56 PM by ToddKennard ]
23 January 2020 08:15 AM #6
We have the same problem with driver 188.8.131.52 on Windows 10 x64 1809. More, I can not disable verification of signature…
Using CertMgr.exe in installer directory (I unzip the exe installer), I have a window with the validity of certificate: from 4/3/2017, until 4/4/2018… Maybe it can help you.
Did someone find any solution ?
1 of 1 Pages