- #VALIDITY FINGERPRINT SENSOR DRIVER WINDOWS 8.1 DRIVERS#
- #VALIDITY FINGERPRINT SENSOR DRIVER WINDOWS 8.1 UPDATE#
- #VALIDITY FINGERPRINT SENSOR DRIVER WINDOWS 8.1 MANUAL#
For example, a file could be excluded in the inf configuration file that is checked for the signature. Obtaining the biometric signature is not certification that the driver will work with Windows Hello. Microsoft will approve the submission provided it meets all Biometric requirements Step Seven: Wait for Microsoft approval and signing The team will review the submitted template in the HLK package to make sure the self-validated information meets the Microsoft’s biometric requirements.
#VALIDITY FINGERPRINT SENSOR DRIVER WINDOWS 8.1 MANUAL#
The feature team within Microsoft will be notified of the submission when it reaches the manual review process. Submit the packaged HLK file to DevCenter for review. Step Six: Submit the driver package and HLK logs When packaging the final HLK in HLK studio include the security review template submitted in the bug as a supplemental file. The HLK tests will make sure the above modifications have been made in steps 3 and 4 and will fail if the configurations information is not there. All third party biometric adaptor files and any third party dlls loaded by these adaptors will need to be labeled and included in this manner if they are to obtain the biometric signature when submitted to DevCenter. This step is the most important to making sure your driver receives the proper certification. Stringparser.dll = SignatureAttributes.WindowsHello Storage.dll = SignatureAttributes.WindowsHello Sensor.dll = SignatureAttributes.WindowsHelloĮngine.dll = SignatureAttributes.WindowsHello The following example demonstrates the formatting to obtain the bio signature on adaptor binaries and their related libraries.įor example, if the driver package contained a sensor, engine, and storage adaptor named sensor.dll, engine.dll, and storage.dll respectively, and one loaded stringparser.dll, then to obtain the bio signature on each one, the INF file would have to include the following components: Packages will need to include specific properties in the driver INF file to properly specify the adaptor dll's obtaining the digital signature. Step Four: Modify the driver configuration infīiometric driver packages will need to be submitted to the new DevCenter portal to obtain the required Windows Hello signature and be uploaded to WU.
#VALIDITY FINGERPRINT SENSOR DRIVER WINDOWS 8.1 UPDATE#
UpdateExistingSubmission: true if the submission serves as an update to a previous submission that has undergone the security review and false if otherwise. When you submit your driver, the Windows 10, version 1703 Fingerprint HLK test will check to ensure that the and tag are included with the following fields:īugId: ID number for the previous HLK submission that contains the previously approved security review information or 0 if the submission is undergoing an entirely new security review.
Step Three: Modify the driver configuration xml file If you do not have access to Connect, contact your Microsoft representative. Documents for the requirements and template can be found within the Fingerprint partner package on Connect. Self validate the sensor and driver to ensure they meet Microsoft’s biometric requirements and report findings in the Fingerprint Security Review Template. Step One: Create a biometric driverįollow the instructions here to create a biometric driver: Windows Biometric Framework Step Two: Test your sensor and self-validate
#VALIDITY FINGERPRINT SENSOR DRIVER WINDOWS 8.1 DRIVERS#
The biometric signature enforcement date is, after which drivers that do not contain the bio signature will not be loaded and will no longer work with Windows Hello. Drivers must undergo a new review if it applies to a new sensor, or if changes to the matching engine have occurred that impact FAR, FRR, or presentation attack detection. Updates to approved drivers can refer to previous submissions for faster approval. New and updated drivers that do not obtain this signature after this date will not work with Windows Hello in Window 10, version 1703 or later after the enforcement date.Ī driver will always undergo manual approval to obtain the Windows Hello signature. Drivers that have been created and signed by WHQL before 6/1/17 are grandfathered. The process will be enforced with an OS check for a specific signature obtained through the Windows Partner Center that can only be obtained by undergoing the process in this document. A new manual review process will be necessary to gain approval to interoperate with Windows Hello. Microsoft has introduced new requirements on biometric sensors to comply with Windows Hello quality guidelines. In this article Submitting a fingerprint driver for Windows Hello compatibility