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-12-09T16:18:33+00:00

    This seemed to work for me:

    Win10 PC Won't Sleep Anymore Solved - Page 2 - Windows 10 Forums (tenforums.com)

    Went to Device Manager > Network adapters > click on Properties for all the devices and then go to Power Management. There was a Realtek device that was checked "Allow this device to wake the computer"

    After I unchecked it, I ran Powercfg -requests and it came back clean.

    Good luck

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-12-12T10:04:03+00:00

    I've had the issue where Windows won't go to sleep since at least early November and it got to the point where I was manually forcing it to sleep, but running a sleep study for the past few days shows that it's actually waking after I force it to sleep. 

    In terms of suggestions that have worked for others;

    -I don't have a Realtek device and my Intel network adapter isn't set to wake the computer, plus the link provided is from 2019 so it looks like it pre-dates the current bug

    -I tried installing KB4568831 but Windows Update said the update is not applicable to my computer

    MoUseCoreWorker.exe definitely seems to be the culprit and I don't doubt the issue has been introduced by yet another a buggy update.

    I got burned pretty badly by an update back in April 2018 that repeatedly failed to install and killed my display driver in the process (so much fun digging up my old 19' Dell monitor every couple of weeks to again re-install the drivers for the 34' only for the update to try and fail again and again somehow screw up the driver) then following an update late last year my computer would repeatedly hang on the splash screen when waking up. So my confidence in Windows as a product is as low as it gets. 

    I just wish there was a way to incentivise Microsoft to lift it's game, it's completely unacceptable for an operating system to be this unreliable. QA across the Microsoft product range is pretty flaky these days (don't get me started on Power BI), so I think the issue is more organisational dysfunction than shift in focus away from Windows development.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-12-12T17:50:40+00:00

    I have the same issue in powercfg. How can i change the line under execution to none. Also hopefully it will remain as

    EXECUTION

    NONE

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-12-14T16:09:15+00:00

    For what it's worth, it's easy to temporarily solve this problem by going into Windows Update Settings and pausing updates. Immediately upon doing this, powercfg stopped showing the USO Worker in the "EXECUTION" section.

    Unfortunately, once the pause ends (whether automatically or manually) the problem recurs and the USO Worker thread prevents sleep again. I may have to keep updates paused and set myself a weekly reminder to check, which shouldn't be necessary on a modern OS.

    My machine uses S3 standby. I have to wonder if everyone at Microsoft is using Modern Standby now, and thus they don't even notice when problems occur on S3 standby systems?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-12-15T06:36:11+00:00

    I have the same problem. I'm surprised it's still not fixed 🤯

    Was this answer helpful?

    0 comments