0XC0000440

0xC0000440: Credential Needs Confirmation Fix

EP
Erropedia Team
📅 May 27, 2026 📅 Updated Jul 31, 2026 👁 10 views Windows Errors Beginner
This error means Windows needs you to confirm your credential (like a password or PIN) before it works. We'll fix it starting with the easiest step.

What's Going On With 0xC0000440?

You're seeing error 0xC0000440 (STATUS_CRED_REQUIRES_CONFIRMATION) when trying to sign into an app, connect to a remote desktop, or authenticate with a work or school account. It's not a crash. It's Windows being extra cautious.

The message: "The requested credential requires confirmation." Translation: Windows has a stored credential for you, but it's not sure that credential is still valid or that you're the one using it. This often happens after a password change, a PIN reset, or when Azure AD Multi-Factor Authentication kicks in.

I've seen this most often with Office 365 sign-ins, VPN connections, and Remote Desktop. The credential is there—but it's in a "pending confirmation" state.

A quick note: This is not a hardware issue or a corrupted OS. Don't waste time with SFC or DISM. The fix is about refreshing the credential itself.

Fix 1: Remove and Re-enter the Credential (30 seconds)

This is the fastest fix. We're going to delete the stored credential and then let Windows ask for it fresh.

  1. Press Windows Key and type Credential Manager. Open it.
  2. Click Windows Credentials (not Web or Certificate-based).
  3. You'll see a list under Generic Credentials. Look for entries related to the service that's failing—like MicrosoftOffice16_Data:ADAL:... or AzureAD:UserID or TERMSRV/computer-name. The icon is usually a key.
  4. Click the arrow to expand that credential, then click Remove. Confirm when prompted.
  5. After removing: Go back to the app or service that gave the error. Try signing in again. Windows will ask for your password or PIN again. Enter it fresh. That's the confirmation it needs.

Expected outcome: The error should be gone. If it's not, move to Fix 2.

Fix 2: Reset Your PIN or Password via Your Account (5 minutes)

Sometimes the credential itself is fine, but the confirmation token expired. This is especially common with Windows Hello PINs or Microsoft work/school accounts that require periodic re-authentication.

  1. Press Windows Key + I to open Settings.
  2. Go to Accounts > Sign-in options.
  3. Under Windows Hello PIN, click I forgot my PIN (even if you didn't forget it). Follow the prompts to reset it. You'll need your Microsoft account password or your local password.
  4. If the error is for a work or school account (like Office 365), go to https://myaccount.microsoft.com and sign in. Look for Security info or Password reset. Reset your password there. Then try the app again.
  5. After resetting, reboot your PC. Try the failing sign-in again.

Why this works: Resetting the PIN or password forces Azure AD or the local authentication service to issue a fresh confirmation token. The old token (which was stuck in "pending") gets tossed.

Fix 3: Clear the Token Broker Cache (15+ minutes, advanced)

If the two fixes above didn't work—and they usually do—the problem is in the Token Broker cache. This is Windows' internal storage for authentication tokens. It can get corrupted or out of sync, especially after multiple password changes. You'll need admin rights.

Step 3a: Stop the Token Broker Service

  1. Press Windows Key + R, type services.msc, and press Enter.
  2. Scroll down to Windows Token Broker Service. Right-click it and select Stop. Leave the Services window open.

Step 3b: Delete the Token Broker Cache

  1. Open File Explorer. In the address bar, paste: %LOCALAPPDATA%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\LocalState
  2. Delete everything inside that folder. You might get a permission error on some files—that's fine, skip those. Delete what you can.
  3. If that folder doesn't exist (it will on most Windows 10/11 Pro or Enterprise), try: %LOCALAPPDATA%\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\LocalState
  4. Empty the Recycle Bin.

Step 3c: Restart the Service and Reboot

  1. Go back to Services. Right-click Windows Token Broker Service and select Start.
  2. Reboot your PC.
  3. Try signing in to the app again. Windows will build a fresh token from scratch.

When to Give Up and Call Support

If none of these fixes work, it might be a larger issue. Two things to check before you call IT:

  • Is your account locked out? Try signing into a web browser at https://login.microsoftonline.com. If you get locked out there, contact your admin.
  • Is it a guest account? If you're using a guest or B2B account (like a shared mailbox), the admin often needs to re-invite you. That's not something you can fix on your end.

But honestly, in my experience, Fix 1 knocks out about 80% of these errors. Fix 2 gets another 15%. So you're almost certainly fine.

Related Errors in Windows Errors
0X000004D5 ERROR_RETRY 0X000004D5: The operation could not be completed 0XC0000282 STATUS_RANGE_LIST_CONFLICT (0XC0000282) — How to Fix It 0X80280051 TPM_E_DAA_INPUT_DATA0 (0X80280051) – 3 Fixes That Work 0XC00D0024 NS_E_INTERNAL (0xC00D0024) – Fix Windows Media Player Crash
STATUS_CRED_REQUIRES_CONFIRMATION 0xC0000440 credential confirmation error Windows login error sign-in confirmation fix credential manager error Windows 10 authentication error Windows 11 credential error work or school account error password confirmation Windows PIN error Windows remote desktop credential error VPN credential error Azure AD authentication error Microsoft account confirmation

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.