To enquire about special prices for existing customers please contact us directly [email protected]
Getting your driver signed by Microsoft has become more than a routine checkpoint, it’s now a major hurdle. Recent changes by Microsoft have significantly increased the complexity of the driver signing process. What once took hours now often spans weeks, involving unclear instruction, conflicting documentation, opaque errors and the dreaded Microsoft Partner Center.
Microsoft enforces that all kernel-mode drivers be submitted to the Windows Hardware Developer Center (WHDC) for signing and validation. Additionally, to pass attestation signing, developers must now comply with an ever growing list of Windows HLK (Hardware Lab Kit) tests. Even minor updates to a driver often require full re-submission and re-certification.
For organizations with limited driver certification expertise, this process consumes precious engineering time and opens the door to costly mistakes and launch delays.
Required for Windows Kernel Drivers: Microsoft mandates digital signatures for kernel-mode drivers to load on modern versions of Windows (starting with Windows 10 version 1607 and onward).
Prevents Driver Installation Failures: Unsigned drivers are blocked during installation by Windows Defender, leading to errors or system warnings.
Proves Code Authenticity: A digital signature verifies that the driver came from a trusted source and hasn’t been tampered with since it was signed.
Enables Secure Boot Compatibility: Secure Boot environments will reject drivers without a valid Microsoft signature, making signing essential for enterprise deployment.
Improves User Trust and IT Compliance: Digitally signed drivers are less likely to be flagged as malware, improving user experience and meeting organizational security policies.
Starting with the release of Windows 10, all new kernel mode drivers for this OS must be submitted to and digitally signed by the Windows Hardware Developer Center Dashboard portal in order to be installed on Windows 10/11 PCs
Windows 10/11 will not load new kernel mode drivers which are not signed by the portal. The portal will only accept driver submissions, including both kernel and user mode, that have a valid Extended Validation (“EV”) Code Signing Certificate. All drivers running on 64-bit versions of Windows must be signed before Windows will load them. In order to sign a driver, an EV certificate and an attestation signing are required. For a public release you must sign your driver with a certificate issued by a trusted root authority.
$7,450
$5,199
$12,450
$10,399
The Certification Gauntlet: Microsoft mandates that all kernel-mode drivers be submitted to the Windows Hardware Developer Center (WHDC) for signing and validation. Furthermore, to achieve even attestation signing, developers must now comply with an expanding list of Windows HLK (Hardware Lab Kit) tests. Even minor driver updates frequently necessitate a complete re-submission and re-certification.
The Cost of Complexity: For organizations with limited driver certification expertise, this intricate process consumes valuable engineering time, leading to costly mistakes and potential launch delays.
Our Expertise – Your Solution: Our deep expertise is rooted in WinDriver, our comprehensive driver development toolkit that generates WDM/KMDF drivers for USB and PCI. We have been certifying these drivers for over 20 years. Beyond this, we can assist in establishing HLK testing environments for other HLK-supported protocols, such as NDIS and potentially any HLK-supported framework.
Navigating Microsoft’s Driver Signing Labyrinth: The process of getting your driver signed by Microsoft has evolved from a routine step to a significant hurdle. Recent changes by Microsoft have dramatically increased the complexity, transforming what once took hours into a weeks-long endeavor. This extended timeline is often due to unclear instructions, conflicting documentation, opaque errors, and the complexities of the Microsoft Partner Center.
IMPORTANT – READ CAREFULLY: THIS SOFTWARE LICENSE AGREEMENT (“AGREEMENT”) IS A LEGAL AGREEMENT BETWEEN YOU AND JUNGO CONNECTIVITY LTD. (“JUNGO”), FOR THE WINDRIVER SOFTWARE PRODUCT ACCOMPANYING THIS LICENSE (THE “SOFTWARE”). BY INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE, YOU AGREE TO BE LEGALLY BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT INSTALL, COPY, OR OTHERWISE USE THE SOFTWARE.
– Individuals: Jungo grants you, as an individual, a personal, non-exclusive, “single-user” license to use the Software on a single computer, in the manner provided below, at the site for which the license was given.
– Entities: If you are an entity, Jungo grants you the right to designate one individual within your organization (and only one) to have the right to use the Software on a single computer, in the manner provided below, at the site for which the license was given.
– License Scope: A single user license allows usage of WinDriver and redistribution of certain components (as defined below) within a single end product SKU, for a single device (identified by its VID/PID (USB) or VID/DID (PCI)), and without SDK/API capabilities. If you need extended license or distribution rights, please contact Jungo.
RESTRICTIONS ON USE AND TRANSFER
(a) You may not distribute, or otherwise transfer or assign, any portion of the Software, including any of the headers or source files that are included in the Software, unless otherwise expressly permitted in this Agreement, subject to the provisions of Section 4 above.
(b) Subject to your full and continued compliance with the terms of this Agreement, including the ongoing payment of annual license fees, you may distribute the following files:
Windows:
-windrvr1640.sys
-windrvr1640_legacy.sys
-windrvr1640.inf
-windrvr1640.cat
-wdapi1640.dll
-wdapi1640_32.dll
-wdapi1640_arm64.dll
-wdapi_dotnet1640.dll
-wdapi_dotnet1640_32.dll
-wdapi_netcore1640.dll
-wdapi_java1640.dll
-wdapi_java1640.jar
-wdreg.exe
-difxapi.dll
-devcon.exe
-windrvr1630.sys
-windrvr1630.inf
-wd1630.cat
-wdapi1630.dll
-wdapi_dotnet1630.dll
-wdapi_java1630.dll wdapi_java1600.jar
-windrvr1220.dll
-wdapi1220.dll
Linux:
-windrvr_gcc_v3.o_shipped
-windrvr_gcc_v3_regparm.o_shipped
-kp_linux_gcc_v3.o
-kp_linux_gcc_v3_regparm.o
-libwdapi1640.so libwdapi1640_32.so
-libwdapi_java1640.so
-libwdapi_java1640_32.so
-wdapi_java1640.jar
-wdapi_netcore1640.dll
-kp_wdapi1640_gcc_v3.o_shipped
-kp_wdapi1640_gcc_v3_regparm.o_shipped
-linux_wrappers.c
-linux_wrappers.h
-wdusb_linux.c
-wdusb_interface.h
-wd_ver.h
-linux_common.h
-windrvr.h
-windrvr_usb.h
-wdsriov_interface.h
-wdsriov_linux.c
-wdreg
-configure makefile.in
-configure.wd makefile.wd.in
-makefile.wd.kbuild.in
-configure.usb
-makefile.usb.in
-makefile.usb.kbuild.in
-setup_inst_dir
-windrvr_gcc_v2.a windrvr_gcc_v3.a windrvr_gcc_v3_regparm.a
-kp_linux_gcc_v2.o kp_linux_gcc_v3.o kp_linux_gcc_v3_regparm.o
-libwdapi1630.so
-libwdapi_java1630.so wdapi_java1600.java
-kp_wdapi1630_gcc_v2.a kp_wdapi1600_gcc_v3.a kp_wdapi1600_gcc_v3_regparm.a
-linux_wrappers.c linux_wrappers.h wdusb_linux.c
-wdusb_interface.h wd_ver.h linux_common.h windrvr.h windrvr_usb.h
-configure.wd makefile.wd.in makefile.wd.kbuild.in
-configure.usb makefile.usb.in makefile.usb.kbuild.in
macOS:
-libwdapi1640.dyld
-libwdapi_java1640.jar
-libwdapi_java1640.dyld
-wdapi_netcore1640.dll
-WinDriver1640.kext
-WinDriver1640.dext
-wd_mac_install.sh
-wd_mac_uninstall.sh
(c) The files listed in Section 5.b above may be distributed only as part of a complete application that you distribute under your organization name, and only if they significantly contribute to the functionality of your application. For avoidance of doubt, each organization distributing these files as part of the organization products is required to have valid license(s) under the organization name/VID, irrespective of the party who actually performed the product development. Licenses granted to subcontractors do not grant distribution or other rights to the organizations for which they are developing.
(d) The distribution of the windrvr.h header file is permitted only on Linux.
(e) You may not modify the distributed files specified in Section 5.b of this Agreement.
(f) You may not distribute any header file that describes the WinDriver functions, or functions that call the WinDriver functions and have the same basic functionality as that of the WinDriver functions.
Web site: https://www.jungo.com
Email: [email protected]
Use, duplication, or disclosure by the Government is subject to restrictions set forth in subparagraph (c)(1) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1)(ii) and (2) of Commercial Computer Software – Restricted Rights at 48 CFR 52.227-19, as applicable.