To solve your problem better, please provide full error message displayed on screen. When does this error occur (during or after Windows runs startup)?

0

Hi maad.. As an FYI, the MS Sasser worm removal tool is no longer available. It has been replaced by the Microsoft Windows Malicious Software Removal Tool. i_XpUser

0

Thank you XpUser:-) New name and new address ;-) for MS Sasser Removal tool! M

0

I am encountering a similar problem on a used laptop supposedly wiped and reinstalled with Windows XP Home edition. To make a long story short, lsass.exe says, "When trying to authenticate a password, this return indicates that the value provided by the current password is not correct." The computer then reboots. This happens even in safe mode. How I got to this point, which may be useful for diagnosis-- 1. Laptop was working fine for a few days. 2. Yesterday the laptop gave me a warning that certain registry files had been changed and advised me to fix them. 3. Shortly after that the laptop crashed for no apparent reason. 4. On rebooting it complained that powrprof.dll could not be found. It booted into safe mode. 5. Today, without my doing anything, it seems to have run correctly. 6. Then I got another warning about the registry files, and it crashed. 7. Given the option to reboot to safe mode, I told it to reboot to the "last good settings." 8. At this point I get lsass.exe error messages which prevent the computer from finishing the boot process, and cannot boot into safe mode. ======= This leads me to ask a few questions-- 1. Is there a way to make this lsass.exe thing go away, so that I can get into safe mode at least? 2. How do I update/fix my registry keys? I apologize for the ignorance shown in this post but at least I'm honest about my limitations. If anyone could advise me I would be very grateful.

0

As mentioned in the earlier parts of this thread, the above error message you seem to be having might have been either from a "Sasser Worm" induced registry changes or a Registry corruption from an unknown cause. In the early stages of of the symptoms of this problem, you could have treated the registry corruption from Safe Mode by the use of System File Checker using SFC /Scannow command Once you cannot even access Safe Mode as is the case you find yourself at the mmoment, your only troubleshoot options are: 1. Repair Installation aka In-place upgrade 2. Parallel Installation & Regedit from there-> New WinXP Pro Installation on a different partition & Regedit. 3. Reformat and Reinstall of Windows M

0