After Windows 11 26H2 update: apps lose saved logins, WhatsApp won't open (DPAPI "Could not get the master key") - cause and fix

Apolônio Serafim 20 Reputation points
2026-10-05T11:46:24.5233333+00:00

Environment: Windows 11 Pro for Workstations, version 26H2 (build 26300.9457), signed in with a Microsoft account and a Windows Hello PIN.

Right after the feature update to 26H2 was installed, I had these symptoms:

  • WhatsApp Desktop (Store app) would not open. The mouse cursor showed the busy circle and nothing appeared. Its log (%LOCALAPPDATA%\Packages\5319275A.WhatsAppDesktop_cv1g1gvanyjgm\LocalState\applog.txt) showed thousands of restarts per hour with: COMException[-2146893772] (0x80090034) "error during native storage initialization" at WhatsApp.Encryption.ProtectionUtils.ProtectBytes
  • The PC felt slow (caused by the WhatsApp crash loop).
  • After a sign-out/sign-in, apps came back, but Edge, Discord, Obsidian and Credential Manager had lost their saved logins. The next day, WhatsApp asked me to link the device again.

Event Viewer > Applications and Services Logs > Microsoft > Windows > Crypto-DPAPI > Operational showed hundreds of:

  • Event 8198: "DPAPI Unprotect failed. Status: 0x8009000B. ReasonForFailure: Could not get the master key"
  • Event 8203: "Master Key decryption failed because no record of this key can be found in the Diagnostic file"
  • Event 3: "Master key access failed. Success: false"

I am posting the cause and the fix I found below, so others can recover their data.

Windows for home | Windows 11 | Security and privacy
0 comments No comments

Answer recommended by moderator
Apolônio Serafim 20 Reputation points
2026-10-05T11:47:07.8366667+00:00

WHAT HAPPENED

Windows protects app secrets (browser cookies and passwords, Credential Manager, app sessions such as WhatsApp) with DPAPI. DPAPI uses a "master key" stored in %APPDATA%\Microsoft\Protect<your SID>, and that key is unlocked by your sign-in credential.

  1. After the 26H2 update, the first sign-in could not unlock the existing master key. Every app that depends on DPAPI started failing.
  2. At the sign-in screen I clicked "I forgot my PIN" / the web sign-in option by accident. This signs you in through the browser or phone (the system account "WsiAccount" is enabled for this flow), so Windows does not receive your password. Windows then created a NEW master key protected by a different credential. Apps could not read their old data, so they silently created new keys and started from scratch (lost logins).
  3. The next day I signed in with my normal PIN. The PIN unlocked the ORIGINAL master key again, but not the one created during the web sign-in. So the data the apps re-created the day before became unreadable too, and WhatsApp asked for the QR code again.

My password had not changed in months. The PIN and the password unlock the same (original) key. Only the web sign-in path creates a separate key.

HOW TO CONFIRM YOU HAVE THE SAME PROBLEM

  • In the Crypto-DPAPI Operational log, look for Event 1 "DPAPI created Master key" at a time you did not expect, followed by many 8198/8203/3 events naming a different key GUID.
  • In %APPDATA%\Microsoft\Protect<SID>\ (hidden/system files) you will see more than one recent key file with a creation date matching the problem.
  • Local Users and Groups shows "WsiAccount" with a last logon time matching the moment the problem started.

THE FIX

Step 1. Sign in ONLY with your normal PIN or password. Do NOT use "I forgot my PIN", web sign-in or "Other sign-in options". Do NOT remove and re-create the PIN and do NOT reset your password yet: the PIN stores the credential that opens your original key, and re-creating it may lock that key permanently.

Step 2. Check if the old key works again: in the DPAPI log, the failures for the ORIGINAL key GUID should stop after this sign-in.

Step 3. Recover the original app data from a shadow copy (System Restore point) created BEFORE the update. Restore points are created automatically before feature updates. In an elevated Command Prompt:

vssadmin list shadows

Pick the shadow copy with a creation date just before the update (example: HarddiskVolumeShadowCopy4), then:

mklink /d C:\ShadowSnap \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4\

(Both backslashes before "?" are required.) Now copy what you need from C:\ShadowSnap\Users<you>\ to a safe folder first, for example:

  • AppData\Local\Microsoft\Credentials and AppData\Roaming\Microsoft\Credentials (Credential Manager)
    • AppData\Local\Microsoft\Edge\User Data\Local State, and in Default: Login Data, Login Data For Account, Network\Cookies
    • The same files for Chrome or other Chromium browsers (if "Local State" in the newest shadow copy has no "os_crypt" section, take "Local State" from an older shadow copy: the key does not change)
    • Electron apps (Discord, Obsidian, etc.): AppData\Roaming<app>\Local State (and Local Storage for Discord)

Remove the link when done: rmdir C:\ShadowSnap

Step 4. Close the apps (Edge, Discord, etc.; check Task Manager for background processes), BACK UP the current files, then copy the old files over the current ones. For browser databases, delete the matching "-journal" / "-wal" files next to them. For Credential Manager, only copy files that do not already exist.

Step 5. Open the apps. Credential Manager (cmdkey /list) should show your old entries again, and browsers and apps should be signed in as before the update. WhatsApp: just link it again with the QR code from your phone. Chrome passwords stored in your Google account sync back by themselves.

Step 6. Restart and sign in with the PIN to confirm: no new "DPAPI created Master key" event and no new 8198 failures.

PREVENTION

  • Avoid the "I forgot my PIN" / web sign-in option unless you really need it.
  • Optional: Settings > Accounts > Sign-in options > turn off "Use my sign-in info to automatically finish setting up after an update", so the first sign-in after an update is done by you.

What I could not confirm: why the first sign-in right after the 26H2 update could not open the original key. It could be the automatic sign-in that finishes the update or the same web sign-in path. I filed a Feedback Hub report for Microsoft.

Was this answer helpful?

7 people found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Felix Huang 0 Reputation points
    2026-10-31T05:45:37.3433333+00:00

    I hit this issue and Claude helped me fix it. Here is post incident report:

    Same issue on 26H2 (build 26300.9818, after KB5127936). Fixed by restoring the DPAPI master key files from a shadow copy.

    Setup: Windows 11 Pro 26H2, Microsoft account, signs in with a Windows Hello PIN. Memory integrity (HVCI) is on.

    Symptoms: after every reboot, Edge, Chrome, Steam and Battle.net lost their saved logins. The PIN itself kept working. Crypto-DPAPI/Operational showed hundreds of events 8198 (Status=0x8009000B, ReasonForFailure=6), 8203 and 3 (Success=false) for my existing master key. Protect calls also failed with “Access is denied”, so apps couldn’t save new logins either.

    Timeline (local time, 2026):

    • Oct 27, 4:23 PM and 6:37 PM: at two normal sign-ins, DPAPI re-encrypted all master keys. Everything kept working.
    • Oct 29, ~5:20 AM: KB5127936 installed. Windows restarted for the update at 5:45 AM.
    • Oct 29, 6:26 AM: a shadow copy was created. It turned out to contain the Oct 27 key files.
    • Oct 29, 5:41 PM: signed in with the PIN.
    • Oct 29, 7:29 PM: restarted from the Start menu.
    • Oct 29, 7:30 PM: Windows signed in automatically before any PIN entry. In that same second, all of my master key files in %APPDATA%\Microsoft\Protect\<SID>\ were rewritten, and the Credential Manager vault was moved to %LOCALAPPDATA%\Microsoft\Vault\Builtin.bkup.
    • Oct 30, 9:38 PM: first PIN sign-in after that restart. DPAPI couldn’t unlock any key, and every app had lost its login.
    • Oct 30, ~10:08 PM: restored the key files from the Oct 29 6:26 AM shadow copy and restarted. Fixed.

    Fix:

    1. Copied the master key files from a shadow copy taken before that automatic sign-in (\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopyN\Users\<user>\AppData\Roaming\Microsoft\Protect\<SID>\) to a backup folder.
    2. Overwrote the current key files with them, keeping the Hidden and System attributes.
    3. Restarted and signed in with the PIN.

    Everything came back: browser logins, Steam, and Credential Manager, which rebuilt itself from Builtin.bkup. It has stayed fixed across several reboots.

    Setup: Windows 11 Pro 26H2, Microsoft account, signs in with a Windows Hello PIN. Memory integrity (HVCI) is on.

    Symptoms: after every reboot, Edge, Chrome, Discord, Steam and Battle.net lost their saved logins. The PIN itself kept working. Crypto-DPAPI/Operational showed hundreds of events 8198 (Status=0x8009000B, ReasonForFailure=6), 8203 and 3 (Success=false) for my existing master key. Protect calls also failed with “Access is denied”, so apps couldn’t save new logins either.

    Timeline:

    • KB5127936 installed, followed by a restart for the update.
    • On the first restart after that, Windows signed in automatically (before any PIN entry). In that same second, all of my existing master key files in %APPDATA%\Microsoft\Protect\<SID>\ were rewritten, and the Credential Manager vault was moved to %LOCALAPPDATA%\Microsoft\Vault\Builtin.bkup.
    • From the next PIN sign-in on, DPAPI couldn’t unlock any of those keys.
    • No new master key was created, and I hadn’t changed my password or PIN.

    What I noticed: on this build, DPAPI re-encrypts every master key at each sign-in (event 8200). My guess is that the automatic sign-in re-encrypted them with a credential that the PIN sign-in doesn’t provide. I haven’t confirmed that.

    Fix:

    1. Copied the master key files from a shadow copy taken before that automatic sign-in (\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopyN\Users\<user>\AppData\Roaming\Microsoft\Protect\<SID>\) to a backup folder.
    2. Overwrote the current key files with them, keeping the Hidden and System attributes.
    3. Restarted and signed in with the PIN.

    Everything came back: browser logins, Steam, and Credential Manager, which rebuilt itself from Builtin.bkup. It has stayed fixed across several reboots.

    Prevention: I turned off Settings > Accounts > Sign-in options > “Use my sign-in info to automatically finish setting up after an update”.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. Zach 1 Reputation point
    2026-10-21T13:34:20.9166667+00:00

    I'm seeing this DAPI issue too. The Windows hello pin says it is unavailable and needs set up again. Happening to most of our fleet and i'm not sure why yet.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.