I noticed that both my Wife and my PC didn't go to sleep last night. Both have this process running... No updates...
Have you tried turning your Wife on and off again ?
Otherwise, I'd recommend an upgrade to Wife 2.0.
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.
I noticed that both my Wife and my PC didn't go to sleep last night. Both have this process running... No updates...
Have you tried turning your Wife on and off again ?
Otherwise, I'd recommend an upgrade to Wife 2.0.
This should fix the issue:
I recommend following solutions in this order:
these are not fixes for that particular problem. only number 3 is and it is also a wrong fix. you do not have to disable the service, all you need is to change it to 'manual' (not 'disabled'!) and stop the service.
this thread should be disabled. there is so much answers and also total bs which is not related to this particular mousocoreworker.exe/update orchestrator service bug at all.
Does anyone know if Microsoft intends to fix this problem?