Problem 1: on windows startup i get the following message "Isass.exe - "invalid parameter passed to service or function" " it then reboots

Problem 2: when asked for adminstrator PASSWORD in recovery console, i press enter because i know the password is blank and its says "invalid password". However, earlier in the day i was able to access the recovery console as it didn’t’ prompt me for an administrator password


Initially the computer wouldn’t go past the opening DOS screen as it said the \windows\system32\config file was corrupted and only gave me the option to enter recovery console where I followed the following instructions.

This involved typing the following commands into the recovery console:
PART 1.
md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
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

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

PART 2.
Copy ‘snapshot’ registry files from \system volume information\ to \windows\tmp\

After completing Parts 1 and Part 2 of these instructions I tried to enter the recover console again to do Part 3 which is when it started asking for an Administrator password. So I tried to open up Windows (just to see if it would let me in this time) and i received the following message when windows starts up
"Isass.exe - "invalid parameter passed to service or function" "

I then went back into the recovery console to redo the instructions however when it asks for the administator password (which is just blank" a message comes up saying "the password is invalid"

I do have a Hiren disk that can run a mini XP os and tried to install SP3 to try to fix at least part of this problem but it won’t let me from this environment.. I have USED the Hiren disk to clear the Administrator password but this has achieved nothing

I have tried using windows xp recovery disc as well as a Windors XP os disc to repair but it hasnt worked. Every time i boot up windows starts installing and then the message comes up "invalid parameter passed to service or function" and it says windows SETUP cannot finish and it reboots

It seems that by going into the recovery console and changing registery files it caused the problem. Then the problem with Isass.exe seems to corrupt user logon validation hence the problem with the recovery console.
I managed to copy over the registry files to the \windows\system32\config\ folder from the \windows\tmp\ folder and the computer opened up into Windows when I restarted (YEAH). Do I have to still restore back to a previous point (this is Part 4 of the instructions)? I am worried that it will kill the computer again! Just running a VIRUS scan over the C drive again while I contemplate the next move as the scan run in the mini XP mode found 8 x dodgy registry files. 2 things:

What happens if you simply hit Enter at the passworf prompt ? ?

And...what protection apps are you scanning with ? ?
There are variants of lsass out there that mask as infections...If I push 'enter' it tells me that the password is invalid and gives me another 2 x tries before it restarts. In the end I got around this by copying over the registry files via the 'mini XP' os that is available through the Hiren CD. As lsass.exe can be a trojan I did run a virus scan over it a few times and it picked up quite a few problems (including a couple of trojans). Have sent it home to it's owner with the instructions to run the scan a few more times over the next few days until it stops picking up problems. Am using SuperAntiSpyware.