|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.