This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Had the same problem.
I checked for updates via Windows Update - it said - no new updates.
I restarted the Windows Update service.
I checked for updates via Windows Update again (2 min later), and now Windows Update finds new updates.
It seems like windows update is stuck in a loop and thus the services keeps on staying alive.
I think that it probably fixed my problem. If anything new will happen, I'll update here.
I installed the driver development kit pwrtest module that showed that it is definitely MoUsoCoreWorker.exe. So no new info on how to fix it, but at least confirms what it is.
The process is described here - but a bit of a hassle, must install Visual C++ and some development kits. I am a programmer - so not a big drama, but perhaps a little frustrating for the uninitiated.....
https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/pwrtest-monitor-scenario
From blending together the .\pwrtest /monitor and .\pwrtest /requests logs, i have (Bolding Mine)
07:16:27 1 Idle: 45 seconds
07:16:32 1 Idle: 50 seconds
07:16:37 1 Idle: 55 seconds
07:16:37 1 Physical Monitor State: On -> Off (Monitor shuts down)
07:16:37 Close: AMD High Definition Audio Device (<<< Shutdown here)
07:16:37 Change: \Device\HarddiskVolume3\Windows\System32\MoUsoCoreWorker.exe
Count: System:0 Display:0 AwayMode:0 PerfBoost:0
ExecutionRequired:0 FullScreenVideo:0
(<<< Muso runs)
07:16:38 Create: \Device\HarddiskVolume3\Windows\System32\MoUsoCoreWorker.exe
Type:Application ProcessID:5552 SessionID:0
Allow: System AwayMode PerfBoost ExecutionRequired
Count: System:0 Display:0 AwayMode:0 PerfBoost:0
ExecutionRequired:0 FullScreenVideo:0
07:16:38 Change: \Device\HarddiskVolume3\Windows\System32\MoUsoCoreWorker.exe
Count: System:0 Display:0 AwayMode:0 PerfBoost:0
*ExecutionRequired:1 FullScreenVideo:0 (<<< Muso seems to demand execution)
07:16:38 Change: \Device\HarddiskVolume3\Windows\System32\MoUsoCoreWorker.exe
Count: System:0 Display:0 AwayMode:0 PerfBoost:0
ExecutionRequired:0 FullScreenVideo:0
07:16:38 1 Idle Reset (<< Wake up buddy!!!!) ****
07:16:38 1 Physical Monitor State: Off -> On (<<< System wakes up again)
07:16:39 Create: \Driver\AtiHDAudioService
Type:Driver ProcessID:0 SessionID:0
Allow: System PerfBoost
Count: System:0 Display:0 AwayMode:0 PerfBoost:0
ExecutionRequired:0 FullScreenVideo:0
Hi Alanasff, thank you for your reply. Yes, the PC is wired via Cat5, but unplugging that has made no difference. :( I should say I had this problem from the outset with this PC, and after much searching online I found that my Samsung Magician SSD software was the culprit. As soon as I stopped that from autostarting with Windows, the problem was resolved. It was then fine ever since, up until the Windows 10 Feature Update 2004 arrived on my PC a few weeks back, and then the problem came back (albeit with one subtle difference - last time it only happened on the first sleep attempt, but this time it happens on every sleep attempt).
I suppose it could be unrelated to the W10 update, but it seems quite a coincidence timing-wise. The only other thing that has changed recently is that I've relocated my router so the Cat5 plugs into a powerline adapter rather than directly into the router - that's what made me think to try unplugging it, but as I say that made no difference. I spent something like a couple of hours on a remote support session with a MS technician the other week and he tried various diagnostics, resetting power preferences and so on, all to no avail.
On my system, wake-on-lan is disabled. So, I don't think that it is the cause of the problem, at least on my PC.
Zochtu; I have seen the issue whereby it goes to sleep but then wakes up immediately. I don't think this is related to MoUsoCoreWorker and the wakeup is hardware related as MoUsoCoreWorker (and indeed Windows itself) isn't running once the PC is actually asleep. I did notice one odd thing though, that perhaps you could confirm; is your PC wired to your network (i.e. with a Cat5 cable)? If so, try unplugging the Cat5 and letting it go to sleep... when I did that mine stayed asleep as if something on my network is sending it wakeup packets causing the network card to wake the PC up again. Do you see the same?
