Wake monitors from power save via script.

I am trying to utilize a script to enable my monitors on a Windows 8.1 system after "Turn off the display" power saving and having no luck at all. The script is fired off by a motion sensor in the room, so that when a user's presence is detected it will automatically light up the display.  The only way I've found so far to wake the monitors is to physically move the mouse or press a key. 

I have the Windows power settings set to "Turn off the display" after 1 minute (for testing) and "Put the computer to sleep" set to "Never". When the system goes into powersave for the monitors, the monitors sleep and go dark. The control panel on the base on the monitors also go dark in response. When I issue most of the commands I've tried below, the control panel on the monitor lights up but the monitors themselves never turn back on. It's like the computer is exiting powersave but not waking up the screen until something physically moves.

Here is what I've tried:

  • nircmd monitor on (hangs)
  • nircmd monitor async_on (doesn't hang but doesn't turn the monitor on)
  • AutoIt script to move the mouse (move 100x by 100y)
  • Wake on LAN from remote system
  • Powershell script to simulate local keyboard input or mouse movement

Nothing seems to work outside of physically touching a button or moving a mouse. Has anyone gotten something like this to work?

Note: I asked this question previously and wasn't able to respond in time to prevent a non-working suggestion marked as an answer.  I'm re-issuing this question in hopes of an answer that will work.


February 16th, 2015 3:08pm

Note: I asked this question previously and wasn't able to respond in time to prevent a non-working suggestion marked as an answer.  I'm re-issuing this question in hopes of an answer that will work.

That thread doesn't have anything marked as an answer, only one marked as a proposed answer. As the original poster you have the ability to unmark any answers if they are not sufficient. I would suggest moving back to that thread as anyone who wishes to assist will know the steps that have been taken, preventing a lot of wasted time. Please don't expect those trying to help you to read through multiple forums in order to ascertain what steps have already been tried.

  • Edited by Acreed02 15 hours 30 minutes ago
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2015 3:16pm

Note: I asked this question previously and wasn't able to respond in time to prevent a non-working suggestion marked as an answer.  I'm re-issuing this question in hopes of an answer that will work.

That thread doesn't have anything marked as an answer, only one marked as a proposed answer. As the original poster you have the ability to unmark any answers if they are not sufficient. I would suggest moving back to that thread as anyone who wishes to assist will know the steps that have been taken, preventing a lot of wasted time. Please don't expect those trying to help you to read through multiple forums in order to ascertain what steps have already been tried.

  • Edited by Acreed02 Monday, February 16, 2015 8:13 PM
February 16th, 2015 11:13pm

Hi aderusha,

Regarding Script related issue, it is recommended to seek help at hte scripting guys forum:

https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG

I am not familiar with scripting, little help could be offered here.

Besides, please see if the following article would help:

Monitor and Respond to Windows Power Events with PowerShell

Thank you for your understanding.

Best regards

Free Windows Admin Tool Kit Click here and download it now
February 17th, 2015 4:54am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics