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: Most helpful
  1. Anonymous
    2020-11-01T16:32:55+00:00

    Specific to the script...Since I'm not a fan of HP programs running I completely removed the scheduling task after it was identified in the Powershell script. If you're just disabling it then it would probably still show since it's there, but it's not active. So it shouldn't be interfering with the password issues in this thread. 

    Other users suggested changing the option to run when user is logged in rather than system run. But, why even keep it running? HP installs too much bloatware when you load full drivers. Just let Win10 find the best driver for your HP printer and run it that way. I've always been against the full install of drivers released by HP. I don't need all the intrusions they include with the software. 

    Not sure about your other machines and your steps of removing IMAP/POP accounts and adding them back. We went through similar steps, but also the process of changing the user account from local to Microsoft account and even creating a new user on the computer it still had the issues. Once removing the HP task all was "fixed".

    Have since updated about 5 more machines. I removed all HP software/drivers before upgrading to 2004 update. No machines had further issue. All HP printers work just fine without the HP bloatware installed so I'm leaving it of those machines.

    Good luck! Hope "real" fix comes from MS soon, but for the time being the helpful posts on this thread seem to work for most.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-11-01T09:15:38+00:00

    The problem still persists. OS build 19041.610

    However, when Outlook forgets the passwords (and the passwords fields are empty), simply putting the machine to sleep and then waking it up, solves everything. And the passwords magically reappear.

    So what is the system doing when put to sleep and then back on? Any ideas?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-10-31T14:53:01+00:00

    Hi Sumit. I have written stuff about this problem on another thread. Please see

    I installed 2004 three times and rolled back every time because of this problem after trying ineffective solutions posted on the above thread.

    One older machine did not have a problem from the start but I set up Outlook after I did 2004 purely as an experiment. (I use this machine for music composition/editing/mixing, not any Office apps). My aged laptop had the problem. I did need Outlook on this machine so, with the experience of my music machine in mind, I deleted all IMAP and POP accounts and set them all up again from scratch. No problem after that. This approach did not work on my UEFI machine so I did the 3rd rollback. I then disabled Safe Boot in my UEFI, re-installed 2004 (4th time) and all is now well. This all seems a bit crazy to me with no real rhyme or reason but I now have three functional machines with 2004. All have build 19041.572

    So, back to your post here: I am curious. Before I rolled back 3rd time I did try your Powershell script. It correctly identified the HP task. I disabled it in Scheduler but the script still found it, even after a restart. It didn't disappear until I actually deleted it from Scheduler.

    What is your perspective on this, Sumit ? Any one else had similar findings ?

    Was this answer helpful?

    0 comments No comments