Google is investigating the logout issue of Google Chrome in Windows 10 v2004
Some users who have upgraded to Windows 10 Version 2004 may have encountered a Google Chrome login account and then forced to log out after closing and opening the Chrome browser again.
In order to ensure that the data can be synchronized normally, the user must re-login, but even after closing the Google Chrome again and then reopening, a similar problem occurs. No matter how many times the user tries to log in, the problem cannot be solved.
During the beta version, users gave feedback to Microsoft and Google, but Google engineers could not reproduce the problem, so Google decided not to investigate the problem.
Google security engineers encountered the same problem a few days ago, which prompted the Google browser development team to restart the investigation, and Microsoft has not yet confirmed this problem.
Microsoft added Data Protection API (DPAPI) in Windows 10 Version 2004 to protect users’ confidential data. This feature currently only supports Windows 10 Version 2004, so earlier versions will not encounter similar problems unless users are planning to upgrade to a new version in the near future.
The DPAPI function is designed to protect users’ private keys, stored passwords, and other credentials generated in Windows 10 and other confidential information from being stolen by malware.
After all, Google is still investigating and Microsoft has not confirmed the problem at all, so the specific reasons have to wait for the follow-up investigation results.
If you encounter this problem, you can now try to recover through the following methods. If they are lucky, you may not be forced to log out after logging in.
If you look in Event Viewer, under Windows Logs > Applications and Services > Microsoft > Windows > Crypto-DPAPI > Operational, do you see any errors?
If the answer is yes, try this:
Close all Chrome Windows
Lock (Press Win+L) your Workstation
Unlock, then start Chrome, does it work then?
I think locking flushes the dpapisrv master key cache, so if that workaround works that narrows down the problem.
