Skip to end of banner
Go to start of banner

Device Manager error (Code 52) with cifx Driver V1.3.0.0 or above

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

This problem could have different reasons and depends on the used Windows operating system

Windows XP / Vista / 7 / 8.x

Note: This poblem is only related the 64Bit versions of the Windows, because these versions only allow to install kernel drivers which are signed by the publisher of the driver.

Hilscher uses a new code signing certificate for their Windows kernel driver NXDRVWIN since V1.3.0.0.
The new certificate uses SHA-2 algorithm as Microsoft is phasing out SHA-1 code signing certificates starting on January 1, 2016.

Installing a driver signed by this new type of certificate may lead (depending on your Windows operating system version) to flag cifX Devices in Windows Device Manager with an error (Code 52):

"Windows cannot verify the digital signature for the drivers required for this device. ..."

Solution

Note: The KB fix must be installed before installing the driver.

    • Users of Windows 7 should check if KB3033929 is installed.
      The fix can be downloaded under the following link: https://technet.microsoft.com/en-us/library/security/3033929.aspx
    • Users of Windows 8.x should execute a "Windows Update".
    • Users of Windows XP 64Bit and Windows Vista 64Bit must update their Windows system to Windows 7 or later,
      because Microsoft does not offer any upgrades to support the new type of ceritificates.

Windows 10 - 1607 and later

Microsoft has changed the signiture checking inside of WIndows.
If the PC BIOS is set to "SECURE Boot", Microsoft only allows to install driver which are signed by Microsoft.

This may lead to flag cifX Devices in Windows Device Manager with an error (Code 52):

"Windows cannot verify the digital signature for the drivers required for this device. ..."

Solution

    • The ONLY way to solve this problem is to DEACTIVATE "SECURE Boot" in the PC BIOS.

Note

    • We are working on an update of the driver signiture but therefore a new Code Signing Certificate is necessary and
      the signing proceedure hat to be changed.
      As soon as we have setup this new proceedure we will offer an updated driver and this should be done until 07/2017.


  • No labels