INTRO: The Tech giant Microsoft has started bringing out Windows 10 May 2020 update last month. The latest update has apparently caused issues with the Google Chrome browser somehow.
As mentioned by the reports from Google Help and Reddit, the new windows 10 update has broken Google Chrome’s sync functionality. The Chrome signs users are out of their Google accounts, which is forcing them to sign in again and again. Also, the google browser is not making use of the cookies, thereby signing users out of several websites and causing issues for the windows users.
A Reddit user wrote: “When I restart my computer, I’m not signed into my Google account and when I start Chrome. All of my website passwords are also forgotten and signed out. I also get the welcome page for one of my extensions that is for the (Adobe Acrobat extension for Google Chrome). This doesn’t happen only when I restart just the Chrome, but when I go for Windows + Chrome restart”.
Microsoft has currently not added the sign-in bug to its list of known issues for now. But, Google Chrome’s team is currently working to figure out a fix for the users. There is an issue titled “TokenService which fails to load, that is mainly causing cookies and sync to reset” in Chromium Bugs since the month of April.
If you are a Google Chrome user who has not updated to Windows 10 version 2004 recently, we would suggest that you may pause the update to stay on the safer side. To do so, go to the Settings -> Update & Security -> Windows Update -> Pause updates for 7 days. You can pause the update for a maximum of 35 days and be on a safer side until all of the bugs and issues get resolved.
The latest mentions from Microsoft is that the issue is not limited just to Chrome. It may have also affected Microsoft’s default Mail app or the OneDrive app, and on Battle.net client also.
If you’re also facing the above-mentioned issue, you may try the workaround suggested by Google security researcher Tavis Ormandy. “Try this step: Close all Chrome windows, Lock (Press Win+L) your Workstation, Unlock, then start Chrome. I think locking flushes the dpapisrv master key cache, so if that workaround works that narrows down the problem.”