I never had any problem with the Windows 7 screensaver. But now I'm using Windows 10 and I can't get the Windows 10 screensaver to stop. I 'm just using the standard blank screen screensaver and it does not require a login. It's not going to sleep or hibernation.
For testing purposes I'm using this code. I scheduled the job and the screensaver does not go off when the macro runs. When I later manually press the Esc key (or move the mouse) the screensaver goes off and I see that Notepad is open and no text has been entered.
//This script will open Notepad and type in some text.
Press Esc
Wait>1
MouseMove>200,300
MouseMove>1092,1059
Wait>1
LClick
Wait>3
//Run Notepad
Run>Notepad.exe
//Wait for Notepad to be ready
WaitWindowOpen>Untitled - Notepad
//Send some text
Send>Hello World
Press Enter * 2
// more code from the Sample macro not shown
I'd prefer a solution that does not require editing the registry. I"m using Macro Scheduler 14.2.03.
Thanks!!
Brian
Windows 10 screensaver won't stop
Moderators: JRL, Dorian (MJT support)
- Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
Re: Windows 10 screensaver won't stop
Unfortunately there have been big changes in Windows 8/10 to the security of the operating system. The screensaver no longer appears to run under the user's console. Therefore it is not possible to kill it.
However, with AutoLogon you can have a scheduled macro unlock a locked console. So - paradoxically - if you set Windows to lock after a timeout, Macro Scheduler with AutoLogon can unlock it and run the macro, but it can't stop a regular screen saver.
So if possible you need to set your Screensaver to "none" and set your username/password under AutoLogon in Macro Properties. Windows will then go straight to the lock screen instead of running the screensaver, and then Macro Scheduler will be able to unlock the console before running the macro.
However, with AutoLogon you can have a scheduled macro unlock a locked console. So - paradoxically - if you set Windows to lock after a timeout, Macro Scheduler with AutoLogon can unlock it and run the macro, but it can't stop a regular screen saver.
So if possible you need to set your Screensaver to "none" and set your username/password under AutoLogon in Macro Properties. Windows will then go straight to the lock screen instead of running the screensaver, and then Macro Scheduler will be able to unlock the console before running the macro.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
Re: Windows 10 screensaver won't stop
Thanks for the explanation!! I wasn't sure if I was the only person having this Windows 10 problem, but obviously not.
I just did a search for a screensaver program to use rather than Windows 10's screensaver, but then I saw on HowToGeek.com that LED monitors won't burn in the image, so I decided not to worry about it.
Thanks again.
Brian
I just did a search for a screensaver program to use rather than Windows 10's screensaver, but then I saw on HowToGeek.com that LED monitors won't burn in the image, so I decided not to worry about it.
Thanks again.
Brian
- Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
Re: Windows 10 screensaver won't stop
Yep ScreenSavers are a hangover from CRT days!
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?