Microsoft solves the forced reboots problem in Windows 10
In the fall of last year, some users encountered the random restart problem of Windows 10. This problem often occurs and may also cause users to be unable to save files in time.
When a problem occurs, the system will pop up “PC will automatically restart”. If the user’s hand speed is not fast enough to save all the work content, it may be lost.
What troubles many users is that this kind of random restart problem occurs frequently, and the system does not clearly indicate where the problem occurs in the error message.
According to Microsoft’s explanation, the problem may only affect some specific devices, so Microsoft directly prevented these devices from upgrading to the latest version based on stability considerations.
Microsoft stated in the latest support document that the problem has been fixed, and the fix will be directly integrated into the latest version of the system image to provide users.
The main affected is the Windows 10 20H2 version. Now the fix has been integrated into this version. Users need to download the latest version of the image before upgrading.
At the same time, devices previously affected by the problem cannot be upgraded to the latest version. Now it has been resolved. Microsoft has lifted the restrictions on the server so that users can upgrade.
What needs to be emphasized is that users who have already upgraded cannot solve the problem through the repair program. Either roll back the system and re-upgrade or reinstall the system directly to solve the problem.
This time Microsoft also solved the LSASS.exe error encountered by some users, which usually appears when users log in to the system or open some control units.
For example, when the user accesses the login option settings, an error will pop up in LSASS.exe, and the error will also occur and your PC will restart within 1 minute.
An error with ID 1015 can be found in the event log, and the error status code is C0000374, which is related to the error or damage of the stack.
The reason for the above-mentioned problem after an investigation is that the system uses the same security identifier and relative identifier to create duplicate built-in user accounts during the upgrade process.
This kind of identifier is unique in use and cannot be conflicted, so if the system mistakenly creates a duplicate account, it will cause conflicts for the currently logged-in user.