James,
The thread is not about the troll actually it seems to diverted as so
I gave the thread what I did to resolve the situation. Depending on the
state of the OS depends what you do. The OS I was doing had a rootkit too &
if you know anything you would understand you cannot trust a machine with a
rootkit. Besides this, the person is paying me to sort out his computer &
this is what I am doing. All his data is backed up now so the best thing I
can do is rebuild it properly so he doesn't get any more trouble or I'd get
it back saying it wasn't repaired properly
FYI: just copying back the userinit.exe is not the final solution. I spent
around 12 hours just to get the machine logging in correctly & I used a
Windows PE disc running from the command prompt to do everything because
when I detached the hard drive, placed it in a SATA caddy to connect to one
of my machines it wouldn't initialise due to the MBR being changed by the
infection. If this would have worked then it would have made life easier.
Also, I found that the NTFS.SYS file was also corrupt causing issues too
Besides the above it seems that more & more machines in the past week are
getting the same infection
So, James. I see that you can repair these corruptions easily without being
able to get into safe mode, system restore, normal login or being able to do
a rdp session. Clever you but I see you haven't provided an absolute
solution. Instead just made pointless comments. Whereas, I have solved this
issue with things I've done
SPAMCOP User
----- Original Message -----
From: "James Watkins" <
[email protected]>
Newsgroups: microsoft.public.windowsxp.general
Sent: Sunday, March 29, 2009 12:07 PM
Subject: Re: Login problem
You appear to miss the main problem in this thread: there is a troll
impersonating several different MVPs and dishing out bad advice under
their
names. I'm not even sure which side you're on: What you say about
userinit.exe causing the problem is correct but your subsequent advice is
equivalent to fixing a scratch in the door of your car with a sledge
hammer.
There is no need at all for the OP to "flatten" his Windows installation.
The userinit-issue can be resolved in far more elegant ways, without
destroying the current installation.