Solved Screen Saver to password logon screen failing

[rzn6jw]

I have set up my Win 7 Pro 64-bit screen saver to bring up the password logon screen upon activation of the mouse/keyboard/whatever.

Late last week, whenever I moved the mouse or clicked the keyboard, the screensaver would go directly to the desktop, bypassing the logon screen. I went to the screensaver utility and unchecked and rechecked the 'On resume, display the logon screen' box, selecting 'Apply and OK' each time.

This would work for maybe two or three times and then go back to returning to the desktop.

I've run MalwareBytes, IOBit, and Norton and all come up virus/rootkit free.

Any ideas?

 

[F5ing]

There are a few seconds of "grace" time, meaning when the screensaver launches you have a few seconds to "wake it" and go back to your desktop without locking it.

I guess I can assume you're not talking about that, right?

 

[rzn6jw]

No, I can catch it fast enough if I want to return to the desktop.

This happens after some time has passed with the screensaver running. In the past (pre-service pack 1 days) I could re-boot the PC and take care of the problem that way. Now, for the last few weeks, this problem won't go away.

It's funny that it'll work two or three times after I re-do the screen saver configuration, and then stop working. It's almost like there's malware running that is playing with me, letting me start correctly and then removing the password protection. But I don't show any malware/rootkit infection.

Anyway, it's a mystery to me. Also, I don't know where to look deep in the Administration Security configuration to see if a DWORD is on or off. Maybe someone could point me in that direction.

Thanks for all you help so far!

 

[EzioAuditore]

Try running www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[rzn6jw]

The first time I tried running SFC /SCANNOW I found that the Windows Module Installer was disabled. SFC ran after I made the module 'Automatic'. I will try the screen saver password after SFC runs.

Something like this happened last year when Windows Update could not install new updates. I checked through the Services and found that the Installer was disabled.

What could disable the Module Installer anyhow?

 

[EzioAuditore]

The first time I tried running SFC /SCANNOW I found that the Windows Module Installer was disabled. SFC ran after I made the module 'Automatic'. I will try the screen saver password after SFC runs.

Something like this happened last year when Windows Update could not install new updates. I checked through the Services and found that the Installer was disabled.

What could disable the Module Installer anyhow?

Anything. May be some malware, or cold be some setting related to windows updates as it is responsible for managing the installation/removal of updates.

Does it happen with every screensavers? Are you using default screensavers or custom installed?

 

[rzn6jw]

No custom screensavers. Have used Mystify forever. Like I said, this happened once with Update, but Update has run every time since - no errors.

Screensaver to password screen seems to be working fine now. Will keep an eye on WMI if something like this happens again.

Thanks for all your help!!

 

[EzioAuditore]

For the Windows Module Installer service, double click it and navigate to Recovery tab and make sure the first two drop-down lists say "Restart the service".
Since you seem to like using mystify screensaver, this may interest you- www.sevenforums.com/tutorials/2140-mystify-screen-saver-change-settings.html