Vendors who provide both legacy biometric and WBDI drivers can use the driver Feature Score to control which driver is installed from Windows Update.
Vendors who choose to write a single driver that supports legacy and WBDI should be aware that to work properly with the Windows Biometric Framework, the driver must support exclusive access. When exclusive access is disabled, the driver functions as a legacy driver. To review how to set the Exclusive value in the registry, see Installing a Biometric Driver.
In addition, a biometric driver operating in legacy mode should not assign the GUID_DEVINTERFACE_BIOMETRIC_READER device interface. Assigning this device interface causes the Windows Biometric Service to recognize the driver.
If Feature Score is set appropriately, the WBDI driver will only be installed on systems that do not have a biometric driver already in place.
If a customer decides to opt into a legacy stack, the customer can install a higher-ranked legacy driver over the WBDI driver.
How Feature Score Works
Feature Score is represented in the third and fourth digit of the overall driver rank. For instance, GG is the feature score from the following driver rank:
Lower feature numbers indicates better matches. The default feature score is 0xFF, which indicates that there is no preference based on the features of a driver.
Microsoft recommends a feature score of 0xa0 for legacy biometric drivers. The feature score should never be set to 0x00, in case there is a need to override it later.
The feature score for a driver is set by an INF FeatureScore directive in the INF DDInstall Section for the device.
For example, the following code sets the feature score of a driver to 0x20:
[DDInstallSectionName] . . . FeatureScore=x20
For more information about how to set the feature score on drivers, see Feature Score (Windows Vista).