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!

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) .

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.

Thanks. I did try the sign on via MS online account process you suggested and some others, and it seems to have worked (fingers crossed). I really don't like the "Big Brother" aspect of having to use an online log on, so hopefully MS fixes the local account issue soon, or I hope that when I do switch back to my local account it still holds the credentials. I passed the 10 day window ro revert to 1909, and the MS tech I chatted with for over 2 hrs to try to fix this said there was no was now to go back, which I find very hard to believe, but that's what he said. Another MS issue that should be fixed.

Hello, similar situation. In our reality we have a lot of small local network (without domain). 2/3 client Windows 10 PRO in WORKGROUP, all of them with same username/password One of this client is configured as SERVER, so it shares one or two folder. And another client some other folder. So when from client1 I run \client2 o \server I'm not asked to insert credential (becasue they are the same) It has happened on more than 3/4 customers (with similar configuration). After one of these clients has been updated to 2004 version when from the same client I run \client2 o \server I'm asked to insert credential. After inserted them I can work. After few hours I've to insert credential againi. Save credential on Windows Credential Manager doesn't help I've noticed the when \server doesn't work if I "lock" the client1 with "windows button+L" and then I login again I run \server and immediately work! I hope this information can help to solve this problem Thanks Luca

Thanks for the detailed response

Systemwide password amnesia (v2004 build 19041.173)

Anonymous

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!

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

Answer accepted by question author

Anonymous

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).

0 comments

Answer accepted by question author

Sumit 44,306 Volunteer Moderator

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.

0 comments

335 additional answers

Anonymous

2020-09-02T14:24:13+00:00

Thanks. I did try the sign on via MS online account process you suggested and some others, and it seems to have worked (fingers crossed). I really don't like the "Big Brother" aspect of having to use an online log on, so hopefully MS fixes the local account issue soon, or I hope that when I do switch back to my local account it still holds the credentials.

I passed the 10 day window ro revert to 1909, and the MS tech I chatted with for over 2 hrs to try to fix this said there was no was now to go back, which I find very hard to believe, but that's what he said. Another MS issue that should be fixed.
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-31T13:09:11+00:00

Hello, similar situation.

In our reality we have a lot of small local network (without domain).

2/3 client Windows 10 PRO in WORKGROUP, all of them with same username/password

One of this client is configured as SERVER, so it shares one or two folder.

And another client some other folder.

So when from client1 I run \client2 o \server I'm not asked to insert credential (becasue they are the same)

It has happened on more than 3/4 customers (with similar configuration).

After one of these clients has been updated to 2004 version when from the same client I run \client2 o \server I'm asked to insert credential.

After inserted them I can work.

After few hours I've to insert credential againi.

Save credential on Windows Credential Manager doesn't help

I've noticed the when \server doesn't work if I "lock" the client1 with "windows button+L" and then I login again I run \server and immediately work!

I hope this information can help to solve this problem

Thanks

Luca
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-30T01:38:52+00:00

Thanks for the detailed response
Was this answer helpful?

0 comments No comments