Hi folks. Hope someone can help. Yesterday I restarted my pc after downloading the latest windows update. Instead of doing what I would normally do and installing it while logged in I let the computer wait to install the updates and then turn itself off. Now when I start the pc and click on my name to log in windows starts to log in and I see the picture from the desktop background and then it immediately logs out again without even getting to the taskbar. The same thing happens when I boot into safe mode. At the same time that I was installing the windows update (there were 4 files contained in the update and they were just what MS call essential updates) I had uninstalled a couple of games without restart and had updated nokia pc suite also without restart.

Obviously as I can't log in I can't post any scans but this link has the most recent HJT logs that I have http://www.daniweb.com/forums/thread168044.html

I think the only way to get access to find out what's happening is to be able to get into have a look using DOS commands but I have no knowledge of this. I think I should be able to get a DOS prompt from booting into safe mode. I will be at work for the next 7 hours at least so if anyone can post something in that time that I can give a go when I get home I would be most grateful.

Dani AI

Generated

This symptom — the logon briefly shows the desktop background and then immediately returns to the logon screen (and the same happens in Safe Mode) — most commonly means the interactive logon chain never gets a chance to start Explorer. That can be caused by a damaged user profile, a replaced or redirected logon helper executable, or a piece of malware that altered the Winlogon startup sequence. It’s not usually a simple cosmetic driver issue; the OS is starting but the hand‑off that launches the shell is failing.

Non‑destructive first checks worth doing before editing files or the registry: try "Last Known Good Configuration" from the F8 boot menu; attempt Safe Mode with Command Prompt (if that still gets you in there, System Restore can be launched from the prompt); and boot from a rescue/Live CD or USB to copy off important data so nothing is lost during recovery attempts. If any repair option reports available restore points, use them before manual changes.

The approach described by (restore a clean logon helper binary and put the Winlogon entry back to the genuine system executable) is a known recovery tactic and is reasonable — but it carries risk. Back up the drive or at least the registry hives before making changes. Verify file timestamps in the system folder for unexpected executables, scan the offline disk with a rescue antivirus ISO, and confirm the shell entry points to the normal shell. As noted, the Recovery Console gives a minimal command set; use it only if comfortable and follow precise steps from a reputable source.

If those measures fail, the safer next steps are an in‑place repair/repair install or a full reinstall after data backup. Given the OP’s comment about a damaged power supply, also verify hardware stability before repeated repair attempts. The HJT logs already posted elsewhere on the forum can help identify persistent startup items or malware and are useful to consult before irreversible changes.

Recommended Answers

All 3 Replies

I've just had a look through MS Update pages and I think that 2 of the 4 updates I downloaded yesterday were the malicious software removal tool and the other one was a Cumulative Security Update for Active X killbits Windows XP. I remember seeing the second one as had never heard of it before. There were a whole lot of updates released for XP HE yesterday and the list is here:

if you get to a dos prompt >
then typing ? will give you the list of commands and then if you type the command (dir)with the word (help) such as
DIR HELP it will give you help. or type DOS HELP into google.
M

After destroying my power supply when trying to clean the pc above I finally fitted a new one but still have the same problem above. I have a boot disc for windows and will try the following fix to see if it works sometime over the weekend:

1. Boot using your winxp cd.
2. Enter recovery console.
3. at the command prompt go to
C:/windows/system32
4. next type:
copy userinit.exe wsaupdater.exe
5. exit and reboot normally. You should now be able to logon. But you're not done yet!
6. run regedit
7. find the Userinit key in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\
8. modify the entry:
C:\WINDOWS\System32\wsaupdater.exe
so that it reads:
C:\WINDOWS\System32\userinit.exe

Just wondering if anyone has any comments before I do something else to knacker my desktop? I found the fix at computing.net by Tom's guide. I have a laptop as well so can check here more often than before when I was checking at work and following printed out instructions....sigh....its either this fix or pay the man a lot of money to reformat hd I think....bigger sigh.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.