No doubt, we all have been using the sleep option in Windows 10 to save energy. It makes sure that you quickly resume your work without waiting for Windows to complete the start-up process.
As a matter of fact, your PC enters into a power-saving mode when you put it to sleep. In this mode, the system just keeps enough power that is required to refresh its memory. However, most of the components in your system are shutdown.
The sleep function was working fine for users until the release of Windows 10 v1909. A good number of Windows 10 users have claimed that the latest feature update is playing havoc with their PCs. In a forum report, one furious Windows 10 user mentioned that the PC keeps waking up on its own.
“Since the update, my computer wakes up every day around 10 AM (it could be worse..), Using “powercfg/lastwake” in a command shell I found it was waking due to a scheduled task: ‘NTTASK\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start’.”
No Official Acknowledgment From Microsoft
The worst thing about this problem is that the system stays on when it is supposed to sleep. This situation ends up draining the entire battery of your Windows 10 system.
It seems to be a mysterious effect that forces Windows 10 systems to wake up from the energy-saving mode. People think that perhaps some sort of wake timer enables for systems running Windows 10 v1909. However, the issue is actually caused by the Update Orchestrator Service.
The service is basically responsible for downloading and installing updates for Windows 10 OS. Even though it’s a useful service but sometimes turns out to be annoying for many of us. The Update Orchestrator Service increases the resource consumption of your PC by around 70%.
Notably, it is not the first that this issue has been noticed. Someone reported a similar issue caused by another Windows 10 update back in February 2018. The OP described the problem on the Microsoft Answers forum and some people confirmed that disabling the Update Orchestrator Service fixed the issue for them.
At the moment, there is no official acknowledgment from Microsoft. We hope that Microsoft immediately investigates the matter and releases a fix as a part of January Patch Tuesday Updates.