Fix 0x80097019 Credential Confirmation Error on Windows

This error pops up when Windows can't confirm a saved credential—usually a network or VPN password. Here's how to clear the stale credential and fix it fast.

Quick Answer (for pros)

Open Credential Manager (control keymgr.dll), go to Windows Credentials, find the entry for your target server/network, expand it, and click Remove. Re-authenticate fresh.

This error—0x80097019, or ERROR_CRED_REQUIRES_CONFIRMATION—is Windows being cautious. It means a stored password or certificate is flagged as needing re-validation. Happens most often with mapped drives, VPN connections (I've seen it constantly with Cisco AnyConnect and OpenVPN), or Remote Desktop shortcuts that saved the wrong credentials after a password change. The system won't use the credential until you confirm it's correct. Most of the time, the credential is just stale or corrupted. Deleting and re-entering it is the fix.

Step-by-Step Fix

Open Credential Manager. Press Win + R, type control keymgr.dll, and hit Enter. (The old rundll32 path works too, but I find the direct control panel shortcut faster.)
Click 'Windows Credentials'—not 'Web Credentials'. The error is about a Windows-level credential, like a network drive or remote desktop login.
Find the offending entry. Look for the server name, IP address, or VPN connection name that triggered the error. It's usually under 'Generic Credentials' or 'Windows Credentials' with a name like TERMSRV/10.0.0.5 (for RDP) or MicrosoftOffice15_Data:ADAL:...' for Office 365.
Expand the entry by clicking the arrow on the right, then click 'Remove'. Windows will ask you to confirm—hit Yes.
Restart the app or connection that failed. Try your VPN connection again, re-map the network drive, or launch Remote Desktop. You'll be prompted for fresh credentials. Enter them correctly.
Check the box 'Remember my credentials' if you don't want to retype them next time—but only if you're sure they won't change soon.

Alternative Fixes (when the main one doesn't work)

If the credential keeps coming back or the error persists:

Clear all stale credentials. Go to Control Panel > User Accounts > Credential Manager, then remove everything under Windows Credentials that looks related to your issue. I've had cases where a leftover TERMSRV entry for an old server was interfering with the new one.
Use the Command Prompt. Open as admin (Win + X, then 'Terminal (Admin)'), and run cmdkey /list to see every stored credential. Then cmdkey /delete:<targetname> (take the exact target name from the list). This nukes it without the GUI.
Check for certificate issues. If the credential involves a smart card or certificate (common in corporate VPNs), open certmgr.msc, look under 'Personal' and 'Trusted People', and verify the cert isn't expired. A cert that expired yesterday will produce this error. Remove the old cert and install the new one from IT.
Reset Windows Credential Manager service. Open an admin command prompt, type net stop VaultSvc && net start VaultSvc. This restarts the service that manages credentials. I've seen it clear weird glitches.

Prevention Tip

Here's what I do: after changing any password (Windows account, work email, VPN), immediately update or remove the old credential in Credential Manager. Don't wait for the error to pop. Also, if you use Remote Desktop frequently, don't save the password for servers that expire or rotate passwords—just type it each time. It's a minor inconvenience that saves you this exact headache.