Microsoft admits June Windows 10 Patch Tuesday updates causing crashes
Another Windows 10 Update is causing crashes to people's systems.
What you need to know
- June's Patch Tuesday updates to Windows 10 are causing PCs to crash.
- The bug is caused by a failure in the Local Security Authority Subsystem Service file Isass.exe.
- The issue affects devices running Windows 10 version 1809, 1903, 1909, and 2004.
Microsoft confirmed recently that its Windows 10 Patch Tuesday updates in June cause system crashes for some PCs (via ZDNet). The issue is caused by a failure in the Local Security Authority Subsystem Service (LSASS) file Isass.exe. The bug affects PCs running Windows 10 version 1809, 1903, 1909, and 2004. It's unclear how many PCs are affected by the issue at this time, but Microsoft is "working on a resolution and will provide an update in an upcoming release."
Microsoft outlines the problem in the support documents for Windows 10 versions 1809, 1903, and 2004. The support documents state:
Microsoft also states that the out-of-band update that shipped on June 16 is affected by the LSASS issue.
Microsoft is working on a fix for the issue that will "provide an update in an upcoming release." At this time, Microsoft has not confirmed if the issue affects earlier versions of Windows 10.
Microsoft recently announced that optional cumulative updates will resume in July, so there's a chance that a fix for the LSASS issue could roll out in an optional cumulative update.
Get the Windows Central Newsletter
All the latest news, reviews, and guides for Windows and Xbox diehards.
Sean Endicott is a tech journalist at Windows Central, specializing in Windows, Microsoft software, AI, and PCs. He's covered major launches, from Windows 10 and 11 to the rise of AI tools like ChatGPT. Sean's journey began with the Lumia 740, leading to strong ties with app developers. Outside writing, he coaches American football, utilizing Microsoft services to manage his team. He studied broadcast journalism at Nottingham Trent University and is active on X @SeanEndicott_ and Threads @sean_endicott_.