Lock PC with screensaver now!

Amd / Athlon xp 1800mhz
April 27, 2009 at 15:27:37
Specs: Windows XP, 512MB
Somebody asked a while back, how to manually run a (by session) password protected screen saver in XP. According to M$ this is a silly security 'feature' (ie bug), disabled 'by design'. An easy way to overcome this new 'enhancedness', is to do it in an automated two fold process; ie, created a batch file similar to this:

@START /WAIT /MIN /LOW %windir%\system32\sstext3d.scr /
@%windir%\system32\rundll32.exe user32.dll,LockWorkStation

Just mod for your screensaver of choice; and create a shortcut in your desktop with your favorite shortcut key... and voila!

See More: Lock PC with screensaver now!

June 4, 2009 at 16:10:35
Your statement isn't true. Regardless, you posted in the NT Forum.


Report •

November 25, 2010 at 00:34:39
Can I associate a key combination (similar to "Windows Key" + "L") with your batch file?

Also, is it possible to set a ten-second delay during which moving the mouse returns me to Windows without having to enter the password... and no other action required?

(I run Windows 7 64-bit Home Premium, but it should not make a difference, right?)

Report •

January 19, 2011 at 17:36:14
Please be aware that if someone walks up and presses CTRL-C, then they can exit the batchfile thereby gaining access to your unlocked workstation.

Report •

Related Solutions

June 25, 2011 at 10:42:55
Sobriquet, I think that's not entirely the case. Only if the lock hasn't effected itself yet. If you give it a good five count and try that, mine only dumps me out at the password entry prompt. You'd have to have console access to reply to the Y/N prompt to kill the batch and hit enter to actually end the script. When I tried it immediately, I got the same prompt, but I did see that the Ctrl-C made it through, as the batch window was waiting for the Y, CR, to terminate. If I give it the five count, the script ends as designed, having not received the control signal before the lock was enacted. My config includes using "scrnsave.exe" which is the configured screen saver, and having password access required after 10 minutes.

There is also a delay between screen saver and lock by default when permitting the screen saver to lock itself. I think it's five seconds by default. You have to set a registry entry to enable the lock to start immediately, else the SS can be cancelled before the lock if you're there in that 5 seconds after it initiates. I know this is not exactly the process we're following in this batch command file, but it makes me wonder if it's not relevant to how much time you can sneak in that Ctrl-C, and possibly the Y and CR. If I get time to test it, I'll repost here.


Report •

Ask Question