New Windows 10 bug causing serious issues

[Hanno Labuschagne]

New Windows 10 bug causing serious issues
https://twitter.com/intent/tweet/?t...-causes-serious-problems.html&via=mybroadband
Microsoft has confirmed that the June 2020 Patch Tuesday update for Windows 10 is causing some users to encounter errors that require a restart.

This follows numerous complaints from users who said they were being forced to restart their computers due to receiving an error message.

The error message reads as follows:

A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000008. The machine must now be restarted.

 

[nan0s0ldier]

99 little bugs in the code, 99 little bugs in the code. Take one down, patch it around 117 little bugs in the code.

 

[Herr der Verboten]

i demund my massive issues

 

[Binary_Bark]

Pro-tip. Don't install windows

 

[wroemwroem]

I had issues like this on 1809 LTSC from May 2020. After cold boot (fast startup), just after clicking OK at the login screen to log in, the screen and start menu flashes consistently, never showing the desktop. After about 10 seconds, a message pops up saying a critical process died, and that the PC must restart. On second boot it works fine.

Workaround: Disabling fast startup resolved the issue.

It seems like when you shut down your PC, you're logged out, but the kernel hibernated. Upon resume, I figure some drivers are not loaded correctly, leading to the logon service hiccup.

BSOD is not generated, but there are events written to the event log, but I'm not 100% sure how to interpret that.

Since my issue is resolved for now, I didn't bother going into further detail. Might as well have been my laptop's aging graphics drivers.

Edit: hybrid boot - > fast startup (got confused between the terms)

 

[Purply]

Same @wroemwroem , I just stopped shutting down my pc and instead just put it in sleep mode until they release another patch that hopefully fixes it.

 

[system32]

I had issues like this on 1809 LTSC from May 2020. After cold boot (fast startup), just after clicking OK at the login screen to log in, the screen and start menu flashes consistently, never showing the desktop. After about 10 seconds, a message pops up saying a critical process died, and that the PC must restart. On second boot it works fine.

Workaround: Disabling fast startup resolved the issue.

It seems like when you shut down your PC, you're logged out, but the kernel hibernated. Upon resume, I figure some drivers are not loaded correctly, leading to the logon service hiccup.

BSOD is not generated, but there are events written to the event log, but I'm not 100% sure how to interpret that.

Since my issue is resolved for now, I didn't bother going into further detail. Might as well have been my laptop's aging graphics drivers.

Edit: hybrid boot - > fast startup (got confused between the terms)

Also had a similar issue as yours with 1809 on my work laptop and work PC.
After about 10 seconds, a message pops up saying a critical process died, and that the PC must restart.
I had to unplug the PC from the network for it to boot.
Never tried the hybrid boot/fast startup thing.
I suspect when PC was imaged loaded with Win10 (previously Win7), the uefi was not cleared and still had fragments of McAfee encryption.

The problem went away after a few months - I don't reboot too often.
I suspect MS updated \efi\Microsoft binaries and fixed my problems.
mountvol z: /s shows new binaries.

EDIT: Found the event log from Feb 2019

The previous system shutdown at 09:21:51 on 2019/02/07 was unexpected. -- The process wininit.exe has initiated the restart of computer AAAU2SRP362 on behalf of user for the following reason: No title for this reason could be found Reason Code: 0x50006 Shutdown Type: restart Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073741819. The system will now shut down and restart. -- A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted. -- Faulting application name: lsass.exe, version: 10.0.17134.376, time stamp: 0x0951607c Faulting module name: ntdll.dll, version: 10.0.17134.471, time stamp: 0x7e614c22 Exception code: 0xc0000005 Fault offset: 0x0000000000024989 Faulting process id: 0x320 Faulting application start time: 0x01d4beb5cae25bda Faulting application path: C:\Windows\system32\lsass.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 44402972-5573-4da4-b576-35f7204f5d0b Faulting package full name: Faulting package-relative application ID:
MS really needs to sort out the testing.

 

[Sl8er]

June 15:

Looking forward to the next episode!

I heard "What.can.we.break.on.the.next.windows.update.S16E07.1080p.HDTV.x264.mkv" might be a good one!

June 25:

So, "What.can.we.break.on.the.next.windows.update.S16E07.1080p.HDTV.x264.mkv" turned out to be alright.

Wonder what "What.can.we.break.on.the.next.windows.update.S16E08.1080p.HDTV.x264.mkv" is going to be like!