Rebuilding Lsasrv.dll file to Log-In to Win2K

[Jason Ducharme]

I recently connected my laptop to the internet after not using it for
about 3 weeks. I was not behind a firewall, and after only about 5
minutes I was infected with the Sasser virus. I didn't know anything
about this virus, and sadly, I tried to fix the problem myself (silly)
by renaming the Lsass.exe and Lsasrv.dll files.

After doing this I was no longer able to log on to my machine. I
renamed the files back to their original names, and still unable to
log on. I then copied the Lsasrv.dll file from my Win2K cd onto the
Windows directory, in hopes that a fresh copy of the file would solve
the problem. Sadly, I'm still unable to logon. Win2K boots normally,
but when it reaches the stage where I would logon with my username and
password, it doesn't display the log-on dialog, and just sits there
indefinitely.

I know now that the Lsasrv.dll is a system file that controls logons,
and that I should have researched this before tinkering. However, the
damage is done. Is there a way to repair this, so that I can access
my machine?

Thanks in advance,
Jason Ducharme

 

[Jason Ducharme]

I recently connected my laptop to the internet after not using it for
about 3 weeks. I was not behind a firewall, and after only about 5
minutes I was infected with the Sasser virus. I didn't know anything
about this virus, and sadly, I tried to fix the problem myself (silly)
by renaming the Lsass.exe and Lsasrv.dll files.

After doing this I was no longer able to log on to my machine. I
renamed the files back to their original names, and still unable to
log on. I then copied the Lsasrv.dll file from my Win2K cd onto the
Windows directory, in hopes that a fresh copy of the file would solve
the problem. Sadly, I'm still unable to logon. Win2K boots normally,
but when it reaches the stage where I would logon with my username and
password, it doesn't display the log-on dialog, and just sits there
indefinitely.

I know now that the Lsasrv.dll is a system file that controls logons,
and that I should have researched this before tinkering. However, the
damage is done. Is there a way to repair this, so that I can access
my machine?

Thanks in advance,
Jason Ducharme

This is a little bit embarassing....I did not copy the Lsass.exe file from
CD to the hard drive, just the Lsasrv.dll file. After copying a fresh
version of Lsass.exe, the computer booted properly, and allowed me to log
on. I have since run Stinger and applied the MS patch, and the computer
seems to working OK.

Thanks,
Jason