Overview
Windows Hello Status answers one specific, surprisingly hard-to-verify question: is passwordless sign-in actually configured on this PC, and if so, which method — a PIN, a fingerprint, or facial recognition? Windows Settings buries this information across multiple sub-pages that only show what is set up for the account currently logged in, and it gives no quick way to confirm from a script or a support session whether Hello is genuinely active or just available in principle. This tool reads the underlying evidence directly and reports it in one window.
Key Features
- Detects whether a Windows Hello PIN has been created for the current user
- Detects whether biometric (fingerprint or face) sign-in has been enrolled
- Confirms whether the underlying Windows Biometric Framework is present at all
- Works without needing to open Settings or sign in again to check
- Read-only — makes no changes to sign-in configuration
- Instant results, no waiting on a Settings page to load
Why You Might Need This Tool
IT support staff troubleshooting a sign-in complaint often need to know, before touching anything, whether Hello is even configured on the machine in front of them — a "my fingerprint reader stopped working" ticket is a very different problem if no fingerprint was ever actually enrolled versus one where enrollment exists but the sensor driver has failed. Anyone auditing their own PC's security posture, or preparing to reinstall Windows and wanting to remember what sign-in methods were active beforehand, gets the same quick confirmation without hunting through three separate Settings pages.
How It Works
Windows does not expose a single clean API that simply answers "is Hello set
up," so this tool checks the same underlying evidence Windows itself relies on.
For the PIN, it resolves the current user's security identifier via
WindowsIdentity.GetCurrent().User and checks whether a matching
folder exists under
C:\\Windows\\ServiceProfiles\\LocalService\\AppData\\Local\\Microsoft\\Ngc\\<SID>
— this is the Next Generation Credentials store Windows creates the moment a PIN
is configured, and its presence is a reliable signal that one exists. For
biometrics, it checks the registry under
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Biometrics\\Credential
Provider\\<SID>, which Windows populates only once a fingerprint or
face template has actually been enrolled for that user. A third, simpler check
confirms whether the Windows Biometric Framework itself is present under
SOFTWARE\\Microsoft\\Biometrics, independent of whether anything has
been enrolled — useful for distinguishing "no compatible sensor" from "sensor
present but nothing enrolled yet."
How to Use It
Run the tool and it immediately shows three rows: whether a PIN is configured, whether biometric sign-in is enrolled, and whether the biometric framework is present at all. Click Refresh after making a change in Windows Settings — such as setting up a new PIN — to confirm the change was detected. There is nothing else to configure.
System Requirements & Notes
Runs on Windows 10 and 11 x64 and does not require administrator rights, since it only reads registry keys and folders that belong to the current user's own profile. It reports on the currently logged-in user only; it cannot check Hello status for other accounts on a shared PC unless run while signed in as that account.
Frequently Asked Questions
Can this tool set up Windows Hello for me?
No — it is a read-only status checker. To configure a PIN or biometric sign-in,
use Settings → Accounts → Sign-in options directly.
Why does it show biometrics as "not enrolled" even though I have a
fingerprint reader?
Having compatible hardware and having actually completed enrollment are different
things — the registry key this tool checks is only created once enrollment
finishes successfully, not simply because a sensor is detected.
Does this reveal my PIN or biometric data?
No. It only confirms presence or absence of the configuration, never any
sign-in secret itself.