Unable to Login - Windows Xp Home Edition

Nice find, GTS. I'd actually gone in on another machine and deleted the =
contents of the UserInit value to test, and got the same behavior as the =
"wsaupdater" file not being present. Too bad there's no "simple" fix

--=20
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"GTS" x wrote in message ...
See Lavasoft Knowledge Base Article 04060901 - Unable to Log On To =
Windows
XP After Removing wsaupdater.exe
http://www.lavahelp.com/articles/v6/04/06/0901.html
--=20
=20
"Bill" wrote in message
...
Was running Lavasoft Ad_ware 6.181 when it complete and
indicated that their were "spyware" in memory & need to
restart & run remove process at next restart.

Click "ok" and attempted to restart PC. When XP came
back up and tried to log back in as the admin to the
machine with the same previous account, it just logs me
off.

Tried boot system into safe mode, too, but does the same
thing (attempt to login in, but just logout again).

Short of reimaging again, is there another way back into
the system????


=20

Nice find, GTS. I'd actually gone in on another machine and deleted the =
contents of the UserInit value to test, and got the same behavior as the =
"wsaupdater" file not being present. Too bad there's no "simple" fix

--=20
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"GTS" x wrote in message ...
See Lavasoft Knowledge Base Article 04060901 - Unable to Log On To =
Windows
XP After Removing wsaupdater.exe
http://www.lavahelp.com/articles/v6/04/06/0901.html
--=20
=20
"Bill" wrote in message
...
Was running Lavasoft Ad_ware 6.181 when it complete and
indicated that their were "spyware" in memory & need to
restart & run remove process at next restart.

Click "ok" and attempted to restart PC. When XP came
back up and tried to log back in as the admin to the
machine with the same previous account, it just logs me
off.

Tried boot system into safe mode, too, but does the same
thing (attempt to login in, but just logout again).

Short of reimaging again, is there another way back into
the system????


=20

G'Day Bill,

Boot to Safe Mode (because it's Home Ed) and
try to log in as "Administrator", leave the password
blank.
--
Regards,
Pat Garard
Australia

______________________________________

This may not be your issue, but I can duplicate the behavior that you're =
experiencing by removing the registry value indicated in the folloowing:

Is the machine on a network? If so, you can try the following. Boot =
the affected computer and let it get to the Welcome Screen. Then go to =
the other computer on the network, log on and click Start, Run and enter =
REGEDIT File, Connect Network Registry. Enter the machine name of =
the affected computer and click OK. You may be prompted for a username =
and password. If so, this must be a user account on the affected =
machine, with Administrator privileges.

You'll see a new branch in the Registry that corresponds to the affected =
computer. Expand this branch and go to:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

In the right pane, look for a value called UserInit. If present, this =
value should read:

C:\Windows\System32\userinit.exe,

The comma on the end is intentional and it must be there. If the value =
is different, double click the UserInit value and change it. If XP is =
not installed on C: on the affected machine, then change the path =
accordingly.

If the machine is not on a network, the steps in the following KB =
article will help you. The steps must be followed exactly.

http://support.microsoft.com/?id=3D307545
How to recover from a corrupted registry that prevents Windows XP from =
starting

And yes, I realize your system will boot, but you can't get past the =
logon. This will allow you to restore your system back to a point =
before you ran AdAware/SpyBot.


--=20
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"Bill" wrote in message =
...
Was running Lavasoft Ad_ware 6.181 when it complete and=20
indicated that their were "spyware" in memory & need to=20
restart & run remove process at next restart.
=20
Click "ok" and attempted to restart PC. When XP came=20
back up and tried to log back in as the admin to the=20
machine with the same previous account, it just logs me=20
off. =20
=20
Tried boot system into safe mode, too, but does the same=20
thing (attempt to login in, but just logout again).
=20
Short of reimaging again, is there another way back into=20
the system????
=20

I'm having the same problem Bill. If you manage to work
out what to do, please let me know at
and I'll do the same.

Cheers!

-----Original Message-----
tried that too and it didn't work...

Clicked on the Admin accout to Login
Get msg Loading Settings
Then get msg Saving Settings
Finally logout and back to the "Login" screen to choose
acct to login into...



-----Original Message-----
G'Day Bill,

Boot to Safe Mode (because it's Home Ed) and
try to log in as "Administrator", leave the password
blank.
--
Regards,
Pat Garard
Australia

______________________________________


.

.

Hi Doug,

I had the same problem at a customer computer and I found the following
simple solution (on this machine it helped perfectly):

http://tinyurl.com/6wxcu

Use answer 2.

Success,

Okko van der Beek

Doug Knox MS-MVP wrote:
*According to the very end of the article, they specify a DEFS
version =
that won't cause this problem. I would assume future DEFs won't
either, =
and that the issue will be addressed in a later release.

--=20
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"GTS" x wrote in message
...
Thanks Doug. I always appreciate your great work here. This
issue =
drove
me nuts the first time I ran into it on a client's laptop.
Hopefully
Lavasoft will address it in their next release.
--=20
=20
"Doug Knox MS-MVP" wrote in message
...
Nice find, GTS. I'd actually gone in on another machine and
deleted =
the
contents of the UserInit value to test, and got the same behavior
as =
the
"wsaupdater" file not being present. Too bad there's no "simple"
fix =

=20
--=20
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart
Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"GTS" x wrote in message =
...
Windows
=20
*



--
ovdbeek
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message872749.html