Few things are more annoying than typing the PIN you’ve used a thousand times and having Windows 11 refuse it — or worse, telling you “Your PIN is no longer available.” The good news: this is a credentials problem, not an account problem. Your Microsoft account is fine, your files are fine, and you can still sign in with your password while you fix it. The PIN itself lives in a protected system folder, and when that folder’s data gets corrupted, Windows loses the ability to verify your PIN.
The most common triggers are Windows updates (especially feature updates), TPM or motherboard changes, disk errors, and occasionally antivirus software locking the credential store. The fixes below go from the quickest (just reset the PIN from Settings) to the definitive (clearing the NGC credential folder and rebuilding it). If you’re locked out entirely, start with Fix 1 — it gets you signed in with your password so you can do the rest. For related sign-in trouble, see our Windows Hello repair guide and our login screen loop fix .
Why this happens
- Corrupt NGC folder: The
C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGCfolder holds PIN credentials; corruption here makes the PIN “unavailable.” - TPM changes: PINs are bound to the Trusted Platform Module — a TPM reset, firmware update, or motherboard swap invalidates stored PINs.
- Windows update damage: Feature updates sometimes break the credential provider chain that handles PIN sign-in.
- Permission drift: System permission changes on the NGC folder can lock Windows itself out of reading your PIN.
- Corrupt user profile: A damaged profile can break the link between your account and its PIN credential.
- Antivirus interference: Some security products aggressively guard credential folders and block legitimate access after their own updates.
- Microsoft account sync issues: For Microsoft accounts, a sync hiccup can desynchronize the local PIN from the account credential.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Sign in with your password instead
Get into Windows first; fix the PIN second.
- On the login screen, click Sign-in options below the PIN field.
- Click the key icon (password) and enter your Microsoft account password — or your local account password if you use a local account.
- Once signed in, don’t skip the remaining fixes: password sign-in works, but you want your PIN back, and the underlying corruption won’t heal itself.
- If you’ve forgotten the password too, use another device to reset it at Microsoft’s account recovery page, then return here.
Fix 2: Remove and re-add the PIN from Settings
The standard reset resolves most cases.
- Go to Settings > Accounts > Sign-in options.
- Under PIN (Windows Hello), click Remove. Confirm with your password when prompted.
- Restart the laptop — this clears any cached credential state.
- Return to Settings > Accounts > Sign-in options > PIN (Windows Hello) and click Set up (or Add).
- Enter your password to verify, then choose a new PIN. Test it by locking the PC (Windows + L) and signing back in.
Fix 3: Use the “I forgot my PIN” link
When Settings won’t cooperate, the recovery link does the same job from the login screen.
- On the login screen, enter any PIN (or leave it blank) and click OK — when it fails, look for I forgot my PIN below the field.
- Click it and verify your identity with your Microsoft account password.
- Follow the prompts to set a new PIN. This path rebuilds the credential even when the Settings route is blocked.
- If the link doesn’t appear, you’re likely on a local account — sign in with the account password (Fix 1) and use Fix 2 instead.
Fix 4: Clear the NGC folder and rebuild
The definitive fix for “PIN is unavailable” errors.
- Sign in with your password (Fix 1). Open File Explorer, click View > Show > Hidden items.
- Navigate to
C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC. - If access is denied: right-click the NGC folder > Properties > Security > Advanced > Change (owner) > enter your username > tick Replace owner on subcontainers and objects > OK, then grant yourself Full control.
- Delete everything inside the NGC folder (not the folder itself).
- Restart, then go to Settings > Accounts > Sign-in options > PIN (Windows Hello) > Set up and create a fresh PIN.
- This forces Windows to generate clean credentials from scratch — the corruption is gone because the corrupted files are gone.
Fix 5: Check the TPM and credential services
A PIN depends on the TPM and two background services.
- Press Windows + R, type
tpm.msc, and confirm the TPM reports “The TPM is ready for use.” If not, clear it via the BIOS/UEFI (this resets TPM keys — you’ll re-add the PIN after). - Press Windows + R, type
services.msc, and verify Credential Manager and CNG Key Isolation are Running with Automatic (or Manual (Trigger Start)) startup. - If either service is stopped, right-click > Start, then set the startup type correctly.
- Restart and try the PIN again. Check your laptop vendor’s guidance too — Dell, HP, and Lenovo all publish TPM firmware updates that fix PIN-related bugs; Microsoft’s support site documents the services involved.
Fix 6: Run system file repair and update Windows
Catch-all for update damage and corrupted components.
- Open Terminal (Admin) or Command Prompt (Admin) and run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealth. - Go to Settings > Windows Update and install everything pending — Microsoft regularly ships fixes for PIN and Hello sign-in bugs. Grab the latest build with Microsoft’s Windows 11 download page if Windows Update itself is stuck.
- After updating, remove and re-add the PIN one final time (Fix 2) so the credential is generated under the fixed components.
- If the PIN breaks again immediately after the next update, pause updates temporarily and report the pattern — recurring update breakage is a known-issue candidate.
Closing
PIN problems feel personal — it’s your code, and the machine is rejecting it — but they’re mechanical: corrupted credential files, a desynced TPM, or a damaged sign-in component. The NGC folder rebuild in Fix 4 resolves the stubborn cases that simple PIN resets can’t touch, and it’s safe to do because it only affects sign-in data. Once your PIN works again, write it down somewhere secure (a password manager, not a sticky note) so a future glitch never turns into a lockout. And if the PIN field itself never appears — just a spinning login screen — that’s a different fault covered in our login loop guide .
