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-11-17T12:38:04+00:00

    the solution WAS : (its now different if you do a clean install with windows 10 version 20H2)

    the "C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start" file is now replaced in version 20H2 by UpdateModelTask file

    5 nights later after clean install of version 20H2 no awaking in sleep mode, like it did with version 2004 and older version without any modification

    read this all before doing anything

    with windows 10 home version 2004 :

    stop the updater in C:\windows\system32\tasks\microsoft\windows\UpdateOrchestrator by doing these :

    DO A COPY of "Universal Orchestrator Start" file to return to "normal" when you'll do the windows updates... store it where you will know to use it for when you'll do windows updates and only modify the the file kept in C:\Windows\System32\Tasks\Microsoft\Windows\UpdateOrchestrator

    modify

    file "Universal Orchestrator Start" in properties\security, add your user administrator name and check "full control" , disable inheritance in advance

    in powershell as administrator, 

    Disable-ScheduledTask "\Microsoft\Windows\UpdateOrchestrator\Universal Orchestrator Start"

    BUT 

    it stops all updatings

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-11-28T15:30:54+00:00

    As promised, just to feedback a couple of weeks later. The solution I outlined 10th November has worked for me. PC is now going into standby without fail as it always used to. A couple of days ago Windows version updated to 20H2 and standby is continuing to work fine.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-11-29T12:45:42+00:00

    "both my Wife and my PC didn't go to sleep last night. Both have this process running... "   Em . . . is your wife version 2.02 or 2.04?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-30T15:28:20+00:00

    People need to stop posting that they "solved" this.  There is no solving it.

    Since there are new updates in the queue the process is back again preventing computers from sleeping.  I for one will not mess with WU (stopping it, etc.) as I had to reinstall the OS after doing that permanently messed up WU.

    Microsoft sucks, plain and simple.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-11-30T16:43:24+00:00

    I've been using Windows for 30 years, now, and the one feature that has caused headache after headache the entire time is Windows Update. So you're right that "MS sucks," but not because of MoUso. Rather, it's because of this maddening, unending, and unbroken continuum of bugs in Update. I also have an iMac and Macbook Pro, NEITHER of which has EVER experienced a single problem with updates over the last 6 years. That, given THIRTY years, MS cannot code a reliable update procedure is far beyond comprehension.

    Was this answer helpful?

    0 comments