So I quickly dropped what I was doing and went over to their place. When I got there I found this Windows XP PC that keeps getting redirected to the login screen after logging in. I asked if they have another working computer.
Like always, I searched the web to find if someone else have already encountered this problem. Sure enough I found that the problem was being caused by a virus. The author said it was being caused by a virus called BlazeFind. Here are the steps I did to solve the problem:
1. I went to the problem PC and then I booted it using Windows XP CD.
2. I went to the recovery console, what I needed to do was go to C:\Windows\system32\
3. to do a COPY USERINIT.EXE WSAUPDATER.EXE unfortunately when I looked the USERINIT.EXE was missing
4. so I went over to the other working Windows XP PC to copy its USERINIT.EXE file. But the problem is I could not copy it to the problem PC because Windows XP Recovery Console won't detect the USB drive.
5. So what I did was reboot the problem PC normally.
6. I then looked if a folder was accessible through the network. Luckily the owner of the problem pc did have a writable shared folder so I copied USERINIT.EXE to the shared folder.
7. I then booted the problem PC again and used the RECOVERY CONSOLE.
8. I copied USERINIT.EXE to C:\Windows\System32
9. I the proceeded again to step 3.
10. After I was finished. I rebooted and I was able to login normally.
11. The final adjustment I made was to go to run REGEDIT and go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ WindowsNT \ CurrentVersion \ Winlogon
12. I then typed C:\WINDOWS\system32\userinit.exe, as it's value.
Make sure that the comma is included. Make sure also to do a malware and virus scan after doing the above steps.
But what if you were not as lucky as I am and you could not see the problem PC in the network? What you could do here is remove the hard disk and make it a slave drive of a working Windows XP PC. Copy the files needed to fix the problem. Then you put back the hard disk in the original PC you took it from. And then fix the problem by following the needed steps I stated above.
Like always, I searched the web to find if someone else have already encountered this problem. Sure enough I found that the problem was being caused by a virus. The author said it was being caused by a virus called BlazeFind. Here are the steps I did to solve the problem:
1. I went to the problem PC and then I booted it using Windows XP CD.
2. I went to the recovery console, what I needed to do was go to C:\Windows\system32\
3. to do a COPY USERINIT.EXE WSAUPDATER.EXE unfortunately when I looked the USERINIT.EXE was missing
4. so I went over to the other working Windows XP PC to copy its USERINIT.EXE file. But the problem is I could not copy it to the problem PC because Windows XP Recovery Console won't detect the USB drive.
5. So what I did was reboot the problem PC normally.
6. I then looked if a folder was accessible through the network. Luckily the owner of the problem pc did have a writable shared folder so I copied USERINIT.EXE to the shared folder.
7. I then booted the problem PC again and used the RECOVERY CONSOLE.
8. I copied USERINIT.EXE to C:\Windows\System32
9. I the proceeded again to step 3.
10. After I was finished. I rebooted and I was able to login normally.
11. The final adjustment I made was to go to run REGEDIT and go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ WindowsNT \ CurrentVersion \ Winlogon
12. I then typed C:\WINDOWS\system32\userinit.exe, as it's value.
Make sure that the comma is included. Make sure also to do a malware and virus scan after doing the above steps.
But what if you were not as lucky as I am and you could not see the problem PC in the network? What you could do here is remove the hard disk and make it a slave drive of a working Windows XP PC. Copy the files needed to fix the problem. Then you put back the hard disk in the original PC you took it from. And then fix the problem by following the needed steps I stated above.
Comments
maybe the pc you copied from is also infected.
are you able to atleast in safe mode?