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,316 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-10-17T02:59:07+00:00

    I ran the specified power shell command and identified the same hp task as others have seen on the computer that has given me issues with 2004. I found the task in the task scheduler, but I also searched for "hp" in Apps and Features and found the related application there. I didn't write it down at the time I uninstalled it so I can't recall exactly what it was called: something about hp customer participation or analytics. Probably got installed as part of an HP driver install. I uninstalled the program and that also removed the task scheduler task so I didn't have to do anything else. I then updated to 2004 and so far I've gone the whole day with several reboots and no issues whatsoever.

    I also checked my other computers that had not had any issues with 2004 and one that I was waiting to update and none of them had that hp software installed. I updated the last one and it also did not have any issues.

    Looks like this workaround really does resolve the issue and since the program that triggers the bug is useful to HP but not to me, removing it is a bonus, not a limitation in my eyes.

    Good job!!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-10-17T02:18:54+00:00

    This procedure worked for me, so you may want o try it. First off I am running windows 10 pro, version 2004, with office professional 2010 64bit.

    What I have done twice now due to outlook passwords being lost with updates.(when I first installed 2004, and with the Sept update).

    Go into control panel

    Find Mail and open it

    Click on E-mail Accounts button

    For each account click change

    Under login information enter your password and check remember password.

    I remove the Test Account settings and then clicked Next and Finished.

    I am not sure if removing the Test accounts made a difference, I just did not want a test email.

    Give it a try and I hope it works for you.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-10-16T19:12:25+00:00

    I'm still bedeviled by this. Here is my output:

    Get-ScheduledTask : The system cannot find the file specified.

    At line:1 char:1

    • Get-ScheduledTask | foreach { If (([xml](Export-ScheduledTask -TaskNa ...
    • 
      
      
    • CategoryInfo          : ObjectNotFound: (MSFT_ScheduledTask:Root/Microsoft/...T_ScheduledTask) [Get-ScheduledTas

    k], CimException

    • FullyQualifiedErrorId : HRESULT 0x80070002,Get-ScheduledTask

    Tu run the command you must start a powershell window in admin mode. Then paste the command.  Hope it is the correct solution to your problem. Then option the windows task scheduler, and delete the job. In my case I was less drastic. @AndreyK02 suggested that checking the task : run only when the user is logged on solved the problem, so I did, and it worked.

    It was explained that the mode the task was previously set, needed the calling of a specific windows API that triggers the bug in windows. By checking this option (run only when the user is logged), this changes the problematic call. Some other users have the problem with other tasks than HP's.  This doesn't make the bug disappears, but it is a good workaround form many.

    Was this answer helpful?

    0 comments No comments