Ladron De La Noche on 5/11/2008 at 01:18
No, it's "lsass.exe". Sorry for the typo, at least I got the thread title right.
I just borked it, I think. I can't even get in now. I fucked up. :mad:
Still a chance though, not giving up. Overwriting the "lsass.exe" to Lsass.exe or LSASS.exe or LSASS.EXE didn't work. Still kept rebooting.
I have a live cd working atm, it's up and running. Will try to get in that way and move some files around.
Update: Mounted NTFS drive. I'm in. Now to fix my mistake.
TBE on 5/11/2008 at 06:17
Don't bother paying for an anti-virus once you get this fixed. (
http://free.avg.com/) Free AVG anti-virus is rated high and it's free. It works well, and isn't a system hog like Norton or Symantec. Make sure you click the download for the one that says it's free. They try to talk you into the one you can buy, which is ok, but for 99% of the people, the free one is a better option.
bikerdude on 5/11/2008 at 08:40
Quote Posted by Taffer_Boy_Elvis
Don't bother paying for an anti-virus once you get this fixed. (
http://free.avg.com/) Free AVG anti-virus is rated high and it's free. It works well, and isn't a system hog like Norton or Symantec. Make sure you click the download for the one that says it's free. They try to talk you into the one you can buy, which is ok, but for 99% of the people, the free one is a better option.
The trouble is, I have frequently found that stuff still gets past AVG as its only free. Kaspersky is the only one that catches the most beats all the other software...
TheOutrider on 5/11/2008 at 18:25
Quote Posted by Ladron De La Noche
No, it's "lsass.exe". Sorry for the typo, at least I got the thread title right.
You didn't, I fixed it ;) hence also the earlier inconsistency - funny enough, I read your post as "lsass" but spotted the typo in the title.
Quote:
I just borked it, I think. I can't even get in now. I fucked up. :mad:
Still a chance though, not giving up. Overwriting the "lsass.exe" to Lsass.exe or LSASS.exe or LSASS.EXE didn't work. Still kept rebooting.
As I said, if you're relatively sure it's not a virus or trojan, your easiest bet is probably XP's internal repair install feature. If the computer has a proper XP CD, that'll leave everything but the XP system files as untouched as possible and will not format the partition. Unless the user profile is horrendously messed up, this should get the system into top shape - if unpatched - again.
If the computer comes with a "recovery CD" however, you should probably stay away from that - those commonly indeed flatten everything and just dump on an image of the stock installation.
You could also just take out the hard drive, connect it to a working PC and run a virus scan on it from there, then back stuff up to the working machine as needed. It's usually the way I go.
Lansing on 5/11/2008 at 23:22
Well that at least explains the lsass / lssas differences. As said before it's almost certainly that lsass was never the real problem - it's just unlucky that it's the last thing logged before things go wrong.
Ultimately your best option is to do something similar to what Outrider suggested - take a complete sector copy of the harddrive using a second machine so you can always go back to the current state if necessary.
Ladron De La Noche on 7/11/2008 at 02:11
(
http://support.microsoft.com/kb/307545) http://support.microsoft.com/kb/307545
FIXED! MS details how. Also, another live cd. This time (
http://www.ubcd4win.com/index.htm) UBCD for Windows. Full NTFS support to read/write.
This was a pain to fix, a few live cds and correction of mistakes. Thanks for the input. :D
Sorry for all my typos. Thanks for the corrections, TheOutrider. ;)
