Systemwide password amnesia (v2004 build 19041.173)

Anonymous
2020-04-10T20:46:55+00:00

I have a Surface Pro 5 with a Windows Hello camera that wasn't working and I wasn't able to fix it. Looked like I'd need to do a reset to fix the drivers, so instead I decided to give 2004 a try, hoping the update would refresh the camera drives. Indeed this worked, but I've been having a lot of problems since the update:

Seems like all sorts of applications and OS features won't remember my username/passwords anymore.

  • Every time I log in I have to sign into both one drive personal and one drive business.
  • Outlook keeps asking me to log into my office365 every few hours.
  • Acrobat keeps asking for my Adobe login every time a load a pdf if I haven't done so in a few hours.
  • Settings periodically makes me fix my insider account configuration by re-authenticating with Hello
  • Lastpass extention in Firefox keeps asking me to enter my password despite being configured to only require a fingeprint (it first asks me for my fingerprint, but then also asks for the password)
  • probably some stuff I can't recall right now.

I wasn't having any of these issues before the update.

I tried following Lastpass's support advice to fix it by reinstalling the extension and resetting several settings but this didn't help.

It's possible these are all individual issues, but since it seems to be an issue with remembering credentials across a variety of applications, I'm suspecting it's a system wide issue and maybe not specific to these applications.

I checked that the credential manager service is running. It was set to manual. I changed it to automatic and rebooted but this didn't seem to help.

Anyone have an idea what could be going on here?

Thanks!

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-10-12T21:28:18+00:00

Update 2/8/21

This issue has been fixed by Windows in this Windows 10 update, February 2, 2021—KB4598291 (OS Builds 19041.789 and 19042.789) Preview (microsoft.com).

  • Addresses an issue in which using local Service for User (S4U) affects Data Protection API (DPAPI) credential keys and causes users to sign out unexpectedly.

I am updating the Outlook Known Issue article to reflect the same, Outlook and other apps won't remember password after Windows Updates - Outlook (microsoft.com).

Was this answer helpful?

9 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Sumit 44,226 Reputation points Volunteer Moderator
2021-02-10T03:14:41+00:00

Issue resolved in KB4601319 monthly update. If you continue to hit the issue, let us know.

February 2, 2021—KB4598291 (OS Builds 19041.789 and 19042.789) Preview (microsoft.com)

  • Addresses an issue in which using local Service for User (S4U) affects Data Protection API (DPAPI) credential keys and causes users to sign out unexpectedly.

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments

335 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-04-08T00:07:29+00:00

    Please, solve this problem! I have the last version of the OS, and every time I closed Chrome, all password disappearing and all sites are logouted. It's impossibile to work in this state!

    I've a Microsoft Account insted af a local account, there isn't any S4U task on my PC, and my Event Viewer is full of "DPAPI Unprotect failed . Status:0x8009000B ReasonForFailure:Could not get the master key"!

    I've installed all updates without any success... I can't work with the fear of knowing that as soon as I reopen the browser all my passwords will be gone and I will be thrown out of all the sites where I had logged out!

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-08-18T01:07:59+00:00

    This is what finally worked for me (after trying everything else on this forum and other forums):

    1. Close all programs
    2. Open Credential Manager and delete ALL credentials (web and Windows)
    3. Go to Settings - Accounts and choose to login with a Microsoft Account instead
    4. Choose PIN, restart computer, login with your Microsoft account
    5. Open Credential Manager and again delete ALL credentials
    6. Open up the apps you use (Outlook, etc.) and sign in. Also open up Chrome (or your preferred browser) and sign in to everything you are usually signed in to.
    7. Open Credential Manager and there should be a bunch of passwords under Windows now
    8. Restart
    9. Login with your Microsoft Account again
    10. Open Credential Manager and make sure the credentials are still there
    11. Open your apps and browser and make sure you are still logged in
    12. Go to Settings - Accounts and choose to login with a local account instead
    13. Put in a password and restart
    14. Login with your local account
    15. Check to make sure you are still signed in to everything
    16. Reboot again to verify and you are done

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-10-15T16:03:45+00:00

    Seemed to have worked for our situation in 2 machines!

    Ran Sumit's code from above:

    Right-click Start>Windows Powershell(admin). Copy and paste below command

    • Get-ScheduledTask | foreach { If ((xml).GetElementsByTagName("LogonType").'#text' -eq "S4U") { $_.TaskName } }

    Then based on Gabriel's suggestion to disable/remove the HP task that was shown in the display has now allowed the users to boot up without issues! They have NOT had to enter passwords for Office/Microsoft 365 (OneDrive, Word, Outlook) and have NOT had to enter passwords to saved remote desktop sessions. One user claims that they're still having some password memory issues with Edge, but I think that's user error induced and not related to this issue.

    Since this worked for two days I'm thinking this is a good workaround. I won't say this FIXED the problem since there's apparently a real bug/issue in there somewhere that really needs to be FIXED, but this is a solid work around.

    Good luck to others with this problem and finding this thread! Post if you have success as well.

    Thanks Gabriel and Sumit!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments