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 KB5049981 update released with new BYOVD blocklist (source)
- Microsoft ends support for Office apps on Windows 10 in October (source)
- Windows 11 24H2 now also offered to all eligible Windows 10 PCs (source)
- January Windows 10 preview update force installs new Outlook (source)
- Windows 10 KB5051974 update force installs new Microsoft Outlook app (source)
- Windows 10 KB5052077 update fixes broken SSH connections (source)