Mouso core worker process

Anonymous

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.

0 comments

317 answers

Anonymous

2021-02-24T08:49:18+00:00

THANK YOU!!! This is the definitive fix, after I did the restart and went into windows update, it was already updating to remove KB4023057.

This makes no sense. Why would windows remove KB4023057 it's a mandatory update? I would be delighted if KB4023057 could be removed. Anybody else able to verify this is possible?
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-02-24T03:06:30+00:00

THANK YOU!!! This is the definitive fix, after I did the restart and went into windows update, it was already updating to remove KB4023057.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-02-23T01:57:17+00:00

My success was: noting there was an unsuccessful update, KB4577586 (uninstalling Flash Player, in Other Updates); I installed the 20H2 Feature Update; then, KB4577586 reported as "successful", and the computer went to sleep at the first instance!

I think the key was MoUSOCoreWorker.exe was being held up by the failed KB4577586 update, thus keeping Update triggered (thus preventing sleep). Note: I had no extensions/add-ons/plug-ins of Flash Player, anyway.

What I don't understand is why the update status is so pervasive on preventing sleep-mode; I presume throughout the years other pending updates have not impeded sleep as strictly.

Edit: MoUSOCoreWorker can still be in effect even though Update Statuses are all successful. Sleep prevention has returned, but I manually ran the update(s), and sleep ability returned once again.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2020-10-05T23:26:50+00:00
Restart Windows Update Service

Open Command Prompt in Administrator mode and execute this command: powercfg /requests

If you see MoUsoCoreWorker.exe listed anywhere, then it’s because of the Windows Update

Open Service Manager, locate Windows Update service, and restart it.

Rerun the Power Config command, and check if the listing of MoUsoCoreWorker.exe is gone.

this information from :

https://www.thewindowsclub.com/what-is-mousocoreworker-exe
Someone needs to tell them its only a temporary fix. The process eventually comes back and prevents the computer from sleeping.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2020-10-04T20:38:24+00:00

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
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments