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,306 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: Newest
  1. Anonymous
    2020-12-05T17:13:32+00:00

    I suspect that this problem has deep issue with security architecture in Windows. Because this is a security matter, they can't disclose it too much what they are doing, before coming with a sound solution.  I've never seen such a big thread about a single issue like this.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-12-05T08:04:03+00:00

    Have you done what I said? Locate the offending tasks using the Powershell command (do you find any?) then alter each one by unticking its "Do not store password" option (enter your password when asked). 

    Disabling them is NOT enough.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-12-05T06:47:52+00:00

    Sumit - Insider MVP,

    I am not posting to in any way bash Microsoft, rather to ask for a reasonable amount of customer service.  I would think that if they are aware of this situation, they would post here with an update regarding what is being done about the problem.  It would be comforting to know just where we stand and when we can reasonably expect a fix.  This is only good business and responsible customer service.

    Thanks for your reply,

    Firecapt1

    Was this answer helpful?

    0 comments No comments