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.

My desktop has been on 2004 for some time now, using a local account with no problem. A week or so I was finally offered the 2004 update on my Surface Pro 5, so I gave it a shot, hoping some of the newer updates might have fixed the problem. But I still got the same issues. I switched from signing in with my local account to my microsoft account. I then turned off all syncing and erased all previously synced data from my account settings on microsoft's web page (it can be a bit tricky to find, but there is an option to do this). As far as I could tell, everything was okay again using the microsoft account sign in and it didn't seem to disrupt my system in any obvious ways. Still, I just really don't like the idea of doing this, so after a while I switched my account back to local login, hoping whatever was wrong was now fixed. At first it looked okay, but it sometimes takes a while to lose passwords and logins. Repeated logouts or reboots don't necessarily show the problem, but after a few hours eventually something weird will start happening like Outlook will prompt for a login again, and at that point lots of things go and if I reboot onedrive personal and business will fail to login and require entering passwords again. Then I had this idea that maybe it's changing the type of login that fixes the problem, not necessarily being on the microsoft login. So maybe if I was using microsoft login prior to the update, changing to the local login would be okay. I reverted back to 1909, which fixed the issues, then switched to a microsoft login while still on 1909. Then I upgraded again to 2004, rebooted a few times, then switched back to local login. At first looked good.... but then the same issues all came back. Very disappointed. Finally, I switched back to the microsoft login and left it that way for a day or so and didn't see any signs of problems. So it does seem to be the case that if you login using your microsoft account, it will mitigate these issues, but you need to be okay with staying with that. As I noted, my desktop hasn't had any of these problems and is using a local account, so I don't think this is a conspiracy by microsoft, it does feel like a bug that affects certain configurations, maybe not common enough for microsoft to bother acknowledging or fixing :(. One previous poster mentioned he though machines that had BIOS were not affected but those that use UEFI are. My desktop uses BIOS and my Surface uses UEFI, so it does fit this pattern. Could just be a coincidence or maybe a correlation because UEFI machines are likely to be newer so may have some other components related to this bug that are not present on older machines? In any case I decided I'd revert to 1909 for now (I restored an image backup to be safe) rather to give in to using a microsoft account for login. One thing I still wanted to try was creating a fresh new user account (local) to see if that would fix it, but I didn't want to take the time to do that right now since I'd have to reinstall or at least reconfigure lots of software. Then Microsoft decided to backport WSL2 to 1903 and 1909. And honestly, WSL2 is the only really compelling feature from 2004 I really wanted. Since I've now got that running on my 1909 install, I'm inclined to just skip 2004 altogether. It sounds like the fall release is practically done already and is focused more on bug fixes and stability than new features. I've set my windows update to not automatically install feature updates for a year. I'll turn that off once the next feature update is released. I'm hoping the next one will not have this issue. 🤞

Click start >> Settings >> Update & Security >> Recovery

I downgrade the version (fallback) to version 1909 now everything perfect

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-08-29T15:53:27+00:00

My desktop has been on 2004 for some time now, using a local account with no problem.

A week or so I was finally offered the 2004 update on my Surface Pro 5, so I gave it a shot, hoping some of the newer updates might have fixed the problem. But I still got the same issues.

I switched from signing in with my local account to my microsoft account. I then turned off all syncing and erased all previously synced data from my account settings on microsoft's web page (it can be a bit tricky to find, but there is an option to do this).

As far as I could tell, everything was okay again using the microsoft account sign in and it didn't seem to disrupt my system in any obvious ways. Still, I just really don't like the idea of doing this, so after a while I switched my account back to local login, hoping whatever was wrong was now fixed.

At first it looked okay, but it sometimes takes a while to lose passwords and logins. Repeated logouts or reboots don't necessarily show the problem, but after a few hours eventually something weird will start happening like Outlook will prompt for a login again, and at that point lots of things go and if I reboot onedrive personal and business will fail to login and require entering passwords again.

Then I had this idea that maybe it's changing the type of login that fixes the problem, not necessarily being on the microsoft login. So maybe if I was using microsoft login prior to the update, changing to the local login would be okay.

I reverted back to 1909, which fixed the issues, then switched to a microsoft login while still on 1909. Then I upgraded again to 2004, rebooted a few times, then switched back to local login. At first looked good.... but then the same issues all came back. Very disappointed.

Finally, I switched back to the microsoft login and left it that way for a day or so and didn't see any signs of problems.

So it does seem to be the case that if you login using your microsoft account, it will mitigate these issues, but you need to be okay with staying with that. As I noted, my desktop hasn't had any of these problems and is using a local account, so I don't think this is a conspiracy by microsoft, it does feel like a bug that affects certain configurations, maybe not common enough for microsoft to bother acknowledging or fixing :(. One previous poster mentioned he though machines that had BIOS were not affected but those that use UEFI are. My desktop uses BIOS and my Surface uses UEFI, so it does fit this pattern. Could just be a coincidence or maybe a correlation because UEFI machines are likely to be newer so may have some other components related to this bug that are not present on older machines?

In any case I decided I'd revert to 1909 for now (I restored an image backup to be safe) rather to give in to using a microsoft account for login. One thing I still wanted to try was creating a fresh new user account (local) to see if that would fix it, but I didn't want to take the time to do that right now since I'd have to reinstall or at least reconfigure lots of software.

Then Microsoft decided to backport WSL2 to 1903 and 1909. And honestly, WSL2 is the only really compelling feature from 2004 I really wanted. Since I've now got that running on my 1909 install, I'm inclined to just skip 2004 altogether. It sounds like the fall release is practically done already and is focused more on bug fixes and stability than new features. I've set my windows update to not automatically install feature updates for a year. I'll turn that off once the next feature update is released. I'm hoping the next one will not have this issue. 🤞
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-29T08:29:44+00:00

Click start >> Settings >> Update & Security >> Recovery
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-29T05:15:08+00:00

I downgrade the version (fallback) to version 1909 now everything perfect
Was this answer helpful?

0 comments No comments