Download biometrics for windows 10 for free. System Utilities downloads - Validity Fingerprint Driver by Validity Sensors, Inc. And many more programs are available for instant and free download. / USB Biometric Device. USB Biometric Device. LET'S STAY IN TOUCH Get updates on sales and more. Leave this field empty if you're human. IriShield-USB MK 2120U / MO2120 / MO 2121/ BK 2121U / BO 2121 IriShield-USB Serial supports USB Interface, Security Infrastructure, and various OS such as Windows family, Linux family, WinCE, Embedded Linux, and Android. Capture Distance. 4.7 cm - 5.3 cm (1.8 inches -2.1 inches) from the image sensor. Provide the named sections referred to in the.HW section. The BiometricDeviceAddReg section sets values for the biometric device, including the exclusive flag and system wake/device idle. To be recognized by Windows Biometric Framework, UMDF-based WBDI drivers must set the 'Exclusive' value to 1.
-->This section describes the tasks that you must complete before you test a fingerprint reader by using the Windows Hardware Lab Kit (Windows HLK):
Hardware requirements.
Software requirements.
Test computer configuration.
Hardware requirements
The following hardware is required for testing a fingerprint reader. You might need additional hardware if the test device offers other features. To determine whether additional hardware requirements apply, see the test description for each test that appears for the device in Windows HLK Studio.
One test computer. The test computer must meet the Windows HLK prerequisites. For more information, see Windows HLK Prerequisites.
The fingerprint reader to be tested.
One certified USB 2.0 hub if the fingerprint reader is a USB-based device.
Note
To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. You do not need a computer that actually has more than 64 processors to test your device. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. For more information see Windows Server Installation Options.
If you use a pool of test computers to test devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. As long as the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers.
For tests that do not include a driver to test, such as hard disk drive tests, the Windows HLK scheduler constrains the tests that validate the device's and driver's Rebalance, D3 State and Multiple Processor Groups functionality to run on the default test computer. You must manually configure this computer to have multiple processor groups. The default computer is the first test computer in the list. Test personnel must make sure that the first test computer in the list meets the minimum hardware requirements.
Note
Except for para-virtualization drivers (as defined by the WHCP Policies and Processes document), you may not use any form of virtualization when you test physical devices and their associated drivers for server certification or signature. All virtualization products do not support the underlying functionality that is required to pass the tests that relate to multiple processor groups, device power management, device PCI functionality, and other tests.
Note
Multiple Processor Groups SettingYou must set the value for the processor group size for Hardware Lab Kit testing of Windows Server 2008 R2 and later device drivers for certification. This is done by running bcdedit in an elevated command prompt window, using the /set option.
The commands for adding the group settings and restarting are as follows:
The commands for removing the group settings and rebooting are as follows:
Note
Code Integrity Setting
The Virtualization Based Security feature (VBS) of Windows Server 2016 must be enabled using Server Manager first.
Once that has occurred, the following Registry key must be created and set:
Software requirements
The following software is required for testing a fingerprint reader:
The drivers for the test device.
The latest Windows HLK filters or updates.
Test computer configuration
To configure the test computer for your test device, follow these steps:
Install the appropriate Windows operating system on the test computer, and then configure the computer for your test network (the network that contains the Windows HLK Studio and Windows HLK Controller.
If the test device is connected through the USB port, connect the USB 2.0 controller to the high-speed USB 2.0 hub, and then connect the test device to the downstream port of the high-speed USB 2.0 hub.
Note
Do not connect the USB test device directly to the root hub of the USB 2.0 controller.
Attach the fingerprint reader to the test computer.
If you have to install the manufacturer-supplied device driver on the test computer, do this now.
Check that the fingerprint reader functions correctly on the test computer.
Install the Windows HLK client application on the test computer.
Use Windows HLK Studio to create a machine pool, and then move the test computer to that pool.
Create test directory [SYSTEMDRIVE]FingerprintReaderTest.
Copy the adapter DLLs from [SYSTEMDRIVE]WindowsSystem32WinBioPlugins for the sensor, storage, and engine adapters.
Create configuration files for the sensor, storage, and engine adapters using the following templates.
Edit the sensorAdapterLib, engineAdapterLib, and storageAdapterLib configuration tags to point to correct adapter DLLs as copied previously.
Edit the supportedModes and supportedPurposes configuration tags to match the device capabilities.
The runOptional attribute is false by default. Change it to true to run extra tests.
For storage tests, change the deviceRequired attribute to true if the device has onboard storage.
Make sure that the test computer is in the ready state before you begin your testing. If a test requires parameters to be set before it is run, a dialog box will be displayed for that test. Review the specific test topic for more information.
Some Windows HLK tests require user intervention. When running tests for a submission, it is a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting completion of an automated test.
Before running any fingerprint reader driver or adapter tests, stop and disable the Windows Biometric Service. If the biometric service is running while the fingerprint reader HLK tests execute, there may be a conflict between the two, and test results will not be accurate.
Writing test configuration files
Before running any fingerprint reader adapter tests, you need to create XML configuration files for the sensor, storage, and engine adapters. The names of these files must be SensorTestConfig.XML, EngineTestConfig.XML, and StorageTestConfig.XML. Use the templates below as a starting point and modify them for your specific device.
Sensor Adapter configuration file
Engine Adapter configuration file
Storage Adapter configuration file
Additional configuration tags
In the configuration file, under the 'device information' section, there are three additional tags:
badSwipeDetectionPoint
SensorFinishCapture
EngineAcceptData
EngineProcessData
Note
A maximum of one badSwipeDetectionPoint tag can appear in a single test configuration file.
privateConnectionSensorToEngine
If TRUE, this indicates that there is an internal connection between the sensor and the engine components that is not managed by the WinBio Framework.
If FALSE, the connection between the sensor and engine uses the standard WinBio adapter interfaces.
privateConnectionEngineToStorage
If TRUE, this indicates that there is internal connection between the engine and storage components that is not managed by the WinBio Framework.
If FALSE, the connection between the engine and storage uses the standard WinBio adapter interfaces.
Note
For a compound device, it's possible to set both the privateConnectionSensorToEngine and privateConnectionEngineToStorage.
engineOnDevice
If TRUE, this indicates that the fingerprint sensor supports the engine functionality in hardware. This typically implies that the sensor is an advanced sensor.
If FALSE, this indicates that the fingerprint sensor supports the engine functionality in software. This typically implies that the sensor is a basic sensor.
storageOnDevice
If TRUE, this indicates that the fingerprint sensor supports template storage in hardware. This typically implies that the sensor is an advanced sensor.
If FALSE, this indicates that the fingerprint sensor does not support template storage in hardware. Templates are stored on disk. This typically implies that the sensor is a basic sensor.
The modern Windows 10 PCs come equipped with Windows Hello. It allows the users to unlock their PC using fingerprint or facial recognition. However, while setting up Windows Hello Face and Fingerprint, you may encounter the face and fingerprint that are not available on this device error.
The full error reads:
“This option is currently unavailable” “Something went wrong- try again later”.
“Windows Hello is preventing some options from being shown.”
This error is usually triggered by an outdated biometric device driver. However, there can be other reasons as well.
In this article, we have listed a couple of troubleshooting tips to help you resolve the Windows Hello face and fingerprint are not available on this device error in Windows 10.
Steps to fix face and fingerprint are not available on this device
Before proceeding with the troubleshooting tips, make sure your Windows laptop supports Windows Hello. Refer your laptop manual or visit the official website to check if the device supports Windows Hello.
1. Update Biometric drivers
One common reason behind this error is outdated or corrupted biometric device drivers. To fix the problem, update the necessary drivers.
- Press Windows Key + R.
- Type devmgmt.msc and click OK to open Device Manager.
- In Device Manager, expand the Biometric Devices category.
- Right-click on the Biometric device and select Update Driver.
- Select ‘Search automatically for updated driver software’ option.
- Windows will now scan and download any pending updates for the biometric device.
- If you have multiple biometric devices, make sure to update all of them.
- Additionally, update your webcam drivers as well.
- Once the update is installed, restart your computer.
Lenovo, Dell, and HP laptops come with a proprietary application that allows you to download and update drivers. For example, the Lenovo laptops come with the Lenovo Vantage application using which you can download and install any pending update for the device.
Alternatively, you can also manually install the drivers from the laptop Dell, HP, and Lenovo website.
2. Update Windows
If the problem is occurring on a newly purchased system, try installing Windows updates. The new system usually comes with an older version of updates and lack compatible drivers.
- Click on Start and select Settings.
- Go to Update & Security.
- Check for any pending updates.
- If found, download and install all the essential updates.
- Restart your PC and check if the face and fingerprint are not available on this device problem is resolved.
3. Disable third-party facial recognition / fingerprint option
By default, your laptop may have a proprietary facial recognition and fingerprint sensor software installed out of the box. HP laptop comes installed with HP Client Security, and Lenovo laptops come with Lenovo Fingerprint Software.
Windows Hello may not function correctly if third-party security software is enabled. Disable any third-party security software to fix the issue.
Drivers Ekey Biometric Usb Devices 3.0
4. Allow the use of Biometrics in Group Policy Editor
- Press Windows Key + R.
- Type Gpedit.msc and click OK.
- In Group Police editor, navigate to Computer Configuration > Administrative Templates > Windows Components > Biometrics.
- Right-click on Allow the use of Biometrics and select Edit.
- Select the Enabled option.
- Click Apply > OK to save the changes.
- Close Group Policy Editor and check for any improvements.
Drivers Ekey Biometric Usb Devices Device
If the issue persists, try disabling Enhanced anti-spoofing.
- Open Group Policy Editor.
- Navigate to Computer Configuration > Administrative Templates > Windows Components > Biometrics.
- Double-click on Facial Features.
- Right-click on Configure enhanced anti-spoofing.
- Select Disabled.
- Click Apply > OK to save the changes.
5. Reset Facial Recognition
Drivers Ekey Biometric Usb Devices Wireless
Incorrect configuration or incomplete setup can result in the face and fingerprint are not available on this device error. Try resetting the facial recognition or fingerprint sensor option.
- Press Windows Key + I to open Settings.
- Click on Accounts.
- Select Sign-in options.
- Click on Windows Hello Face or Windows Hello Fingerprint.
- Click the Remove button.
- Once removed, click on the Get Started or Setup option.
- Follow on-screen instructions to set up Windows Hello.
- Restart your computer to apply the changes.
6. Uninstall and reinstall drivers
If the webcam or fingerprint sensor drivers are corrupted, it may create a problem when the user tries to set up Windows Hello. To fix the issue, attempt to reinstall the drivers.
Drivers Ekey Biometric USB Devices
- Right-click on Start and select Device Manager.
- In Device Manager, locate Fingerprint drivers.
- Right-click on the device and select Uninstall device.
- Do this for webcam and Hello facial recognition devices as well.
- Once done, click on Action and select Scan for hardware changes.
- Windows will scan for new devices and automatically install them with appropriate drivers.
- Reboot the computer and check if the error is resolved.
Drivers Ekey Biometric Usb Devices Download
The face and fingerprint are not available on this device problem can be fixed by updating or installing missing Windows Hello drivers. If the issue persists, try other steps in this article.