Waking Windows 10 machine outside of EPG update schedule

[itm2]

I have NextPVR 4.0.4 installed on a Windows 10 Pro machine. It seems to be waking the machine at around 07:48 each morning, even though I have the EPG update scheduled for 19:13 (i.e. the evening). My NRecord log is attached (please note that I changed my EPG update time from 02:13 to 19:13 yesterday, but the machine still woke at 07:48 as well as 02:13 yesterday). I have no recordings scheduled, so the wake could not have been caused by a scheduled recording.

Below are the latest powercfg results from windows:

Code:

C:\WINDOWS\system32>powercfg -waketimers
Timer set by [SERVICE] \Device\HarddiskVolume2\Program Files (x86)\NPVR\NRecord.exe (NPVR Recording Service) expires at 19:12:59 on 03/08/2017.

C:\WINDOWS\system32>powercfg -lastwake
Wake History Count - 1
Wake History [0]
  Wake Source Count - 1
  Wake Source [0]
    Type: Device
    Instance Path: PCI\VEN_10EC&DEV_8168&SUBSYS_83A31043&REV_03\4&1a6b7f80&0&0050
    Friendly Name: Realtek PCIe GBE Family Controller
    Description: Realtek PCIe GBE Family Controller
    Manufacturer: Realtek

While the wake at 07:48 was not directly attributed to NPVR the machine doesn't have much else on it (it was built specifically to run NPVR), so I can't imagine what else would be waking it.
???

[Graham]

Friendly Name: Realtek PCIe GBE Family Controller
Description: Realtek PCIe GBE Family Controller

It appears that the network controller in the 'puter is receiving something from somewhere that causes the network controller to wake the machine. Does a mobile phone or something come out of standby at about 07.48?

To stop the network controller from waking the machine ... Device Manager --> Properties --> Power Management --> Tick off "Allow this device to wake the computer".

[mvallevand]

What Graham posted is the safest bet, however if you want WOL to work so you can connect to the server from a client that won't be a good solution. I suspect that you have the NIC option to wake on pattern match ane netbios or something else from a different PC woke the box.

Martin

[itm2]

What Graham posted is the safest bet, however if you want WOL to work so you can connect to the server from a client that won't be a good solution. I suspect that you have the NIC option to wake on pattern match ane netbios or something else from a different PC woke the box.

Martin

Yes that's exactly right - I have the NIC wake option set so that I can use WOL from other devices on the network.

I have a bunch of other devices on the network (mainly Intel PCs and Android phones and tablets). None are explicitly scheduled to do anything at that time in the morning, and certainly none are configured to connect to the HTPC on a scheduled basis. Any idea what sort of network events might inadvertently wake up a NIC?

[pBS]

go into net adapter settings and set wol to magic packet only...
at least turn off pattern match cuz it will wake pc when *any* other pc comes on within network..[and that pc looks for network resources]
magic packet can target the specific computer..[it's a rearranged mashup of computer's network card mac address]
magic packet targeting is the way almost all wol utils work..

[itm2]

go into net adapter settings and set wol to magic packet only...
at least turn off pattern match cuz it will wake pc when *any* other pc comes on within network..[and that pc looks for network resources]
magic packet can target the specific computer..[it's a rearranged mashup of computer's network card mac address]
magic packet targeting is the way almost all wol utils work..

If I set the magic packet only option I find that WOL doesn't work - i.e. if I put the machine into sleep mode, then try to wake it from another Windows 10 machine using the Wake On Lan App, the target PC doesn't wake.

[mvallevand]

Any idea what sort of network events might inadvertently wake up a NIC?

I suspect it is NetBIOS Name Resolution, any device that might have your backend server "hostname" cached could wake it looking for it.

Under power management there is a tick to only allow magic packets to wake the machine. Maybe that will help.

Martin

[itm2]

I suspect it is NetBIOS Name Resolution, any device that might have your backend server "hostname" cached could wake it looking for it.

Under power management there is a tick to only allow magic packets to wake the machine. Maybe that will help.

Martin

It's that "magic packets only" tick that seems to disable WOL. Untick it and it wakes fine, but also wakes when I don't want it to (which is the problem).

I don't think any of my Android devices have the WINS name of my HTPC defined - they all refer to its (static) IP address. Even if they did, none of them would be in use at that time of the morning!

[pBS]

hmm,that's the exact opposite of how it's supposed to work..if all other wake on lan triggers are disabled, and only magic packet is set to wake, then only if you send the 'proper' wake on lan command [targeting that exact adapter hardware] will it wake the pc..nothing else should, and that should always wake it if set..
tho i hear win10 doesn't honor things you setup...lol

run powershell and type this into it.."Get-ScheduledTask | where {$_.settings.waketorun}"
to list other tasks scheduled to run..look for odd ones...
you may also have the 'update orchestrator' creating new scheduled wakes..TaskName is “Reboot” and is located in folder “\Microsoft\Windows\UpdateOrchestrator\”.
Task Scheduler (Local) > Task Scheduler Library > Microsoft > Windows > UpdateOrchestrator, and right-click on Reboot and click Properties: disable wake this task,etc..

oh and win10's 'wake on lan' app might be crap...may not be actually be sending 'magic packet' to wol...which is why it breaks when magic packet only is selected..
there are tons of small apps that can wol properly out there.

[pBS]

http://www.sysadminshowto.com/wp-content...-8.1-3.jpg
http://www.sysadminshowto.com/wp-content...-8.1-4.jpg

it also may be your driver if a realtek network card..make sure it's the correct one for your specific hardware..newest not always best..
oh and turn off 'green ethernet'


what app are you using to do the wol?