Windows 10: I have a signed driver with custom INF file for customized USB device. How do i get signed...

I have a signed Win7/Win10 driver with custom INF file for customized USB device, a very common Cypress USB 2.0 HS chip. How do i get signed for Win 11?I go in endless circles about how to do this. I would frankly be willing to pay a partner to help, but unable to connect with anyone. Microsoft won't even answer questions because i don't have a support subscription?!?Anyone been through this BS?Thanks,Ron

:)

 

Mass Storage Class stops working when VID/PID is added to custom INF file

We have developed a device that has a USB port for communication with a PC. The firmware for this device references the DeviceInterfaceGUID that is specified in the custom INF file of the USB driver on the PC. The firmware also has code that transfers data files between the PC and itself over the USB port by using the Mass Storage Class.



The USB driver on the PC follows the instructions given at WinUSB (Winusb.sys) installation for developers - Windows drivers | Microsoft Learn in the section labeled “Writing a custom INF for WinUSB installation”.



When the custom INF file does not specify the vendor identifier (VID) and product identifier (PID) for the device then everything works fine. Both USB communication and transferring files between the device and the software on the PC work fine. The Device Manager, on the Driver tab, shows the driver to be: Provider = Microsoft, Date = 6/21/2006, Version = 10.0.19041.1, Signer = Microsoft Windows.



However, when the custom INF file is modified to specify the vendor identifier (VID) and product identifier (PID) for the device then only USB communication works, but transferring files does not. The device’s file system does not show up in Windows Explorer as a mapped drive any longer. The Device Manger does show the proper custom information on the Driver tab now, which is why the custom INF file was modified.



What do we need to do so that our device can communicate with our software over USB, transfer files over USB using the Mass Storage Class and display the proper custom driver information on the Driver tab in Device Manager?

 

Device Driver Signing on Windows 10

It's due to the fact the driver was sigend with a SHA1 code signing certicate. As of July 2019 Windows does not trust SHA1 code signing certificates.

Even if Windows still trusted SHA1 certificates out of the box, a certificate signed in 2016, would not be explictly trusted due to expiration of said certificate.

You can either add the certificate to your trusted certificate store or disable driver signature enforcement all together. I do not suggest you disable the enforcement of signed drivers.

Source: Preparing for the deprecation of SHA-1 signatures

 

Need support for signing the Custom FTDI CDM Driver in order to install it in Windows 10

Hi there,

Take a look at this article this should take you through the steps you need to get your custom driver signed

https://docs.microsoft.com/en-us/windows-hardwa...

Let me know if this doesn't help