Windows login bug - use S&D backups?

Fixit must be unloaded as well even if you don't have changed anything there. The reason is simple, loading a hive means adding the hive to the current registry. If you don't unload the hives which we have added they will just be still there. This is not what we wanted because this is your second system registry and it is not necessary to change anything there.

The reason why we have to load the hive in the first case is because we wanted to edit it. I know, it is really a little bit confusing.:spider:
 
@lobuej

You know, I have inserted a warning at the beginning. I will only works on systems similar to functio's one. Please open a new threat and describe your system and what tools and hardware you have available. I will take a look there later.
 
Okay, I unloaded both and am now going to swap the drives and see if this all works! Even if it doesn't, thanks chi-va! I will return!
 
@all, especially lobuej

Please never enter your private email address in a public post if you don't want to get unwanted spam.:grandpa:

I will request the admin(Tashi) to delete your email address. If you want that someone send you an email please exchange it via PM.
 
@lobuej

I hope you will read this because I'm not really here. Quite busy right now. Sorry, but I won't send you an email.

Warning only for Windows XP systems with BootCD with Windows PE support

Please take a look here:
http://windowsxp.mvps.org/peboot.htm

7. In order to fix the Userinit value in the loaded hive, navigate to the following location:

HKEY_USERS \ MyXPHive \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon
Click to expand...

Please be careful. If you want to repair all the profiles it should be this key:

HKEY_LOCAL_MACHINE\MyXPHive\microsoft\windows nt\currentversion\winlogon

It is better to post your problem in the forum in order to get assistance.
 
Your recommendation worked with a slight change

Chi-va and functio,

My apologies for posting my email address. IF that can be removed from this forum, I would certainly appreciate it. Thank you but I was desperate for some answers and/or replies.

Your recommendation worked for me with a slight change for Windows XP Pro users.

I revised the path in your step #8
The directory structure is not winnt. It is windows

C:\windows\system32\userinit.exe,:)
 
No, I can't. I'm not an administrator nor a moderator on this forum. Sorry! But I have already send a PM to an admin.
 
Hooray! My old drive is now accessible via Windows login, so everything is back to normal :D

Thanks very much indeed for your help chi-va! :present:
 
I have to bump this thread again as the bug has reappeared on a friend's PC. I now have an XP machine and tried to fix his problem by slaving his Win2K hard drive to my machine. Unfortunately it didn't work. Should I instead try to fix his drive using a PC with Win2k? I still have my old Win2k PC and could slave his drive to it.
 
functio:

I would like to suggest that you consider starting a new thread with your current problem since this thread is over six months old since it is hard to follow exactly what is meant by "... the bug has reappeared on a friend's PC ..." without trying to re-analyze the thirty one (31) posts that proceed your current post.

Please note: If your post is not directly related to Spybot, the new thread should probably be started in the Tavern forum.
 
You must log in or register to reply here.
Back
Top