Computer wakes from sleep automatically every night

Although disabling Orchestrator and various other steps such as disabling wake timers allows the system to stay in sleep mode, it will also prevent needed routine maintenance from occurring during off hours as well as prevent user configured off-hours tasks such  backups. Of course you can run those maintenance tasks during the day, but my personal preference is to run maintenance tasks during off hours.  Not everyone will agree, but I recommend the following as a more selective and effective diagnostic process to isolate the root cause of the problem.

Note that the problem is not that Orchestrator is waking the system. It is supposed to do that. The problem is that once the task is complete, something is preventing sleep.

The following diagnostic steps will allow you to determine what that is. Run this first thing when you find your computer is awake rather than in sleep mode as expected.

1. Open a Command Prompt with administrative privileges
2. Run    powercfg /systemsleepdiagnostics
3. Open the resulting html report    C:\Windows\System32\system-sleep-diagnostics.html

This report covers 3 days and includes info on power requests, sleep states changes, and sleep intervals. 

The Power requests sections lists what processes woke the system and for how long. It's color coded green/yellow/red.

Generally you can ignore the green/yellow as they are normal tasks that take minimal time. 

Select Power Requestsand select anything that is Red. There are no generalizations as to what you may find and what actions to take since it is specific to what is installed/configured on your system. In my case it was MiniTool ShadowMaker which I had installed and tested, but decided not to use. There was probably some configuration change I could of done, but I simply uninstalled it.

Since that time (about 3 months ago) I have never found my system awake in the morning. However, Backups run at night as scheduled, Windows Automatic Maintenance runs nightly as scheduled and the computer goes back to sleep as expected.

When I run the "powercfg /systemsleepdiagnostics" command it says "This command requires administrator privileges and must be executed from an elevated command prompt."

Because powercfg must be run from an elevated command prompt.

I do not think it is the whole truth. My PC is not configured to go to sleep. I use it frequently and I just do not want it to be so. If I had to enable autosleep, it would have to be a really long timeout, like a couple of hours. When I stop using it, I used to manually hibernate it.

If I configured it with such long timeout, that means that, when it gets woken up by UpdateOrchestrator at night, it would stay powered on until morning, which means I could very well hibernate it manually again then.

The result is that now I just power it off rather hibernate, to block auto-wakeups.

M$ certainly got broken something here and I recall it started to happen with 1903 update. Before that, even though I had auto-sleep disabled, it would wake up to check for updates and then go asleep again. It is not happening anymore since that update and it is what most folks here are experiencing since then I think.

This automatic wakeups to perform updates have another side effect. My wife's laptop is actually configured to go to sleep automatically. So it wakes up to install updates, then reboots (if needed). But it is conifgured with BitLocker and the laptop does not have TPM so there's a boot password required. The effect is that rather to finish installing updates and go to sleep, it stays powered on awaiting for the boot password.

I think most folks here need a way to disable these autowakeups which are broken since 1903 release and requires workarounds or fixes that impact other functionalities and are not easy to implement for lee experienced people.