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: Oldest
  1. Anonymous
    2020-07-11T04:51:57+00:00

    Not going to use Sign-in account and not going back to 1909. Using IP address instead of name for storing windows credentials access to NAS works. Using \NASname will keep asking for password every time windows startup and until now still no update from Microsoft to solve this issue really is pathetic.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-07-17T17:06:52+00:00

    Not going to use Sign-in account and not going back to 1909. Using IP address instead of name for storing windows credentials access to NAS works. Using \NASname will keep asking for password every time windows startup and until now still no update from Microsoft to solve this issue really is pathetic.

    So, after Over 2 months , nobody has figured out a real fix or workaround that sticks. Not to mention Microsoft has failed to even acknowledge the problem let alone fix it. I tried rolling back to 1909 and it worked great, but then the dang thing reinstalled itself without my knowledge. after a couple of days even though I had my system updates paused for 7 days. Of course now the time limit has passed. 

    It is really a major annoyance but I guess that is the world of Windows and has been since Windows 3.0. I hate the alternatives because they tend to be just as buggy in my experience. Not to mention I hate crapple in any form.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-07-17T18:30:18+00:00

    I've avoided updating back to 2004 for now due to this issue, plus it wasn't available for my computers in Windows Update. It's now available to one of them, but not my Surface yet.

    On another thread (I can't recall which one now) it was mentioned that if you do a full system Reset, the newly reset system will not have this issue. Or that alternatively, you can add a new User Account and the new user will not see this problem (you can then migrate from your old account to the new one).

    Can anyone here confirm if the above is true or not?

    I've always been reluctant to log into Windows using a Microsoft Account (I log in to Microsoft applications using my Microsoft account). Among other issues, it's never been clear to me what exactly Windows will store on your account versus locally. I vaguely recall it was storing or backing up bitlocker decryption keys in your account, but that may have been for Home versions only. Just for security, I don't want my keys, passwords, etc stored on Microsoft's cloud. Is there a detailed document explaining what Microsoft does when you sign in with a Microsoft account?

    It seems to be the case that if you fix the issues from this thread by signing in with an MS account, they will come back if you switch back to a local account. Is that the indeed the case?

    Just trying to get some clarifications before I end up updating.

    Thanks!

    Was this answer helpful?

    0 comments No comments