Home News Troubleshooting Windows Update Killed Chrome

Troubleshooting Windows Update Killed Chrome



If you killed Windows Update Chrome on your PC, this guide will help you fix the problem.

One of Microsoft’s Windows 10 updates was so bad that it broke Google Chrome. Google announced that Microsoft has successfully bypassed an important security feature in all Chromium-based web browsers, including Chrome, with the Windows 10 1903 update. This is the Chromium sandbox.



In May 2020, Microsoft released the last major update for Windows 10. As an unfortunate side effect of the Windows 10 May 2020 update, some users reported noticeable issues with the Google Chrome browser.

After the Windows 10 May 2020 update, some users of Reddit and Google Help Forums noticed that the browser stopped syncing and returned to a disabled state upon restart. This does not affect bookmarks, but it does affect the data you save in your Google account to sync with smartphones or other computers.

Apart from what is perhaps most annoying, this issue also clears cookies from your computer. That being said, the websites treat this Chrome browser as a fresh install and prompt users to sign in every time they restart their computer.

As TechDows points out, Google was aware of these issues with Chrome even before the May Windows 10 update. The April Chromium Bug Report details what Google is aware of the issue. Two months later, the company is still investigating the matter.

GeneralNew from 10/12. Almost four months after the first report of this issue, it still occurs. Some users are still having problems with the latest versions of Windows when using Chrome, and it looks like Google and Microsoft don’t have a clear solution.

Fortunately, there is a new workaround that seems to fix the issue and expose a potential source. Discovered by TechDows, a user commented on a Chromium thread to indicate that the “S4U” task in Windows Task Scheduler will force Chrome to return passwords and other data. Microsoft explains in more detail what the “S4U” task is. In short, it allows the computer to perform tasks as a local system account. User explains:

This is because the RPC used by UBPM to generate the S4U token can sometimes delete your credentials stored in lsass. Among other things, your stored credentials (or rather a hash) will be used to generate your DPAPI user encryption key. Once removed, lsass only uses the empty string hash (!!).

Honestly, it’s over By my head, but other thread users are reporting that disabling these S4U tasks solves the problem. In particular, at least one Microsoft technician responded to the comment that he is considering this solution. To try this for yourself, open a PowerShell window as administrator and paste the command below. Then remove all listed tasks from the task scheduler.

Get-ScheduledTask | foreach {If (([xml] (Export-ScheduledTask -TaskName $ _. TaskName -TaskPath $ _. TaskPath)). GetElementsByTagName (“LogonType”). “# text” -eq “S4U” €) {$ _. TaskName}}

If you encounter this annoying problem, give it a try!

The original article follows.

If you’re using Chrome on Windows 10, it’s probably best to avoid the May 2004 update until the issues are resolved. To do this, go to Settings> Update