Please register or login. There are 0 registered and 1052 anonymous users currently online. Current bandwidth usage: 326.30 kbit/s November 29 - 12:40pm EST 
Hardware Analysis
Forums Product Prices

  Latest Topics 

More >>


  You Are Here: 
/ Forums / Software /

  lsass.exe-system error 
 Date Written 
Continue Reading on Page: 1, 2, 3, 4, 5, 6
Ryan Synik Apr 04, 2007, 09:47am EDT Report Abuse
>> Re: lsass.exe-system error
Hi. I'm new here, so please if I'm irritating you guys just tell me. I have a Q.

My computer was suffering from a lsass.exe error. So I re-installed windows.
Will any other stuff I have(on my Desktop and such) be OK?

Want to enjoy less advertisements and more features? Click here to become a Hardware Analysis registered user.
Matt Moore Jun 03, 2007, 09:39am EDT Report Abuse
>> Re: lsass.exe-system error
My issue is the same as the rest. I followed most of the steps from;en-us;307545. Unfortunetly, I skipped a few steps. Now I'm getting an error "Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
You can attempt to repair this file by starting windows set up using the original set up CD-ROM.
Select 'r' at the first screen to start repair."
I'm not sure what to do..

Shadow_Ops_Airman1 Jun 03, 2007, 09:49am EDT Report Abuse
>> Re: lsass.exe-system error
there are 2 services in windows that share the same name.

AMD Athlon XP-M 2500+ (133x14= 1867MHz) (209x11= 2299MHz)
DFI LP NF2 Ultra-B (Hellfire 3EG Rev2)
Antec SX800, Neo HE 500, 4 Antec 8CM Fans
Thermalright SI-97 1 Antec Tricool 12CM Fan
CL SB XFi Xtreme Music
2x Barracuda HDs (250/400)
2x Samsung Write
Shadow_Ops_Airman1 Jun 03, 2007, 10:10am EDT Report Abuse
>> Re: lsass.exe-system error
ok if you have the original Windows CD, have your CD drive set as first boot device, insert your CD press any key to boot the CD, once it gets done with its processing it will give you options, Install Windows, Repair and i believe restart system. well you Press the R command, you may have to log into administration account but follow directions on screen, if you need help type in -? or /? if im not mistaken for some basic help. Course you may find info on the Recovery Console at microsofts site.

AMD Athlon XP-M 2500+ (133x14= 1867MHz) (209x11= 2299MHz)
DFI LP NF2 Ultra-B (Hellfire 3EG Rev2)
Antec SX800, Neo HE 500, 4 Antec 8CM Fans
Thermalright SI-97 1 Antec Tricool 12CM Fan
CL SB XFi Xtreme Music
2x Barracuda HDs (250/400)
2x Samsung Write
Steven Scharf Jun 03, 2007, 12:48pm EDT Report Abuse
>> Re: lsass.exe-system error

Matt Moore Jun 04, 2007, 02:13am EDT Report Abuse
>> Re: lsass.exe-system error
I tried these steps earlier but somehow messed a few things up. Now when I try the steps over again everything I type in the command prompt either says "No matching files were found." or "The system cannot find the file specified." I was able to boot into my computer at one time, but somehow screwed it up more to now I can't even follow the steps. I'm afraid this problem has become much more complicated. Perhaps if there was a way to reset the settings so I can redo the steps?

A B Jun 29, 2007, 06:31am EDT Report Abuse
>> Re: lsass.exe-system error
Is there any easier way to copy the SAM file than installing another operating system? Ie. any disk-based utilities?

Eric Shakespeare Jul 27, 2007, 06:20pm EDT Report Abuse
>> Re: lsass.exe-system error
After searching a bunch of sites and finding the "fix links" disabled or broken I found a link that is real user friendly and fixes the lsass error quickly. It's a lot eaiser then reloading XP and moving your data just to find out you missed something and now it's lost. Here's the link:

The following is a corrected version of Charlie White's excellent article and if the steps are followed exactly should resolve many problems and very often result in a repaired and fully functioning XP environment:
"PC users, you all know what it is: That dreaded Blue Screen of Death. That's right, the BSOD. You've installed a seemingly innocent application, restarted your computer, and suddenly you see this horror in front of your eyes: A big blue screen with some cryptic message on it. Try restarting again, same thing. You're dead. What will you do? What WILL you do?? Well, don't let it ruin your day. Remain calm. If you're using Windows XP, I can help you fix it. Come with me, down into the bowels of Windows XP, where only the high priests go. It'll be fun!

I'm going to show you how to bring your computer back to life, and restore it to the point where things went south. You might want to print this article and squirrel it away for that fateful day when this happens to you. Or if you don't want to print it (and who prints anything these days, anyway?), and you get a big ugly blue screen, just get on another computer somewhere and come back to this Web page for comfort and advice. I can get you out of this mess. I know, because I was in the same mess and I got myself out of it.

Here's what to do: First, get the Windows XP CD you used to install your operating system. By the way, this routine only works with Windows XP, either Professional or XP Home Edition. If you don't have a bootable XP CD, get one and have it with you at all times, because you never know when the dreaded BSOD might strike. But before you do anything with that CD, try restarting your computer again. Sometimes, for some odd reason, this works. Usually not, though. If you've tried that and everything else you can think of, and you can't even boot into Safe Mode, this is the mission for you.

Put the XP CD in the drive, and restart. When it says "press any key to boot from CD," go ahead, press any key and you're on your way to recovery. The Recovery Console, that is. If it doesn't give you a choice to boot from your CD drive, go into your computer's BIOS and make the adjustment for it to boot from CD. PCs brands and motherboards are too diverse for me to give you specifics on this, so follow the prompts and you can make that CD boot happen without too much trouble. Look at your screen when it boots up, and it always says "hit DEL for BIOS settings" or something similar. If you can't get it to boot from CD, just give up and call for support or take your computer to the nearest computer store for professional help.
OK, troops, are you still with me? Good. It'll look like you're re-installing Windows XP, but don't worry, you're not. This is just a screen showing you that your computer is loading enough files from the CD to actually do something, anything but that awful blue screen. Now when you see the screen that asks you if you want to install Windows, don't! Just hit R for recover, and you'll see the ominous Recovery Console. Don't let that intimidate you; the Recovery Console is your ugly, black-suited friend. It will have a dark, bleak screen, with the following stuff:

Microsoft Windows(R) Recovery Console

The Recovery Console provides system repair and recovery functionality.
Type EXIT to quit the Recovery Console and restart the computer.


Which Windows Installation would you like to log onto
(To cancel, press ENTER)?

Go ahead and hit the number 1 on your keyboard, or whichever number corresponds to the operating system you were using when havoc struck. Enter your administrator password, and then hit enter. You're in! Now it's time to run with the big dogs! Do not be afraid, dear reader, I am here to help you. By the way, if you don't know your administrator password, just try hitting the Enter key, and if that doesn't work, well, there's a fix for that, too. Just go to the following site and get the necessary tools to get you in:

If you type the following commands into your computer, it will work magic, akin to going back in time. There are three parts to this process, but believe me, they take much less time than reinstalling Windows XP and all your applications. So follow along with me, and keep in mind that each command must be typed exactly as you see it here. Please note that this procedure assumes that Windows XP is installed to the C:Windows folder. Make sure to change C:Windows to the appropriate windows folder if it's at a different location. The copy commands will answer you with a little "file copied" message. The delete commands just move on to the next line. Because of the way your Web browser displays individual lines, a command might look to you like it's two lines, so I've separated each command by an empty line. But anyway, type the whole command in one line, and when you've finished typing that command, hit the Enter key. Be sure to include the spaces I've included between each word here:

Section Addendum Note: In the following commands, we are simply copying some existing files to a temporary location. This way, if anything should go wrong down the line, you will at least still have access to the original files. These original files are not used again in this tutorial, but you should be aware that you made a backup copy of them in the folowing directory:

md c:\windows\tmpcopy c:\windows\system32\config\system

copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak
delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default

Important Addendum Note: When attempting the copy operations above, you may encounter an error message saying basically "unable to copy". The way arround this is to simply replace the copy (and delete) commands above with the following:
cd \windows\system32\config
rename system system.kpp
rename software software.kpp
rename sam sam.kpp
rename security security.kpp
rename default default.kpp
I use the extension .kpp becuase windows XP sometimes likes to use the .bak extension itself and unlike the copy commands above, we are not putting our backup copies in the windows tmp directory, but rather we are leaving them in thier original directory (but with the .kpp extension, so that windows will ignore them.). As I said before, these are just backup files, but it is good to know where they are if the repair fails and you ever need them. Note: The delete is no longer necessary becuase rename is basically like a "copy and delete" operation in one.

Section Addendum Note: In the following commands, we are simply copying some repair (basically default window install) files so that we can get windows XP to boot. (It will look awful and none of previous setup and programs will show up, but that is fine.) We simply need to make windows runnable so that we can do the next parts (that will retore our full configuration as it was prior to the crash).

copy c:\windows\repair\system c:\windows\system32\config\system
copy c:\windows\repair\system\software c:\windows\system32\config\software
copy c:\windows\repair\system\sam c:\windows\system32\config\sam
copy c:\windows\repair\system\security c:\windows\system32\config\security
copy c:\windows\repair\system\default c:\windows\system32\config\default

Now you can relax for a minute. You've made it through the first part! Way to go! Now what did you just do? I'll tell you. You first made a temporary directory called "tmp" (md tmp), and then into it, you copied all the files that boot up Windows. Then you deleted all those startup files, one of which is the stinker that got you into this mess in the first place. After that, you copied into that same place fresh startup files from a special repair directory. When you reboot, Windows will look for those files where it always does, and there won't be a stinker in the bunch. The only thing is, there won't be all your settings for all those applications you run every day, either. But not to worry. Right now, you're sitting in something like a lifeboat -- it's not the original ship, but it'll get you back to where you need to go. We'll get everything back to that comfortable place, but only after we go through steps 2 and 3.

Now type Exit and watch your computer restart into Windows XP again. Be sure not to tell it to boot from the CD this time. But wait. That's not the way you had XP set up before this disaster struck! That's OK. We're in a lifeboat right now -- this isn't your comfy cruise ship, not just yet. Hang in there. I'm going to show you how to restore your system to the way it was the moment before you told it to install that errant application, or whatever it was you did, so follow along and we'll go to part 2.

Part 2
Here's where you'll copy the saved registry files from their backed up location by using System Restore. This folder is not available in Recovery Console and is normally not visible -- Microsoft is protecting you from yourself by hiding it from you and locking it away from you. But we have the keys. Before you start this procedure, you'll need to change several settings to make that folder visible:

1. Start Windows Explorer.

2. On the Tools menu, click Folder options.

3. Click the View tab.

4. Under Hidden files and folders, click to select Show hidden files and folders, and then click to clear the "Hide protected operating system files (Recommended)" check box.

5. Click Yes when the dialog box is displayed that confirms that you want to display these files.

6. Double-click the drive where you installed Windows XP to get a list of the folders. It's important to click the correct drive.

7. Open the System Volume Information folder. This folder appears dimmed because it is set as a super-hidden folder. If you're using the FAT32 file system, this will be easy. If you're using NTFS, it won't let you open the folder, but here's how to get around that: Right-click on that system volume information folder and select Sharing and Security. Then click the Security tab. (No security tab? Skip two paragraphs.) Click Add, and then in the box that's labeled "Enter the object names to select," type the name of the user that's at the top of the Start menu -- that's probably you. [Damn it, why do they say object names when it's people's names? I guess that's Microsoft for you.]

Anyway, make sure you type the name the way it's listed there on the Start Menu. I made the mistake of typing my first name only and it wouldn't let me in. Type first and last name if that's how it's written on the top of the Start menu. After you've typed that in, click OK a couple of times and finally that monster will let you in.

But what if you don't see a Security tab? Try this: Click to select the checkboxes (Addendum Note: check BOTH checkboxes) in the "Network sharing and security" area -- one is labeled "Share this folder on the network" and the other is labeled "Allow network users to change my files." Change the share name to something short, like sysinfo. Then it'll let you in. After you're done with this entire rescue operation, you might want to go back and change these back to the way they were before, for maximum security. (Addendum Note: If you get an error when you change the name to sysinfo, and hit apply/ok, just try it again...that happened to me, but it worked on the second try with no problems.)

OK. Now here you are, in the inner sanctum where only the high priests go. Be not afraid, all ye who enter here. As Microsoft so eloquently puts it:

NOTE : This folder contains one or more _restore {GUID} folders such as "_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}".

8. Open a folder that was not created at the current time. You may have to click Details on the View menu to see when these folders were created. There may be one or more folders starting with "RP x under this folder. These are restore points.
Addendum Note: The System Volume is NOT a subdirectory the windows directory. So if you cannot find it, go up one directory level and look again.

9. Open one of these folders to locate a Snapshot subfolder; the following path is an example of a folder path to the Snapshot folder:

C:System Volume Information_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}RP1Snapshot

From the Snapshot folder, copy the following files to the C:WindowsTmp folder (you can use your mouse, you're in Windows now, remember?):
_registry_user_.default (Addendum Note: Notice the period (".") before the word default)

This is how Microsoft explains this: "These files are the backed up registry files from System Restore. Because you used the registry file created by Setup, this registry does not know that these restore points exist and are available. A new folder is created with a new GUID under System Volume Information and a restore point is created that includes a copy of the registry files that were copied during part one. This is why it is important not to use the most current folder, especially if the time stamp on the folder is the same as the current time."

Anyway, you're still not done. Don't worry, the magic is about to begin. Believe me, if you do this in front of your friends, they'll start thinking you're some kind of god. So, heavenly father, get ready to dazzle 'em.

Now it's time to place those files you just made visible to the Recovery Console where they belong. And to do that, we need to get back into the Recovery Console. So, make sure your CD is in the drive, and restart Windows, this time hitting any key when it tells you to do that if you want to boot from CD. Yes, you want to boot from CD, so you can launch your old cryptic pal, the Recovery Console. Type R after it goes through that file-reading routine that looks like an install but isn't. Then you're back into our dark-suited friend with its ominous command line. It's kinda like going into the basement to fix some broken pipe or something. But we're not scared. The command line is our flashlight and friend. Here we go:

Part 3
In part three, you delete the existing registry files, and then copy the System Restore Registry files to the C:WindowsSystem32Config folder:

From within Recovery Console, type the following commands:
Section Addendum Note: Here we are simply replacing those "default" repair files with valid and current restore point files. So we delete the old files (default) files and copy in the new files. If get errors when trying to delete, you can simply skip the delete commands and just do the copy (and when prompted to overwrite, type Y (for yes) and hit enter

delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\software
delete c:\windows\system32\config\default
delete c:\windows\system32\config\system

copy c:\windows\tmp\_registry_machine_software c:\windows\system32\config\software
copy c:\windows\tmp\_registry_machine_system c:\windows\system32\config\system
copy c:\windows\tmp\_registry_machine_sam c:\windows\system32\config\sam
copy c:\windows\tmp\_registry_machine_security c:\windows\system32\config\security
copy c:\windows\tmp\_registry_user_.default c:\windows\system32\config\default (Notice the period (".") before the word default in the first parameter

Now. You're done! Type exit and your computer will reboot into whichever restore file you chose. But wait. If it's not the right one, that's OK, you can now go into your System Restore area and pick a different restore point if you want. There's a whole calendar full of them in there. I bet you didn't know that Windows XP is watching just about every move you make, taking notes all the while. It can restore about any state you had on that machine. And the best part is, even when it's doing all that, it's still 10% faster than Windows 2000 according to our extensive tests here at the Midwest Test Facility. Here's how to get into that restore area if you're not happy with the current restore point:

1. Click Start, then click All Programs.

2. Click Accessories, and then click System Tools.

3. Click System Restore, and then click Restore to a previous Restore Point.

Sheesh, before this I hated the command line. Many of you probably still do. But when it saves your butt like this, you have to feel grateful. I should send out a badge of courage for all you intrepid souls who followed me into these dark gallows, the basement of Windows XP. I hope this routine was successful in bringing your computer back to life. I know how it feels to have your computer down for the count. As a wise old man once told me, "When your computer crashes, it's like your dog just died." He was so right. Excuse me now, I'm going to go get some work done on my Mac."

John Graffeo Sep 01, 2007, 12:05pm EDT Report Abuse
>> Re: lsass.exe-system error
I saw that some people had made an error of copying the system.bak file over to the system file in C:\windows\system32\config, and as a result when they went to run the recovery console with the windows recovery disc, it would ask for the administrator password, which would not work. Without the administrator password, you could not follow the instructions above. Also if you tried to start the computer normal, you would receive the lsass.exe system error "When trying to update the password, there was an error." and the computer would not load past that screen. It appeared that the only solution was to either re-install windows or find a program that allowed you to change the administrator password.

I had this problem, so I tried a number of programs to change the administrator password, none of them worked. Reinstalling windows was not an option. Luckily I was able to solve this mess and the computer is working fine, but unfortunately, the solution is not simple to explain.

I downloaded UBCD4Win and created an Ultimate Boot CD for Windows. On the CD I created, there was a program NFTS4DOS. Using this program, I was able to access the C: drive and go into the windows folder, C:\windows. I was also able to get into the System Volume Information folder, then into a restore point folder. Since this folder is a "folder" I had to use the dir /a command to see hidden folders. Once I got into the System Volume Information, I looked for the restore point folders mentioned in the instructions above. Once I found a good restore point folder (RP020 or whatever), I sought out to get the registry files for SAM, DEFAULT, SYSTEM, SOFTWARE and SECURITY.

Unfortunately, the file names in DOS are only 8 letters and since most of the names start off with the same eight letters it was hard to tell what was what. Your best bet is to find some software that allows you to view long file names in DOS. I did not have that handy, so I looked at the same files (system, software, security, sam and default) on someone else's computer and guage which ones you see in DOS are the ones you need to copy to C:\windows\system32\config. I copied what I thought were the right files, but unfortunatey, the file I copied as the system file was not correct. When I went to re-start the machine, the system file came up as corrupted.

At that point, I threw in the Windows Recovery disc and after it loaded I hit "R" for repair and it asked which configuration I wanted to repair, however, before it asked for an Administrator password, it stated that the Control Set of the registry was bad and gave me a C:\windows prompt. With that prompt, I simply followed the directions above and copy the right file into the C:\windows\system32\config. Now the computer is working again.

I know this message is choppy, but I am a novice at this. Bottom line. Try to get NFTS4DOS and see if you can access a restore point folder in dos and copy them into the config folder. If you don't get it right, Windows may not load, but you may get around the administrator password requirement.

Hope it helps.

Greg Buck Oct 27, 2007, 02:05am EDT Report Abuse
>> Re: lsass.exe-system error

Thank you so much for your detailed fix. I'm so glad that after scrolling through it to see it's gerth, I didn't shy away from it. It looks insanely more involved than it really is. I hope that anyone else suffering with this lsass issue will give your fix a chance. It works.

People out there, hear me now, the solution has been brought down from the mountain!! Eric (aka Moses) has brought unto you these commandments...erm...instructions...yes, instructions. He speaks the truth, and the truth shall set you, and your computer, free!!!

But I digress.

Anywho, your fix worked like a charm for me. Thanks again.

Btw, I was able to get into the recovery console without a problem. If someone is having a problem getting past the admin logon because of a fubar'd password, my suggestion for recovering/changing it is the Offline NT Password & Registry Editor. I've used it a number of times and it's never let me down.

Michael Khounani Nov 24, 2007, 05:24am EST Report Abuse
>> Re: lsass.exe-system error
The url for the "Charlie White "Windows XP crashed? Here's help"" article is changed to:

Mostafa Radwan Jan 31, 2009, 07:35am EST Report Abuse
>> Re: lsass.exe-system error
hi everyone,
I know that I am two years late, but I really need help with the "lsass.exe" problem
whenever I try to write this command in the recovery tool:
md c:\windows\tmpcopy c:\windows\system32\config\system

I get "the parameter is not valid"
I really need help fast as I don't know much about this windows setup stuff

Steven Scharf Jan 31, 2009, 11:30am EST Report Abuse
>> Re: lsass.exe-system error
That's not a valid DOS command.

Are you looking at ""?

Ian Steen Feb 28, 2009, 09:22pm EST Report Abuse
>> Re: lsass.exe-system error
Thank you Eric and John for the tips, but after reading both of your posts I still have some questions that I'm hoping you or someone could answer for me.

My computer won't boot to windows. When I turn it on it just goes to the Windows XP Pro edition Logo screen, then the screen goes black for a few seconds then reboots and again goes to the Windows XP Pro edition Logo screen. This process is repeated, again and again until I turn the computer off. I wanted to try to repair the installation that Eric posted instead of reinstalling as I do not want to lose my files as they are not backed up. The repair install is unfortunately not available on my Windows XP cd so I was going to try repairing xp using repair console following Charlie White's article but I'm afraid to try this because I have a OEM operating system and OEM XP cd. I have read in the following link:;en-us;q307545
that if you have an OEM operating system and you do this repair install, your administrator password will not work when you try to get back into the Recovery Console to complete the process.

So my first question is will I lose My Documents and files if I do the repair install? And my second question is will my computer create another admin password? And if it does is there anything I can do to prevent this?

John Graffeo wrote in his post: quote
"I saw that some people had made an error of copying the system.bak file over to the system file in C:\windows\system32\config, and as a result when they went to run the recovery console with the windows recovery disc, it would ask for the administrator password, which would not work. Without the administrator password, you could not follow the instructions above."

He then goes on to explain how to fix this if you have made this mistake but he doesn't say what file is the correct file to copy to C:\windows\system32\config. I am hoping that John or someone might be able to tell me the name of the correct file as I would like to avoid making this mistake in the first place.

I would appreciate any help I can get. I sent an email to with these questions over a month ago still have not received a reply. Thanks.

Richie Rich Mar 09, 2009, 11:41am EDT Report Abuse
>> Re: lsass.exe-system error
I encountered the lsass.exe application error on my laptop. I called Dell and paid $49.00 and all they wanted to do was reformat and reinstall or they took me thru several commands in the recovery console including a chkdsk whish was unsuccessful. I kept asking them about a REPAIR INSTALL but it was like I was talking to the wall.

So, I finally booted from my XP disk and did a REPAIR INSTALL. I didn't lose any files or programs. It seems all it did was replace all the files associated with the operating system ONLY and left everything else alone. Once it had completed installing, it began doing all the necessary auto updates until Windows was up to date. Just note that when you do a Repair Install, it looks just like a new install but it doesn't remove your files. I kept my fingers crossed during the entire process and was pleasantly surprised when Windows quickly booted and my desktop and files reappeared with no changes.

After the Repair Install, I ran the SASSER removal tool from Norton's site but it didn't find anything nor did SPYBOT or AVG. So I'm not sure what may have caused the problem. If anyone has suggestions about what else I can do to prevent a re-occurrence, please let me know.

Before anyone does a total reformat, I suggest trying a REPAIR INSTALL first. You have nothing to lose and you may save all your files and programs. You can find plenty of step by step instructions in this forum or the Net on how to boot from your disk and do a Repair Install. Now that I've done it once, it really is pretty easy.

Good luck everyone on this cuz the lsass.exe problem can raise your blood pressure when you see it.

I want my $49.00 back from Dell....sheesh, what a waste of money that was!

adam daly May 20, 2009, 09:46pm EDT Report Abuse
>> Re: lsass.exe-system error
i have windows xp on my laptop was recently installing service pack 3 when i restarted my computer i got the Isass.exe error '' 0xc0000006 '' cannot boot in safe mode or nothing and i do not have a xp boot cd any help would be greatly appreciated

Alan Oliveros Aug 16, 2010, 06:16am EDT Report Abuse
>> Re: lsass.exe-system error
i'm getting the lsass.exe failed to initialize properly (0xc0000142) click OK to terminate. what i've noticed is:
1) mouse is non-responsive.
2) nothing happens after i press enter (since mouse is non-responsive). i just get this big black screen.

i've confirmed that my PC is clean and does not have the Sasser worm/virus/trojan as I've ran Symantec's W.32 Sasser Removal Tool, the Stinger, my own Malwarebytes Anti-Malware and Avira Anti-Virus (which are both updated) and even Microsoft Malicious Software Removal Tool. no trace of Sasser.
lsass.exe is located in C:\Windows\system32 and it is spelled with a lower case l - which i do believe makes my lsass.exe legit.

i have a Windows XP Home Ed install CD and i've tried doing a Repair Install and still to no avail.

i have also replaced the lsass.exe in C:\Windows\system32 by copying the lsass.ex_ from the WinXP Home Ed install CD while i'm in Ubuntu (yes I have dual OS).

i have even used RegCure (thinking it might help) and i still get the problem above.

as with Ubuntu, i get a GRUB boot loader (makes you choose between Ubuntu, Memtest and Windows XP).
one thing i've noticed, if i boot my PC with the WinXP CD on the drive i get to the GRUB and a successful boot, without the CD, i get no GRUB, a grey "loading" bar at the bottom and then the lsass problem.

actually i am now tempted to delete the whole Windows folder while i'm in Ubuntu so i could do a "clean" install. is that a wise solution?

before i encountered the lsass.exe the PC I am using had WinXP Service Pack 3 and a bunch of Stardocks product installed and running (WindowBlinds, Bootskin, Logon). it had a custom bootscreen and log on screen. it also had StyleXP. i returned all those that have been changed by the said programs to Windows default and uninstalled all of them. that's when the problem started. so now i'm back to running WinXP Service Pack 2.

i tried booting to Safe Mode and Last Known Good Config (without the WinXP CD) but i just get a black screen with the Safe Mode on all corners. i think i might even have encountered the BSOD once so i did not use the Safe Mode and Last Known Good Config anymore.

Alan Oliveros Aug 18, 2010, 01:51pm EDT Report Abuse
>> Re: lsass.exe-system error
this lsass.exe has really tested my patience far too enough. after doing almost everything that was suggested by everyone here, i just gave up and gave in to the whole reformat thing. i just re-formatted my drive several hours ago and re-installed my copy of windows xp (i chose the other format option, not the quick one). that automatically should mean i am starting from a clean slate. but lo and behold, immediately after installing windows xp and restarting the PC without the windows xp installer on my rom drive, mr. lsass.exe rears its ugly head again with the same problem i had before.

i'm beginning to have a love/hate (mostly hate) relationship with lsass.exe to the point that this topic and the other lsass.exe topic have become my favorite here LOL

i've never had this problem before, only after uninstalling StyleXP and several Stardock products here that i've encountered this problem, which is why i just reformatted my drive C. could this already be a hardware related issue?

just a quick stab at my very "lovely" setup:

150GB Hitachi Hard Drive split into two:
-C: Windblows XP (primary)
-E: Ubuntu

150GB Western Digital:
-D: Data (slave)
this one was my former primary drive and it still has an old install of Windows XP. i don't think this one is giving me the lsass.exe problem as this was already my setup even before the incident with lsass.exe

Continue Reading on Page: 1, 2, 3, 4, 5, 6



  Topic Tools 
RSS UpdatesRSS Updates

  Related Articles 

A weekly newsletter featuring an editorial and a roundup of the latest articles, news and other interesting topics.

Please enter your email address below and click Subscribe.