Hi Dushter,
I am willing to give your solution a try but I have a question: If you stop the Update Orchestrator service, is Windows Update still functional or you have to run it manually once in a while?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
My computer (Windows 10, 64-bit Build 19041) is constantly waking up from sleep and then going back to sleep for a short time only to repeat the cycle. I ran sleep diagnostics on the Windows PowerShell as administrator i.e. powercfg /systemsleepdiagnostics. The report from yesterday (5/31/2020) indicates that my computer awoke from sleep 50-55 times during the course of the day until at about 8:00 p.m., I decided that it was better to fully shut down the computer rather than have these continued cycles. The common thread in all these awakenings from sleep is MoUSO Core Worker Process (MoUsoCoreWorker.exe).
- Power Requests
- \Device\HarddiskVolume5\Windows\System32\MoUsoCoreWorker.exe | START TIME | DURATION | TYPE | TOKEN | | --- | --- | --- | --- | | 2020-05-31T18:18:53 | 0:00:01 | Execution | 0xffff8389192ab2e0 |
This executable is a Microsoft programming element.
Why is this happening and what can I do to eliminate this totally annoying phenomena?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi Dushter,
I am willing to give your solution a try but I have a question: If you stop the Update Orchestrator service, is Windows Update still functional or you have to run it manually once in a while?
At face value I would agree, but I've noticed conditional retry rules for tasks may not make it that straight forward (e.g. an other underlying update task may have its reasons for not completing, thus leaving WU triggered but not affecting sleep mode - I've seen it). I know this doesn't make total sense either, but for the vast majority of the time, it so far is working satisfactorily, and I wanted peops to know the good of this for the amount of work involved.
I run mine every other day, and so far it has not run into circular problems. I'm only working in so much light, a.k.a. knowledge, and can't make the effort to go further down this rabbit hole. - Entropy is always increasing.
It's good to know you have another method in case the problem rears again beyond my method's ability.
I've conformed to not doing so many things manually anymore since there are a bazillion people involved for a gazillion possibilities of which path/ideology is going to take precedence (e.g. I was noticing today how file archive attribute ideology is mostly now abandoned).
Also, I've tried the disable MSO worker recommendation (can't think of the exact words right now), but it gave my system MAJOR problems --- I thought it was going to need a complete re-install, but it managed to get out of what ever problem was caused, so I abandoned that idea immediately.
Anyway, glad yours works too. For now, I'm sticking with what's working on mine.
that task should be run every 5 minutes if you want your computer to sleep every time when it should. if you do that once a day, there is possibility that in one day your computer will be awake almost 24h. my solution still works. i have done it on my computer 4-5months ago or something and it still sleeps when needed.
My sense is the scenario is very convoluted to simply resolve. The implemented task (see above, page 26) has been working well ! I'm almost over delusions of hearing the computer on :) and have now regained trust.
Thanks to showstopper for helping with the task commands!
The update 21H1 worked for me as well when I installed it in March, but now there was another update on April 16th and the problem is back. This is getting very annoying.