lsass.exe error loop at bootup

[Dr. Scruffy]

I just had the same problem as of this morning, but I just fixed it! I found this article at the knowledge base of MS's support site: http://support.microsoft.com/default...;en-us;q324762 http://support.microsoft.com/default.aspx?scid=KB;en-us;q324762 OK I've tried entering in the hyperlink twice, but it doesn't seem to take. Anyhow the article # is 324762. You will have to use the recovery console of the XP installation disk. It appears the problem involves the msvcrt.dll. I unregistered it a couple of days ago when I wanted to remove ctfmon.exe from startup permanently. However, if that wasn't the reason, then it was because I installed some new hardware last night. When I turned my computer on this morning the first problem was that I couldn't receive any info from the internet. I think I ended up checking every phone line in the house! So then I loaded my second installation of windows to check it out. I was able to access the internet just fine. However, when I went back and loaded the original copy of XP I know got a error about lsass.exe not having a valid endpoint. Well enough blather I hope this helps all who need it. Word of advice: If you have enough room, partition and install a second copy of your OS. I did on a 5 Gig partition. This has saved my but so many time I can't even count!!

[poohbeer]

Found a working sollution at http://computing.net/windowsxp/wwwbo...rum/46198.html
Had to make a few variations on that post but the idea was the same so you should be able to work this out yourself too.

If I'm correct what this does is simply a system restore but then not only once like the bootup choice let's you do but up to 4 times (in my case).
If anybody thinks this is not so, please let me know.


And if this little bit is the sollution for you, please post a message here.

and now the texst just in case the other site goes down

Name: TripleA
Date: October 27, 2002 at 02:21:16 Pacific
Subject: Fix for lsass.exe & related errors.
OS: Windows XP
CPU/Ram: Any

Comment:
After leaving my PC to download overnight, i rebooted in the morning only to get and error similar to:
"lsass.exe system error - invalid parameters passed to function or service"

I thought WTF? and after a few reboots i knew it was screwed. My guess is that someone has hacked me (for what reason i will never know) or i had been infected with some kind of p00fter virus.

Now this got me angry. But most of all i wanted to use my PC again, without having to fdisk, format etc.

So i traced the problem back to a few of XP's startup files which are loacted in windows\system32\config. Now these files contain information about your software, user accounts, and many other things. This is why you are unable to alter or modify them from within windows itself.

BUT this is where you have to be tricky. You could either get your hands on another Hard Disk with XP, or use something like ntfsdos. Basically you will need something that can read your Hard Disk.

Anyway after fooling around for a bit i came across a folder that i had never really taken much notice of. Its:

c:\System Volume Information

This is a hidden and protected folder that amazingly enough keeps what are know as system restore points for you. Basically it takes note of nearly everything you do.

In this folder there will be some wierd looking folders like:

_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}

if you browse through these you will find other files named something like RP01 or RP35, etc...

Bascially find the one with the highest number and in it will be another folder named snapshot, and in this folder are the files which you need to recover your system:

_registry_user_.default
_registry_machine_security
_registry_machine_software
_registry_machine_system
_registry_machine_sam

copy these files to a temp directory and rename them to:

default
security
software
system
sam

now you will need to delete the offending files in c:\windows\system32\config and replace them with the new files.

If you get the same error go back and choose another folder (the RP01 etc) to restore from.

After doing so you will be able to boot up and use your PC again.

[Golgo1]

I also had probelms with lsass.exe in my Satellite laptop, but I managed to get at my files and at least burn them to back up. I'm not sure if this will work everywhere, but this is what I did:
I installed Win2000 right over XP (on the same partition), which left all my files because 2000 uses an NT directory as default install, XP uses Windows. anyway, 2000 up and ran quite well actually, but wouldn't allow me to access any of my XP protected files. If you log in as Administrator in 2000, and you can find your XP files, you can force the ownership over to you, giving you full access to them, and since 2000 is running fairly stable, you can burn backups, or transfer over netwrk or whatever. reply if you need to know how to take back file/folder owneship in 2000. After salvaging data, I did have to wipe my drive and re-install XP(the laptop will only run 100% with XP) Hope this helps save some data that Microsoft doesn't seen to care too much about

[KalahariHarry]

Creating Windows XP setup disks http://support.microsoft.com/default...b;en-us;310994

After booting to a graphical user interface
Choose the repair option

For more help and commands on the recovery console

http://support.microsoft.com/default...b;en-us;307654

Following commands

bootcfg /rebuild

If that option does not work. Load recovery console again

chkdsk /p
fixboot
exit

if still faulty another command to use is

chkdsk /r (this will take longer)
exit
mbr (use option with care)

If how ever it's a service that requires enable

Then use “enable" handy if your service has been turned off

enable service_(name of service)

You might need to allow certain things

Type set (to see what the options are set to

eg.
set allowwildcards=true (example)

saving from C: to A: remember only 8.3 characters

c:\mydocu~1 as an example

To access NTFS drives I use a program called NTFSDOS
(a google search will get the file)

Known XP problem, yes, known repair, unfortunately, Not Yet

[LoneStarr]

I have had the same experience. I managed to fix it.

Insert at bootable WinXp CD and choose the system restoration option. At some point the program will exit to the command promt and query what windows installation to boot from. Type the number of your crashed WinXp version. The program will then ask you to type in the adminstrator password. Do that and restart your computer and it should be fixed.

Don't ask me why, but it worked for me.

[brasonkidfartdog]

hey this problem i hate greatly. I have fixed my computer thought, if you have an HP that came with WinXP Restore on the HD and not a cd, and your computer keeps the reboot cycle, what do you do? easy when rebooting push F10 right after your BIOS inits. and the HP RESTORE will pop up, but then youll have to do a destructive recovere, i tried non destructive and still had same problem, luckily i just finished moving all data across network before this dumb problem. Fix it Bill

[smithlr]

Got the old lsass.exe last night on a neighbours computer. Windows XP has got to be the worst software ever. "Safe Mode" is totally useless. I had loaded MS Powerpoint and that was it.
I put the XP setup disk in the CD and started it. Somewhere in the setup it asked if I wanted to "install" XP or to "repair" it. I chose to "repair". It took about 30 - 35 minutes but up it came. I rebooted and all was well. All files and data, including the desktop were all there. The software I loaded before the crash was also there and useable.
It takes a brave man sometimes. I had contacted Dell to help out but as soon as I said I had loaded software, they dropped my call like a hot potato.
I breathed a big sigh of relief when it all came back.
"It's alive, it's alive!!

[runningonempty]

My problem with lsass.exe started recently. I have couple XP PC's that are experiencing this problem. http://support.microsoft.com/default...b;en-us;324762
On all effected machines for some reason msvcrt.dll was replaced with ver 6.1.8637.0 which according to Microsoft DLL database is relative in Microsoft 2K OS family and Win ME. I have no idea how the original msvcrt.dll (ver 7.0.2600.1106 for WinXP + SP1 & ver 7.0.2600.0 Win XP -SP1) got replaced with the lower version. Users of those machines informed me that the WIndows File Protection box came up wanting replace some of the protected files with correct versions. They didn't have the XP CD so they clicked cancel. After that system wanted to restart and than after the reboot all they would get is pointer, empty desktop and lsass.exe error message. I'm not sure why Windows requested CD for this, because I checked dllcache in WINDOWS\SYSTEM32 dir and some of PC's had the correct file version there. ???? My solution was to replace the msvcrt.dll with the correct version. So I used ERD COmmander and replaced the file. Which I extracted from working machines You can also grab it from XP CD I386\ASMS\7000\MSFT\WINDOWS\MSWINCRT folder. . Probably most of you will have to use Recovery Console which is text based. I'm going also put those files in the dllcache dir, just in case some program will try to replace msvcrt.dll again ( Good luck and please post your results. I'm still interested in learning how this method will turn out.

[samsol15]

This is all a bunch of bullsh*t, seriously i have tried everything on this page but none of it seems to work. A have put in the windows xp home edition cd but it has blocked all access off it. I think i got my virus through Kazaa, did anyone else use Kazaa because this is very irritating. A have also accesed the BIOS thing at the start but dont know what to do, my computer won't let me logon and it doesn't even go to the username part. It keeps sayin Isass.exe File Missing or sometin like dat. PLEASE HELP!

[chilock]

seems like this is becoming common problem - just to add my situation - satellite laptop - wirless internet connection stopped working - rebooted after looking around for possible problems - getting the lsass.exe wit the password thingy and continual rebooting - none of the option let me in - will keep searching for fix- sucks that so many are having same problem-------could a virus have caused this i do have macafee firewall running 24/7