How to I stop MoUsoCoreWorker.exe from running or get it to run & end?

Lord Method Man said:

Pausing updates doesn't work and neither does requestsoverride.

Pity I was about to try these options....

steve108 said:

After the PC has been awake for an hour or so, "powercfg /requests" eventually stops outputting that MoUsoCoreWorker will prevent sleep. I guess Microsoft changed something.

That's exactly what I'm seeing but it's certainly longer than an hour. It's at least 2 hours but I think it's more like 4 hours & then it disappears.

Used mngerhold's solution back in March. I am on version 21H1 now and the override request is still in tact and I have never noticed any issues from doing this. If M$ ever resolves the issue then I'll remove the override request.

BazzaG said:

It's at least 2 hours but I think it's more like 4 hours & then it disappears.

FYI ... MoUsoCoreWorker.exe disappeared from the powercfg list approx. 2 hours after I switched the PC on this morning (local time).

Regarding the requestsoverride option ... I'll look into that shortly.

BazzaG said:

FYI ... MoUsoCoreWorker.exe disappeared from the powercfg list approx. 2 hours after I switched the PC on this morning (local time).

Regarding the requestsoverride option ... I'll look into that shortly.

Has your PC stopped sleeping when you expect it to then?

BazzaG said:

I suspect MoUsoCoreWorker.exe is added when Windows does a scan for updates but I'm not 100% certain of that.

I just ran powercfg /requests when WUMT was checking for updates, and nothing was added.

Code:

PS C:\Windows\system32> powercfg /requests
DISPLAY:
None.

SYSTEM:
None.

AWAYMODE:
None.

EXECUTION:
None.

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

I have never run powercfg /requestsoverride

steve108 said:

Has your PC stopped sleeping when you expect it to then?

That depends...

When MoUsoCoreWorker.exe is NOT running my PC sleeps as it should.

I find that MoUsoCoreWorker.exe gets started once a day, generally after my PC has either been switched off or has been put to sleep overnight.

In todays case, MoUsoCoreWorker.exe didn't bother me at all because I was continually using my PC for more than 2 hours after I switched it on.

The behaviour of MoUsoCoreWorker.exe is a LOT different today compared to its behaviour back when I opened this thread a few months ago. Today, its much less a PITA as it was back then.

- - - Updated - - -

Matthew Wai said:

I just ran powercfg /requests when WUMT was checking for updates, and nothing was added.

I think it has more to do with whether or not there are any outstanding updates.

But as I said above, the behaviour of MoUsoCoreWorker.exe has changed a lot over the last few months.

BazzaG said:

I think it has more to do with whether or not there are any outstanding updates.

But as I said above, the behaviour of MoUsoCoreWorker.exe has changed a lot over the last few months.

Have you hidden the outstanding updates, if any?
MoUsoCoreWorker.exe has never caused a problem at my end since 20H2 was clean installed last year.
I don't even notice the existence of it. I have hidden a lot of outstanding updates.

Matthew Wai said:

Have you hidden the outstanding updates, if any?

Nope.

Matthew Wai said:

MoUsoCoreWorker.exe has never caused a problem at my end since 20H2 was clean installed last year.

I did a clean install of Win10 around October last year.