Unable to reach desktop

[Chuck]

I am running XP Home on a gateway 500 x. Whe I start up i get th
welcome screen with my name. When I select my name it indicate
loading personal setting, then quickly goes to logoff, and returns t
my welcome screen. The same thing happens when I start in safe mode.
Any advice

 

[Rick \Nutcase\ Rogers]

Hi Chuck,

Run any spyware removal programs lately? The userinit value may have been
corrupted by the removal of blazefind. It adds wsaupdater.exe to the logon
value in the system registry, sometimes appending it, sometimes replacing
it. Running Adaware or other cleaners detects and removes wsaupdater.exe,
but doesn't correct the registry damage. If this is the case, then you may
need to load the registry hive from another installation and change it. This
is the key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Userinit string value should be:

C:\WINDOWS\system32\userinit.exe,

On the damaged installations it's one of these:

C:\WINDOWS\system32\wsaupdater.exe,
C:\WINDOWS\system32\userinit.exe,C:\WINDOWS\system32\wsaupdater.exe,

Another "quickie" method of resolution is to load the Recovery Console (see
below), copy userinit.exe as wsaupdater.exe from the command prompt, then
restart normally. Once in, go and change the registry value back to what
it's supposed to be and delete the copied file.

HOW TO: Install and Use the Recovery Console in Windows XP [Q307654]
http://support.microsoft.com/?kbid=307654

This can also be done by using the 6 disk boot floppy set mentioned in the
above article, as it loads enough of the Recovery Console so that you can
copy the file. This is particularly useful if you have an OEM installation
that includes only a Restore CD, or no disk at all.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Rick \Nutcase\ Rogers]

Hi Karen,

There is no easier solution that I am aware of. The problem is that the
registry value mentioned is looking for the wsaupdater.exe file to validate
the logon. As the file is not there, it cannot validate and rejects the
logon. You can't edit the registry and correct it without logging on, or by
remotely loading the registry hive (something for advanced users).

The second part of that post provides the most viable solution for home
users. The alternative is a repair install or full reinstall - not the best
options for a number of reasons. By copying the file you should be using
(userinit.exe) as the file that the system is looking for (wsaupdater.exe),
you are essentially "fooling" the system so that it will load the user
profile. Once loaded, you can manually correct the registry and delete the
copied file.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

I'm having the EXACT same problem Chuch wrote about. However, I'm a
computer
novice and while Rick's reply may be accurate, I'm wondering if there is
an
easier fix for this problem? It is very frustrating becasue I can't even
get
to my desktop.

Thanks for any help anyone can provide to this computer novice!

-Karen

Hi Chuck,

Run any spyware removal programs lately? The userinit value may have been
corrupted by the removal of blazefind. It adds wsaupdater.exe to the
logon
value in the system registry, sometimes appending it, sometimes replacing
it. Running Adaware or other cleaners detects and removes wsaupdater.exe,
but doesn't correct the registry damage. If this is the case, then you
may
need to load the registry hive from another installation and change it.
This
is the key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Userinit string value should be:

C:\WINDOWS\system32\userinit.exe,

On the damaged installations it's one of these:

C:\WINDOWS\system32\wsaupdater.exe,
C:\WINDOWS\system32\userinit.exe,C:\WINDOWS\system32\wsaupdater.exe,

Another "quickie" method of resolution is to load the Recovery Console
(see
below), copy userinit.exe as wsaupdater.exe from the command prompt, then
restart normally. Once in, go and change the registry value back to what
it's supposed to be and delete the copied file.

HOW TO: Install and Use the Recovery Console in Windows XP [Q307654]
http://support.microsoft.com/?kbid=307654

This can also be done by using the 6 disk boot floppy set mentioned in
the
above article, as it loads enough of the Recovery Console so that you can
copy the file. This is particularly useful if you have an OEM
installation
that includes only a Restore CD, or no disk at all.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

I am running XP Home on a gateway 500 x. Whe I start up i get the
welcome screen with my name. When I select my name it indicates
loading personal setting, then quickly goes to logoff, and returns to
my welcome screen. The same thing happens when I start in safe mode.
Any advice?

 

[Guest]

Rick, I have the same problem identified in this thread.

Since I can't get past the welcome screen, how do I load the registry hive
from another installation and make the changes? I'm not sure how to get to
the hotkey string you discuss.

I'm a little over my head.

I appreciate your feedback.

T. Knight

Hi Karen,

There is no easier solution that I am aware of. The problem is that the
registry value mentioned is looking for the wsaupdater.exe file to validate
the logon. As the file is not there, it cannot validate and rejects the
logon. You can't edit the registry and correct it without logging on, or by
remotely loading the registry hive (something for advanced users).

The second part of that post provides the most viable solution for home
users. The alternative is a repair install or full reinstall - not the best
options for a number of reasons. By copying the file you should be using
(userinit.exe) as the file that the system is looking for (wsaupdater.exe),
you are essentially "fooling" the system so that it will load the user
profile. Once loaded, you can manually correct the registry and delete the
copied file.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

I'm having the EXACT same problem Chuch wrote about. However, I'm a
computer
novice and while Rick's reply may be accurate, I'm wondering if there is
an
easier fix for this problem? It is very frustrating becasue I can't even
get
to my desktop.

Thanks for any help anyone can provide to this computer novice!

-Karen

Hi Chuck,

Run any spyware removal programs lately? The userinit value may have been
corrupted by the removal of blazefind. It adds wsaupdater.exe to the
logon
value in the system registry, sometimes appending it, sometimes replacing
it. Running Adaware or other cleaners detects and removes wsaupdater.exe,
but doesn't correct the registry damage. If this is the case, then you
may
need to load the registry hive from another installation and change it.
This
is the key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Userinit string value should be:

C:\WINDOWS\system32\userinit.exe,

On the damaged installations it's one of these:

C:\WINDOWS\system32\wsaupdater.exe,
C:\WINDOWS\system32\userinit.exe,C:\WINDOWS\system32\wsaupdater.exe,

Another "quickie" method of resolution is to load the Recovery Console
(see
below), copy userinit.exe as wsaupdater.exe from the command prompt, then
restart normally. Once in, go and change the registry value back to what
it's supposed to be and delete the copied file.

HOW TO: Install and Use the Recovery Console in Windows XP [Q307654]
http://support.microsoft.com/?kbid=307654

This can also be done by using the 6 disk boot floppy set mentioned in
the
above article, as it loads enough of the Recovery Console so that you can
copy the file. This is particularly useful if you have an OEM
installation
that includes only a Restore CD, or no disk at all.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org


I am running XP Home on a gateway 500 x. Whe I start up i get the
welcome screen with my name. When I select my name it indicates
loading personal setting, then quickly goes to logoff, and returns to
my welcome screen. The same thing happens when I start in safe mode.
Any advice?

 

[Rick \Nutcase\ Rogers]

Hi,

This should help explain what you need to do:
http://rickrogers.org/fixes.htm#Blazefind

How to accomplish this in your situation is covered in the second half of
the article.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

Rick, I have the same problem identified in this thread.

Since I can't get past the welcome screen, how do I load the registry hive
from another installation and make the changes? I'm not sure how to get
to
the hotkey string you discuss.

I'm a little over my head.

I appreciate your feedback.

T. Knight

Hi Karen,

There is no easier solution that I am aware of. The problem is that the
registry value mentioned is looking for the wsaupdater.exe file to
validate
the logon. As the file is not there, it cannot validate and rejects the
logon. You can't edit the registry and correct it without logging on, or
by
remotely loading the registry hive (something for advanced users).

The second part of that post provides the most viable solution for home
users. The alternative is a repair install or full reinstall - not the
best
options for a number of reasons. By copying the file you should be using
(userinit.exe) as the file that the system is looking for
(wsaupdater.exe),
you are essentially "fooling" the system so that it will load the user
profile. Once loaded, you can manually correct the registry and delete
the
copied file.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

I'm having the EXACT same problem Chuch wrote about. However, I'm a
computer
novice and while Rick's reply may be accurate, I'm wondering if there
is
an
easier fix for this problem? It is very frustrating becasue I can't
even
get
to my desktop.

Thanks for any help anyone can provide to this computer novice!

-Karen

:

Hi Chuck,

Run any spyware removal programs lately? The userinit value may have
been
corrupted by the removal of blazefind. It adds wsaupdater.exe to the
logon
value in the system registry, sometimes appending it, sometimes
replacing
it. Running Adaware or other cleaners detects and removes
wsaupdater.exe,
but doesn't correct the registry damage. If this is the case, then you
may
need to load the registry hive from another installation and change
it.
This
is the key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon

Userinit string value should be:

C:\WINDOWS\system32\userinit.exe,

On the damaged installations it's one of these:

C:\WINDOWS\system32\wsaupdater.exe,
C:\WINDOWS\system32\userinit.exe,C:\WINDOWS\system32\wsaupdater.exe,

Another "quickie" method of resolution is to load the Recovery Console
(see
below), copy userinit.exe as wsaupdater.exe from the command prompt,
then
restart normally. Once in, go and change the registry value back to
what
it's supposed to be and delete the copied file.

HOW TO: Install and Use the Recovery Console in Windows XP [Q307654]
http://support.microsoft.com/?kbid=307654

This can also be done by using the 6 disk boot floppy set mentioned in
the
above article, as it loads enough of the Recovery Console so that you
can
copy the file. This is particularly useful if you have an OEM
installation
that includes only a Restore CD, or no disk at all.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org


I am running XP Home on a gateway 500 x. Whe I start up i get the
welcome screen with my name. When I select my name it indicates
loading personal setting, then quickly goes to logoff, and returns
to
my welcome screen. The same thing happens when I start in safe
mode.
Any advice?