---
title: "Cannot Scan Fingerprints To Non-Cached Client"
slug: "cannot-scan-fingerprints-to-non-cached-client"
updated: 2025-10-14T22:08:31Z
published: 2025-10-14T22:08:31Z
canonical: "mfa.rapididentity.com/cannot-scan-fingerprints-to-non-cached-client"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://mfa.rapididentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cannot Scan Fingerprints To Non-Cached Client

If you are experiencing issues trying to scan your fingerprint to a computer where your MFA user has not been cached to it, see the following settings and items that need to be in place for this functionality to work.

## Policy Settings

In the Admin Portal > Policies Tab > Hardware tab > **Allow Unauthenticated One to Many Biometric Match** and setting to 'True' allows for users to walk up and swipe their finger without first entering a username. ![fingerprint settings.png](https://cdn.document360.io/cf888ab6-47bb-4aaa-984b-26a47cdccf46/Images/Documentation/fingerprint%20settings.png)

  

In the *Settings* tab, check (✓) the option **Allow Unauthenticated One-To-Many Biometric Match**. When enabled, the server compares the presented fingerprint template against the whole database of fingerprint templates and successfully authenticates if it matches. Click **Save** at the bottom of the page to confirm the change. ![fingerprint settings 2.png](https://cdn.document360.io/cf888ab6-47bb-4aaa-984b-26a47cdccf46/Images/Documentation/fingerprint%20settings%202.png)

  

You can verify that the *BioDevice* setting/registry key has been set by the MFA Policy by going to the device's registry: `HKLM\Software\Foray` and see if `BioAnyUserSync` is present and set to "True".

---

## Embedded Readers

- Make sure the BioDevice is set to "wbf" ![fp enroll - regedit.png](https://cdn.document360.io/cf888ab6-47bb-4aaa-984b-26a47cdccf46/Images/Documentation/fp%20enroll%20-%20regedit%282%29.png)
- If you are on MFA Client v4981, try rolling the client version back to an older version (this will require uninstalling the current client software and installing an older one)
  - *Recommended versions*: [4.9.4.1](/v1/docs/4941-client-release-notes), [4.9.6.1](/v1/docs/4961-client-release-notes)

---

## Drivers

If you are using a *Digital Persona* device, you may need to install the driver onto the client computer if it is not already

- *Recommended*: [DP-UareU-WSDK-220](https://cdn.document360.io/cf888ab6-47bb-4aaa-984b-26a47cdccf46/Images/Documentation/DP-UareU-WSDK-220.zip) ![download_symbol.png](https://cdn.document360.io/cf888ab6-47bb-4aaa-984b-26a47cdccf46/Images/Documentation/download_symbol.png)
- [U.are.U_Windows_3.2.0.89](https://cdn.document360.io/cf888ab6-47bb-4aaa-984b-26a47cdccf46/Images/Documentation/U.are.U_Windows_3.2.0.89.zip) ![download_symbol.png](https://cdn.document360.io/cf888ab6-47bb-4aaa-984b-26a47cdccf46/Images/Documentation/download_symbol.png)