Windows 10: Wake remote Win 10 PC-> Wolcmd command-> Works manual, not in cmd

I have a Win 10 PC acting as a media server. I want it to sleep unless needed.

To make the use easy, especially for my wife, I want to have a WOL packet sent to it when I boot or login to another PC. I can accomplish the remote wake with Wolcmd.

I have written a batch file that I can run from a CMD prompt which wakes the computer fine.

But, when I run that bat file via the Task scheduler, it does not wake the PC. I have turned on History Logging and see that it is running. Really don't need that, as I see it open a CMD window and run.

I can't imagine why it won't work from the Task Scheduler.

Any ideas?

:)

 

Turn system icons on or off network greyed out! windows 10

Okay guys I solved it.

I did 2 things simultaneously so not exactly sure which worked, just do both:

1. Enable Event Log service

Go to control panel >> Administrative tools

or

Start button and type: Administrative tools

Click on Services

Find Windows Event Log, if it's not running right click it and Start it

if Start is not an option

Right click it >> Properties >> Change startup type form Disabled to Manual or Automatic.

>>Apply >>OK >>right click it again and Start. It should say Running...

2. Run the System File Checker scan

Open windows commander (win+R, type cmd)

In commander type "sfc /scannow"

System will start scan. On my machine it found some errors and repaired them.

After it's finished, restart your PC

and voila! - everything works

 

Windows 10 PC wakes spontaneuously shortly after going into sleep state--behavior started after the November 2015 update

Your comment about the magic packet induced me to do something I should have known to do from the outset: check the wake-up settings of the network adapter. I actually do want to be able to wake up the PC remotely using an app that send a magic
packet. However, I don't want any packet to wake the PC--just a magic packet.

When I went to look at the adapter properties I saw that "Allow this device to wake the computer" checkbox was checked (as I expect/want) but the "Only allow a magic packet to wake the computer" sub-checkbox was cleared (which is not what I want).
I'm pretty sure I went through these settings months back when I got the whole sleep/remote-wake thing working in the first place. I'm tempted to believe that the upgrade cleared the "Only allow a magic packet ..." checkbox. (After all, the upgrade changed
my default browser setting back to Edge when it had been Chrome.)

Anyway, I set that second checkbox and hopefully things will behave better now.

Thanks for your help.

 

NVM...I figured it out.

Even though the bat file and the wolcmd.exe were in the same directory, I needed to specify the path to wolcmd.exe within the batch file.

The batch file,when run from the Task Scheduler, does not look in it's own directory. So, with no path variable set up for that directory, it was failing.