Userinit Registry entry messed Up

kif

kif

Novice
Hi,

I messed up Regedit entry "userinit" value, As some wscript was running. I made Userinit entry blank,Now am Unable to login my account:@. i tried to repair it showing me blue screen as Virus problem :no: . please help :huh:.

--- Updated Post - Automerged ---
kif said:
Hi,

I messed up Regedit entry "userinit" value, As some wscript was running. I made Userinit entry blank,Now am Unable to login my account:@. i tried to repair it showing me blue screen as Virus problem :no: . please help :huh:.
Click to expand...
Bump...

Additional info....

Os: Windows XP

Hp compaq presario Laptop.. i dont have Recovery CD. Guys please suggest
 
If you have made changes to the userinit key, then it will give you loopback while logging in to the system.

The value of the following key should be “C:\Windows\System32\userinit.exe,” without the quotes but with the comma after the exe part:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Steps for rectifying this problem:
Log on to a networked computer.
Run Regedit.exe
Point your cursor to HKEY_LOCAL_MACHINE
Select File > Connect Remote Registry
Type computer name (infected computer)
Navigate to the following location in registry of destination or infected computer
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Edit these two values in right pane:

Shell
Userinit
Shell=explorer.exe
Userinit = C:\windows\system32\userinit.exe,
Exit from Registry
Restart Infected computer.
You should be able to log on to computer.

OR

Login to XP recovery console (after booting off XP CD)

From the c:\windows> prompt, type:

Expand d:\i386\userinit.ex_ system32

Change d: to the drive letter of your CD-ROM.

Note that you must be in the c:\windows directory to type this command (this is the default directory in the Recovery Console)

The second parameter on the expand commandline tells it to write the expanded file into the system32 directory. (type expand /? for more info on the expand utility)

You can alos try repairing your OS
 
Back
Top