nPVR Continually Wakes PC

[itm2]

First, let me know if I should start a new thread.  This seems like a good place to start for now.

I am a WMC refugee configuring my first NextPVR box, and am experiencing the same wake/failure to sleep issue.  As yet I have not scheduled recordings, and EPG is scheduled to update from Schedules Direct at 0345 hrs.  That's not the cause, the issues I describe here occur in the afternoon and early evening, which is the time I have to work on the PC.

I find that the NPVR Recording Service keeps waking the PC shortly after it sleeps, as determined using powercfg /lastwake.  The time till it wakes can range from 1 to 30 minutes or so after I manually sleep the box.  After it wakes, it will not sleep again.

The issue does not occur if the NextPVR service is stopped.  Restarting the service or the PC does not help:  I have restarted the PC, put it to sleep, and have NextPVR wake it after a minute or so.

This is a new Windows 10 1909 install, and NextPVR is the only program the PC is used for.

Has anyone found a solution to this?

2 years later...I also have this problem (NPVR v5.25 on Windows 10). NextPVRServer.exe is waking the PC just a minute after I have manually put it into sleep mode. I have no scheduled recordings for the next 9 hours, my next scheduled EPG update is also >9 hours away. 

Code:

C:\Users\My User>powercfg /lastwake
Wake History Count - 1
Wake History [0]
  Wake Source Count - 1
  Wake Source [0]
    Type: Wake Timer
    Owner: [PROCESS] \Device\HarddiskVolume3\Program Files\NextPVR\NextPVRServer.exe

There's nothing in any of the NPVR logs for the time that the PC was last woken from sleep (Nrecord.log/NPVR.log/device-***.log). I restarted the NPVR service several times yesterday.
Any ideas for how I can diagnose this further?

I have my network adapter configured to allow magic packets only to wake it.

[mvallevand]

It will still be a local issue, with some BIOS or Windows setting for network, drive activity, USB or the hidden wake option that is doing this or everyone would not be able to put their machine to sleep.

Martin

[sub]

You can check the nrecord.log for any messages starting with "Requesting wake up for". These are the cases where is scheduling the machine to be awake at a specific time.

If that doesn't show anything, you can enable verbose logging, and check for any messages starting with "PowerManagement". These are cases where it's actively doing something, and needing the machine to stay awake.

[sub]

Realistically, you'll probably find you've got your power management settings in Windows set a bit too tight, and you need to increase the time without activity or something before sleeping/