Now you're confusing me. Previously, in response to me suggestion to run
psexec.exe, you reported this:
Bad PC has C
Windows
My good desktop is same.
Your reply led me to believe that you had successfully established a psexec
session on PCbad, which in turn caused me to conclude that the drive letter
assignment on PCbad was correct. Your most recent post implies that you
never got a psexec session running. If this is so then I must ask for more
careful reporting. If you report things that do not exist then I am unable
to solve your problem.
A quick test with psexec.exe will show you that you can omit the -p prompt.
It is optional. How can you find out? By typing this at the command prompt:
psexec /?
See the word "optional" against theb -p parameter? Now let's go back a few
steps, run the psexec command I propose, then report accurately what you got
in response to the "set system" command.
"BP" <BP@discussions.microsoft.com> said this in news item
news:616DF35C-4C03-4B14-B927-12CDC563C542@microsoft.com...
> Sorry for confusion, I meant the Badpc does not have an Administrator
> password I just hit enter at password. So do I leave off the -p xxxx cmd
> or
> do I type the command line like this on the Goodpc cPSTools\psexec
> \\PCbad
> -u Administrator cmd?
>
> Also I have the PCbad on my home network booted to the user account sign
> on
> screen. Is this were it should be?
>
> "Pegasus [MVP]" wrote:
>
>> If the command
>>
>> cacls CWindows\system32\userinit.exe
>>
>> scrolls through the arguments list then you must have mistyped it. Best
>> to
>> check it on PCgood.
>>
>> Why do you want to set or change passwords at this stage? It would be
>> better
>> not to introduce new variables at this stage.
>>
>>
>> "BP" <BP@discussions.microsoft.com> said this in news item
>> news:8693DEF6-D772-4EEA-8872-43BD8432E900@microsoft.com...
>> > When I try this command it just scrolls with the aruments list. Does
>> > not
>> > appear to do anything. Also the bad pc does not have any password how
>> > do I
>> > change the command for that?
>> >
>> > "Pegasus [MVP]" wrote:
>> >
>> >> Excellent. This means that your system drive letter is still correct
>> >> (assuming that you originally installed Windows in cWindows).
>> >>
>> >> You now need to check on PCbad that the registry key
>> >> HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\UserInit
>> >> points
>> >> at CWindows\system32\userinit.exe and that the file
>> >> CWindows\system32\userinit.exe does indeed exist. You can open the
>> >> registry of PCbad from within regedit on PCgood.
>> >>
>> >> While you have an active psexec session, you might as well check the
>> >> access
>> >> rights for userinit.exe like so:
>> >> cacls CWindows\system32\userinit.exe.
>> >> The file must be readable by everyone.
>> >>
>> >>
>> >> "BP" <BP@discussions.microsoft.com> said this in news item
>> >> news:10836305-A1E5-4346-9B04-D7A5FD613AFA@microsoft.com...
>> >> > Bad PC has CWindows
>> >> > My good desktop is same.
>> >> >
>> >> > "Pegasus [MVP]" wrote:
>> >> >
>> >> >> OK, let's do it the easy way. Let's assume that PCbad is the
>> >> >> problem
>> >> >> PC.
>> >> >>
>> >> >> 1. Get a copy of psexec.exe from www.sysinternals.com.
>> >> >> 2. Turn on PCbad. Do not log on.
>> >> >> 3. Log on to PCgood.
>> >> >> 4. Open a Command Prompt.
>> >> >> 5. Type these commands:
>> >> >> psexec \\PCbad -u Administrator -p xxxx cmd
>> >> >> (Replace xxxx with the Administrator's password on PCbad)
>> >> >> set system
>> >> >>
>> >> >> What is the value of %SystemDrive%?
>> >> >>
>> >> >>
>> >> >> "BP" <BP@discussions.microsoft.com> said this in news item
>> >> >> news:853B0638-FA99-466B-AFE5-8749A6C9DC1B@microsoft.com...
>> >> >> > I can do either with good instructions, but I can easily put the
>> >> >> > hard
>> >> >> > drive
>> >> >> > in a usb enclosure?
>> >> >> >
>> >> >> > "Pegasus [MVP]" wrote:
>> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >> "BP" <BP@discussions.microsoft.com> said this in news item
>> >> >> >> news:2B2A0A45-3396-4025-BA94-99C3A24227F0@microsoft.com...
>> >> >> >> > I recently ran super spyware removal because I had the
>> >> >> >> > Internet
>> >> >> >> > Security
>> >> >> >> > 2010
>> >> >> >> > virus. It cleaned several files and had me reboot. The Compaq
>> >> >> >> > Presario
>> >> >> >> > V2000
>> >> >> >> > laptop now only boots to the User Accounts screen in either
>> >> >> >> > safe
>> >> >> >> > mode
>> >> >> >> > or
>> >> >> >> > normal and lets me click on either of the 2 accounts I have
>> >> >> >> > Admin
>> >> >> >> > and
>> >> >> >> > myname.
>> >> >> >> > As it starts logging in it then says Log off saving desktop
>> >> >> >> > then
>> >> >> >> > returns
>> >> >> >> > to
>> >> >> >> > the accout sign on window. I have searched the internet and
>> >> >> >> > tried
>> >> >> >> > the
>> >> >> >> > recovery console and replaced the userinit.exe but it did not
>> >> >> >> > work.
>> >> >> >> > I
>> >> >> >> > see
>> >> >> >> > lots of listings for this issue but few fixes that do not
>> >> >> >> > work.
>> >> >> >> > Any
>> >> >> >> > other
>> >> >> >> > fixes I can try?
>> >> >> >>
>> >> >> >> As you already found out, the problem is caused by userinit.exe,
>> >> >> >> either
>> >> >> >> a) because the file is not where it should be; or
>> >> >> >> b) because its registry reference points at the wrong place; or
>> >> >> >> c) because you have an incorrect system drive letter.
>> >> >> >>
>> >> >> >> The cure is easy if you can reach the problem machine with a
>> >> >> >> networked
>> >> >> >> machine under the Administrator's account, harder if you can
>> >> >> >> remove
>> >> >> >> its
>> >> >> >> disk
>> >> >> >> and connect it as a slave or USB disk to some other WinXP PC and
>> >> >> >> harder
>> >> >> >> again if neither of these applies. What applies in your case?
>> >> >> >>
>> >> >> >> .
>> >> >> >>
>> >> >> .
>> >> >>
>> >> .
>> >>
>> .
>>