Another day, another Windows 10 glitch. Microsoft has acknowledged a new critical issue affecting Windows 10 PCs with the distribution of the June 2020 cumulative update. The update is causing serious problems that lead to unwanted (and seemingly random) automatic reboots, often with little warning.

The latest KB4557957 or KB4560960 update is intended to patch some of these problems, but seems to have caused as many problems as the buggy system update that was supposed to fix them.

According to Microsoft's recently updated documentation, the problem is related to a bug in the Local Security Authority Subsystem Service (LSASS) file (lsass.exe), which displays an error message.

On computers affected by this bug, the following message appears: "A critical system process, C:ⅳWINDOWSⅳsystem32ⅳlsass.exe, failed with status code c0000008. Reboot machine. The machine must be restarted. [This results in an unexpected reboot, which not only interferes with work during the reboot process, but also erases unsaved data and may even render the machine unusable for an extended period of time.

According to the latest documentation, "Microsoft is working on a solution and will provide an update in a future release. Translation: No good fixes yet.

Until Microsoft has a solution, the only way to resolve this issue is to uninstall the offending update. This can be done in the "Update and Security" menu under "Settings" on a Windows PC.

1. go to Settings > Update and Security > View Update History

2. select "Uninstall an Update"

3. from the recent entries, select Update for Microsoft Windows (KB4557957) or Update for Microsoft Windows (KB4560960)

Look for either Select the update and click "Uninstall"

This issue specifically affects the latest KB4557957 or KB4560960 update, but Windows 10 since the introduction of the Windows 10 May 2020 update, has been plagued by issues including unwanted logouts from Google Chrome and other problems. This latest patch, the first since the May 2020 update was distributed, was intended to address some of these issues, but it seems best to wait until these issues are further fixed.