Lsass exe failed with status code 128

Those are good details and I will think about it and try to recreate it. I already shared what I have in my notes for that issue so need to recreate it again. While you are waiting not just for me you could do some Google searches on the error messages and get some ideas from search results with similar errors that do not involve BearShare that one I have seen. With your "arsenal", you should be in good shape. I was googling for hours, but I didn't find anything useful.

The truth is that I google a lot even before I go to forums. So that I write here means that I'm really desperate. I see there are a lot of experts here, I hope some of them knows a bit more about the internals of Windows OSs.

I suspect, the methodology we use is inexpedient. We're using a kind of blackbox technique, like "Is XY installed that might interfere?

In this case, I think it would be more effective to examine the problem in further depths. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Are you given a countdown timer until XP shuts down? What happens when you try to boot in Safe Mode? Show 1 more comment. Active Oldest Votes. Soonts Soonts 17k 9 9 gold badges 51 51 silver badges bronze badges.

Add a comment. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related Care to try it in the name of science? I'm joking, please don't try it!! Once the hard disk is attached to the new system, navigate to the file structure to where the Lsass. To check if the malware process has been terminated, close Task Manager, and then open it again. Another option is to connect the affected hard drive to another system.

I was unable to do this so good luck! I'm gotten rid of it and updated as many things as possable. Read everything I just posted above you. Welcome to OZZU and good luck. It's possible the issue is more likely to happen soon after a reboot, but I don't have enough datapoints yet to confirm. The two most recent lsass terminations both happened within 12 hours after a reboot of the server, however in some of the cases there were already a number of users logged on and working for several hours before lsass died.

Possibly there is one or more user whose profile triggers the failure when they log on to the server. Going to try removing KB and see if that makes any difference. Glad to see they're aware of the issue! Products 72 Special Topics 41 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity. Microsoft Edge Insider. Azure Databases. Autonomous Systems. Education Sector. Microsoft Localization. Microsoft PnP.

Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work. Small and Medium Business. Humans of IT.