A bug in Windows 10 version 2004 prevents cookies and logins from being saved

New reports indicate that some users have issues with Windows 10 2004 and 20H2 successor. They says that cookies or login data fails to be saved, especially with the Chrome browser. As one user figured out, it is due to the S4U task  "TASK_LOGON_S4U" in the Task Scheduler.


Such tasks are described by Microsoft as follows.

ASK_LOGON_S4U is yet another option that provides a more secure alternative. It takes advantage of a service for user (S4U) logon to run the task on behalf of the specified user, but without having to store the password. Since the Task Scheduler runs within the local system account, it can create a S4U logon session and receive a token that can not only be used for identification, but also for impersonation on the local computer. Normally a S4U token is only good for identification.

The confirmation of the above issue can be found the FeedbackHub and on the Answers forum . If you are affected by the bug, you can check whether it is due to this service using PowerShell.


  1. Open PowerShell as Administrator.
  2. Copy and paste the following: Get-ScheduledTask | foreach {If (([xml] (Export-ScheduledTask -TaskName $ _. TaskName -TaskPath $ _. TaskPath)). GetElementsByTagName ("LogonType"). '# text' -eq "S4U") {$ _. TaskName} }
  3. In the output, see if you have any of such tasks. If you have some, try to disable them one by one to find the task that gives you the issue.

The user explains it further on bugs.chromium:

This is because the RPC that UBPM uses to create the S4U token can sometimes delete your saved credentials in lsass. Amongst other things, your saved credentials (or rather, the hash of them) are used to generate your DPAPI user encryption key, and when they're deleted lsass just uses the hash of the empty string (!!).

Several comments have confirmed that this workaround works.

Check out the following resources.


Support us

Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:

If you like this article, please share it using the buttons below. It won't take a lot from you, but it will help us grow. Thanks for your support!


Author: Sergey Tkachenko

Sergey Tkachenko is a software developer who started Winaero back in 2011. On this blog, Sergey is writing about everything connected to Microsoft, Windows and popular software. Follow him on Telegram, Twitter, and YouTube.

5 thoughts on “A bug in Windows 10 version 2004 prevents cookies and logins from being saved”

  1. A rather harmless bug compared to the “fix” for the Disk Optimizer not saving its runs — that update breaks your ability to open a number of file types from within saved searches.

    I’m not the only one with this problem, I checked the abysmal answers forum. I also replicated it in two virtual machines.

    Leave it to MS to provide a fix for a severe flaw, only to replace it with another disaster.

  2. Hi

    Thanks for the info. What about the Alt + Tab bug, that messed the order of windows if you quickly alt-tabbed the 2 most recent windows? It is still here on 20H2, which introduced the new Microsoft Edge in Alt+Tab crap. Only workaround I have found so far is to disable the Alt+Tab dialog altogether and force Explorer to use the legacy one. As far as I know, this bug was fixed in some Insider version of Windows 10 (build 20231 to be more precise – Will this ever be backported to stable versions, what do you know about this?


  3. Your PowerShell command is malformed as there are extra spaces in it. It should be: Get-ScheduledTask | foreach { If (([xml](Export-ScheduledTask -TaskName $_.TaskName -TaskPath $_.TaskPath)).GetElementsByTagName(“LogonType”).’#text’ -eq “S4U”) { $_.TaskName } }

Leave a Reply

Your email address will not be published.

Using Telegram? Subscribe to the blog channel!
Hello. Add your message here.