G
Guest
I cannot log on. After selecting user, the system start to log on but immediately begins logging off. I tried rebooting in safe mode, but the same thing happened. How do I correct?
R
roger
Hi,
"Blazefind changes the following registry-key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Winlogon
"Userinit" = "C:\WINNT\system32\userinit.exe,"
in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Winlogon
"Userinit" = "C:\WINNT\system32\wsaupdater.exe,"
Used Lavasoft Adaware to get rid of the pest ----> removed blazefind
and
with it the wsaupdater.exe
==> next time i tried to logon my computer the system tries to run
wsaupdater.exe which it couldn't find ! FAILED LOGON -> LOGOFF
I first tried to find ways to change the registry from within the
recovery console but i did not succeed (ERD commander will probably
work, but since i wasn't sure that this was the problem i thought it a
little bit too expensive)...
Then i thought of this:
just copy userinit.exe as wsaupdater.exe !! It's as simple as that....
YES!! it works again... and blazefind is gone (it seems....
)"
Using the recovery console employ the command
copy C:\Windows\System32\userinit.exe
C:\Windows\System32\wsaupdater.exe
(this is one line separated by a space, supposing the partition where
windows is installed is C, and supposing blazefind caused this)
Good luck
"Blazefind changes the following registry-key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Winlogon
"Userinit" = "C:\WINNT\system32\userinit.exe,"
in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Winlogon
"Userinit" = "C:\WINNT\system32\wsaupdater.exe,"
Used Lavasoft Adaware to get rid of the pest ----> removed blazefind
and
with it the wsaupdater.exe
==> next time i tried to logon my computer the system tries to run
wsaupdater.exe which it couldn't find ! FAILED LOGON -> LOGOFF
I first tried to find ways to change the registry from within the
recovery console but i did not succeed (ERD commander will probably
work, but since i wasn't sure that this was the problem i thought it a
little bit too expensive)...
Then i thought of this:
just copy userinit.exe as wsaupdater.exe !! It's as simple as that....
YES!! it works again... and blazefind is gone (it seems....
)"Using the recovery console employ the command
copy C:\Windows\System32\userinit.exe
C:\Windows\System32\wsaupdater.exe
(this is one line separated by a space, supposing the partition where
windows is installed is C, and supposing blazefind caused this)
Good luck