Windows 10 Sleeps Before UpdateEPG and Recordings Start

[spartankl01]

I found the answer to a very frustrating problem and wanted to post it for others. I was having a problem where my Windows 10 PC would wake and start an UpdateEPG or a recording, but the PC would go to sleep after one minute. Here is an example of a failed UpdateEPG that was scheduled for 1:00 AM:

2018-01-16 01:00:05.048 [DEBUG][74] Resuming...
2018-01-16 01:00:05.817 [DEBUG][6] cycling MVP servers
2018-01-16 01:00:13.026 [DEBUG][9] Recording service noted the system was resuming...
2018-01-16 01:00:13.026 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2018-01-16 01:00:13.327 [DEBUG][9] PurgeOldDeletes()
2018-01-16 01:00:34.646 [DEBUG][10] Pre EPG Update
2018-01-16 03:44:01.044 [DEBUG][74] Resuming...

The UpdateEPG would complete when I would later press the power button in the morning. Recordings were similar:

2018-01-16 08:56:05.035 [DEBUG][28] Resuming...
2018-01-16 08:56:05.535 [DEBUG][6] cycling MVP servers
2018-01-16 08:56:12.842 [DEBUG][9] Recording service noted the system was resuming...
2018-01-16 08:56:12.842 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat

but all my recordings reported "Recording service not running at recording time."

There is a hidden Windows 10 setting "System unattended sleep timeout" that was set to one minute. It appears NPVR did not start telling Windows 10 to "stay awake" in the first minute and the PC just went back to sleep.

I found this Windows Q&A that solved my problem: https://answers.microsoft.com/en-us/wind...52d?auth=1

I adjusted the setting to 10 minutes and this gave enough time for NPVR to start sending the "stay awake" messages to Windows 10. My PC then went to sleep 10 minutes after UpdateEPG or Recordings completed.

Hope this helps others as it took me a long time to solve this problem.

[HarryH3]

The settings choices that the "New Microsoft" uses as defaults never cease to amaze me. It would be interesting to know just how many billions of dollars have been wasted worldwide on people "fixing" things that worked fine before Windows 10 installed or a Windows 10 update was forced out with inadequate testing.

[sub]

I've made a change for the next release that will fix this.