On Thu, 10 May 2018 10:07:37 -0400, Paul wrote:

Optimist wrote:
My update status says that KB4103727 and KB4103729 are awaiting restart.

The PC is left running all night with all user applications shut down, with non-active hours set for
the night time.

The PC neither bothered to go to sleep last night nor restart.

Wasn't the whole point of active hours to ensure the PC will be kept up-to-date without the user
needing to intervene?

It looks like it's a scheduled task of some sort. It
belongs to the Update Orchestrator. Your fix isn't
here, and this is only peripherally related.
Update Orchestrator is part of the delivery system.

https://www.windowscentral.com/how-p...alling-updates

You can turn on "History Recording for all Tasks" if you want. In
this case though, I don't think it records the "Not" of the trigger
condition. It would only record if the Task ran or not.

https://s14.postimg.cc/3rwjk9hn5/Tas...er_History.gif

*******

https://superuser.com/questions/5329...-automatically

powercfg -energy

That gives a report, which can include why a computer isn't
sleeping. Something as simple as having VLC open could account
for your symptoms (a multimedia task that stops wake timers
or something).

Try this for more info

powercfg /?

That would work best from an Administrator command prompt window.

Using the right click menu, if yours still says "Powershell",
you can simply type "cmd" into the Administrator one, to
start an administrator command prompt session.

Paul

This morning the PC had gone to sleep so I had to log on again. But once again, it had not bothered
to restart outside the active hours, so I restarted it myself and went off for a cuppa.

It's obvious that this active hours feature is just totally pointless.