Confirmed
- Windows is not currently offering or completing the selected biometric sign-in path.
Device · reviewed 2026-09-01
Windows Hello face or fingerprint unavailable diagnostic
Windows Hello availability depends on supported hardware, device enumeration, drivers, sign-in configuration, policy, and the current Windows state.
High for Windows Hello symptomNot confirmed until device presence and policy are checked
Try a scenario
Resume a saved session — paste a Resume Capsule
The capsule is validated and restored only in this browser. An invalid capsule changes nothing.
Meaning & limits
What this diagnostic record establishes
Not confirmed
- The message does not prove the sensor is physically defective.
- It does not justify changing BIOS or deleting biometric credentials as the first action.
Context changes the route
What does Windows show?
Choose the context that matches your incident. These are alternatives, not a sequence of fixes. Follow only the matching check and keep its verification and rollback together.
The option is missing or unavailable
Likely layer: Hardware enumeration, driver, capability, or policy
First safe check: Check whether Windows can currently see the biometric device
Expected: You can separate a missing device from an enrollment or recognition problem.
Steps, verification and rollback
- Open Device Manager and look under Biometric devices, Cameras, and Unknown devices.
- Record the exact device name and any status code; keep PIN or password access available.
Verify: Return to Settings → Accounts → Sign-in options and compare availability after one normal restart.
Rollback: No system change is made by this check.
The option exists but recognition fails
Likely layer: Enrollment quality, sensor condition, or device software
First safe check: Check the sensor and one controlled reattempt
Expected: A consistent failure across clean, controlled attempts supports a device or enrollment-specific next step.
Steps, verification and rollback
- Clean and dry the sensor or camera area and confirm another sign-in method works.
- Record whether failure affects every enrolled finger or face attempt.
Verify: Use the same enrolled method once; do not repeatedly lock out the account.
Rollback: No system change is made by this check.
Work or school policy message
Likely layer: Identity policy or device management
First safe check: Preserve the policy message and contact the administrator
Expected: The administrator receives the exact policy evidence needed to check allowed Hello methods.
Steps, verification and rollback
- Capture the exact managed-policy message and device ownership context.
- Do not remove the work or school account to bypass policy.
Verify: Confirm any change through the organization-approved sign-in method.
Rollback: No system change is made by this check.
Before any second repair step
Verify the observation and preserve the evidence
After the first safe check, record whether the reviewed intermediate result occurred, whether the original problem was retested, and the exact output. An expected observation is not automatically a repair.
Outcome boundaries
- Observed as expected
- Observed something different
- Result unclear
- Could not complete the check
Then separately record whether the original problem still occurs, was not reproduced once, or has not been retested yet. Every session ends in stop, one repeat of the same check, one named missing fact, or escalation—never an open-ended repair sequence.
Evidence fields for this task
- Exact device nameAs shown in Device Manager
- Hardware IDsCopy the first one or two IDs, after reviewing them
- Driver provider/version/dateProvider · version · date
- Port/device comparisonWhat changed on another port, PC, cable, or reconnect
The browser-local Evidence Pack combines the selected context, safe action, actual observation, sources, review date, missing evidence, and stop boundary. It can be copied or printed without creating an account or uploading a log.
After you perform the safe check
Read the evidence you collected
Paste bounded driverquery or PnPUtil enumeration text and extract driver, package, provider, class, version, signer, state, path, and device-relation facts without recommending a download or naming a culprit.
Review trail
Official and first-party sources
- Windows Hello common issues and troubleshooting tips Microsoft Support · primary
- Error codes in Device Manager in Windows Microsoft Support · primary