Reputation: 10284
OK, I am working on developing a USB device. I have created a custom windows driver for the device based on a pre-made Windows driver from my MCU manufacturer. The driver works fine on Windows XP, and Windows 7 (32-bit), BUT on my Windows 7 64-Bit machine, it will not let me use the driver. The driver will install just fine but when i go to the driver properties (in device manager) it says "This driver is not digitally signed by Microsoft" and it will not let me use it. I REALLY don't want to pay 100's of dollars to Microsoft and hours of time to get this driver certified (for several reasons). Is there any way I can get around this other than telling my customers to go back to XP??? PLEASE HELP!
Upvotes: 1
Views: 962
Reputation: 13018
You don't have to submit your drivers for WHQL certification. Microsoft only demands that your code is signed with a digital certificate. You can choose where you buy the certificate, GoDaddy sells them for 179 $ per year.
EDIT: Microsoft has a deal with Verisign: first year for 99$. https://winqual.microsoft.com/help/default.htm#obtaining_a_verisign_class_3_digital_id.htm
Upvotes: 3
Reputation: 59983
For testing purposes, you can enable the test certificate and self-sign the driver.
To actually release it in the wild, it needs to be digitally signed to run on 64-bit systems, and there's no way around this. What are your reasons for not wanting to go through the signinf process?
Upvotes: 1