baraka607 said:
ColradoGuy said:
I am having trouble with my notebook. I recently decided to turn on the screensaver to "blank" after 10 minutes and set the power managemet to never turn off the display under either power condition. I would leave my computer for 10 minutes or so and then when I would come back, I was logged out. Yes, I mean logged out as in all open, running applications were closed, not just at the login screen. I searched the web and found many others with a similar problem. Most replies refer to the check box on the screensaver setup page that says "on resume, display logon screen." This is quite different though as even with that checked, the current user is not actually logged off and the running applications are not shutdown. I (and others with this problem) are actually being logged off. Incidentally, the box is not checked, and now the screensaver is diabled. Power management is set to never turn anything off, ever. I still have the problem. I then saw a post that said I needed to uncheck the "require password to logon" option in the user settings. Seemed odd since my computer worked as it should for the last 9 months with that option checked (by default), but I gave it a try. The system still logs me out. I then went back to the screensaver and re-enabled it with the "bubbles" but this time, I set the timeout to 9999 minutes, figuring that it would then take a week of idle time before it logged me out, if in fact that was the problem. Didn't work, still being logged out with applications running. I have searched all over the web, but can't find a solution. Any ideas would be greatly appreciated.

Thanks
Hey buddy,
That mostly happen if you are infected with virus or trojan which corrupts the registry key holding the value of the files which are executed while logging in to windows. The other possibility is, the registry key getting replaced with some incorrect value.

So here is the solution:
1. You need to connect the infected computer to a network. Make sure that there is one computer in the network which doesn’t suffer from this problem. Now, switch on both of the computers, i.e. the infected and the working computer.
2. From the working computer, Go to Start> Run, type regedit.exe and hit enter. This will launch the registry editor.
3. Go to File> Connect Network Registry, by using this infected computer’s name or IP address.
4. Locate the following entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
5. In this entry there is a key named userinit, double click on the key and set its value to “C:\WINDOWS\System32\userinit.exe,”
If the problem still persists then you need to run a repair setup. Check out for detailed instructions on running a repair setup over here.

Please let me know if this solve your problem and i will figure something else. Your welcome:)
Thanks baraka607. I followed what you suggested and it worked like a charm. Cheers and thanks again. I can now log into my guest account and standard user accounts..

See post #10 @ 10 Nov 2010 for baraka607 response

Hey buddy,
That mostly happen if you are infected with virus or trojan which corrupts the registry key holding the value of the files which are executed while logging in to windows. The other possibility is, the registry key getting replaced with some incorrect value.

So here is the solution:
1. You need to connect the infected computer to a network. Make sure that there is one computer in the network which doesn’t suffer from this problem. Now, switch on both of the computers, i.e. the infected and the working computer.
2. From the working computer, Go to Start> Run, type regedit.exe and hit enter. This will launch the registry editor.
3. Go to File> Connect Network Registry, by using this infected computer’s name or IP address.
4. Locate the following entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
5. In this entry there is a key named userinit, double click on the key and set its value to “C:\WINDOWS\System32\userinit.exe,”
If the problem still persists then you need to run a repair setup. Check out for detailed instructions on running a repair setup over here.