Forum Discussion
Windows 10 Restart after Login
- May 28, 2020
lpham did you installed Windows 10 May 2020's updates?
I have several users got the same issue after this month's patches installed.
Exactly the same error message in Event log.
The patches we installed are: KB4551853 & KB4556441
We're still looking for a resolution.
Just noticed if user turn off PC fast start seems not having this issue anymore, not sure if this is a work around.
Thelink73 MS provided us with a private hotfix for limited testing for a few days that seems to have resolved the issue. However, it is not included in June Tuesday patches. As we would like our test PCs to received regular June patching, the recommendation is to always remove any private hotfix before Before we can receive the We had to remove the private hotfix before installing a public release patch to avoid the potential issues.
Microsoft Support has now informed us that the fix is tentatively scheduled for July’s patch release cycle.
We have advised users' PC that is affected by this issue to use a workaround with putting PC to "Sleep" for overnight instead of Shutdown PC daily to avoid the daily crashes.
We're experiencing same issue.
- ppbooJun 12, 2020Copper Contributor
Marius6299 Yes, we have an MS case open and have tested a private Hotfix that seems to address the problem. We have to remove the private hotfix to allow the latest June CU to installed. MS has informed us that the fix is tentatively scheduled for July Cumulative updates.
- dyeLuckyJun 12, 2020Copper Contributor
Marius6299 I opened a ticket on this too; uploaded event viewer logs and can confirm the following:
- All PC's with issues are Windows 10 1809
- kb4551853 may be the culprit, as we are finding that lsass.exe keeps failing; I requested that our service desk uninstall this patch and keep me posted
- Restarting the PC helps the issue
Additionally, I referenced this article with in the ticket, so Microsoft SHOULD be watching. 🙂
- Marius6299Jun 15, 2020Copper Contributor
Thx. I've also referenced this thread and reported to our dedicated MS PFE as well.
We've tested removal of kb4551853 as well. Got a mix bag of results.
Hopefully a fix can be found soon.