Mouso core worker process

Anonymous
2020-06-02T04:20:14+00:00

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?

Windows for home | Windows 10 | Sleep and Power on, off

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.

0 comments

317 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-03T14:03:46+00:00

    In my case I stopped the Windows Update service which allowed the pending updates to install; the computer then went to sleep.

    But I'm sure this will occur at the next update, unless what I just installed patches the issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-03T14:19:31+00:00

    Same here. I wonder if there is a separate problem, unrelated to Windows Update and this particular process? Mine will actually attempt going into sleep mode - it just wakes up again immediately. Not sure how that compares with others' experience here.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-03T15:37:22+00:00

    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?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-03T16:01:31+00:00

    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.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-03T16:05:17+00:00

    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.

    Was this answer helpful?

    0 comments