inituser32

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

OS: WinXP.

In the hunt for viruses I have accidently changed my Windows NT registry
entry on HKLM for inituser32.exe. Pfew! In practical terms that means my
computer logs out before windows has completed it's logon process. Now, all I
need to do is to change the windows registry key back to the normal value.
However, when I cannot log on I'm kinda left in the blue! Btw, it's a laptop,
doesn't make it any easier...

Got any quick fix for this?

Thanx :)
 
Access the registry from another computer and change the value.
Of course if your standalone and have no other PC's that will be impossible.

Regards
Mark Dormer
 
Thank you for your reply, Mark.

However, I only get as far as the login window. When I enter the password
and click OK to log on, WinXP almost completes the logon sequence and then
closes the connections and we're back to the logon window again. So I'm not
able to connect from any of my other computers.

Impossible?

I have an NTFS formatted computer with a winreg fault, renamed inituser32
adding 3 x'es to the path. There is a solution somewhere. I just need to find
it. Even if I have to rip out the HD and rewrite the tracks with my
teeth...lol

I'm at war here, and I'm gonna win! Cheeky little laptop won't stand a
chance :)

Cheers!
 
Firstly, inituser32.exe is not a windows file.
It is either some other programs valid file or a virus/trojan/malware

OK, you don't need to be logged on to be able to access the computer from
another one.
Firewall settings may be an issue though

If you can get the drive into another PC you should be able to get rid of
the file.
THough I suspect that is not going to fix the issue

Try a repair installation
http://www.michaelstevenstech.com/XPrepairinstall.htm

Regards
Mark Dormer
 
Hi Mark

My solution to this problem was to install another WinXP, make a copy of the
userinit.exe to userinitxxx.exe, reboot on the original version (which now
worked), redo the changes in winreg and that's it. I'm now back up'n'running.

And yes, inituser32 would've been a virus, it was just me and my genetic RAM
failures making inituser32 out of userinit! Sorry about that.

Cheers,
Svein
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top