Security News > 2020 > November > Windows 10 20H2 LSASS crash issue causes forced reboots
Microsoft has acknowledged a new known issue causing forced restarts on Windows 10 20H2 devices due to the Local Security Authority Subsystem Service system process crashing.
"To prevent the issue and not receive the safeguard hold, you will need to name all built-in user counts back to their default name before attempting to update to Windows 10, version 2004 or Windows 10, version 20H2," Microsoft says.
While a full fix for this issue is not immediately available as Microsoft has just started investigating it, you can work around it by going back to a prior Windows 10 version using instructions available here.
"You will then need to update to the later version of Windows 10 after the issue is resolved."
Today Microsoft applied an additional compatibility hold due to a second issue affecting devices running Windows 10 2004 or 20H2 and causing crashes with blue screens when users plug in a Thunderbolt NVMe Solid State Drive.
News URL
Related news
- Windows 10 KB5041580 update released with 14 fixes, security updates (source)
- New Windows 10 22H2 beta fixes memory leaks and crashes (source)
- Windows 10 KB5041582 update released with 5 changes and fixes (source)
- Windows 10 KB5043064 update released with 6 fixes, security updates (source)
- Microsoft says it broke some Windows 10 patching – as it fixes flaws under attack (source)
- Windows 10 KB5043131 update released with 9 changes and fixes (source)