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

Try3 said:

Bazza,

You seem to have overlooked that posted solution. It directly addresses your reported problem and it works.

Denis

Chop the arm off because it hurts is not a good solution, Denis.

BazzaG, run sfc again just to make sure the output is clean as I expect it will be.

Try3 said:

Bazza,

I am not suggesting that you chop your arm off. I am suggesting that you solve your reported problem.




Denis

Well let the OP decide. Let's just hack stuff up and call it a solution?

Try3 said:

Bazza,
You seem to have overlooked that posted solution. It directly addresses your reported problem and it works.

Haven't overlooked it, just trying other possible fixes 1st. Personally I don't consider the powercfg /requestsoverride a "fix" but rather a work around. Given that I'm not a Windows guru I did have some concern that doing so might cause some other problem. I accept the possibility of such might be small, even negligible.

If this is a common problem that's been around for a while then it's about time MS got off their backside and fixed it.

- - - Updated - - -

steve108 said:

BazzaG, run sfc again just to make sure the output is clean as I expect it will be.

Yep runs nice & clean now:
Windows Resource Protection did not find any integrity violations.

steve108 said:

Arm hurts, so let's amputate it.

From the movie, Lawrence of Arabia. "The trick, William Potter, is not minding that it hurts".
Is there a permanent fix yet for MoUsoCoreWorker.exe preventing Windows 10 sleep? : Windows10
Putting this code in a batchfile should work:

Code:

taskkill /im MoUsoCoreWorker.exe /f
powercfg -h off
rundll32.exe powrprof.dll,SetSuspendState 0,1,0
powercfg -h on

- - - Updated - - -

Or if you have disabled hibernate, then this:

Code:

taskkill /im MoUsoCoreWorker.exe /f
rundll32.exe powrprof.dll,SetSuspendState 0,1,0

BazzaG said:

Haven't overlooked it, just trying other possible fixes 1st. Personally I don't consider the powercfg /requestsoverride a "fix" but rather a work around. Given that I'm not a Windows guru I did have some concern that doing so might cause some other problem. I accept the possibility of such might be small, even negligible.

If this is a common problem that's been around for a while then it's about time MS got off their backside and fixed it.

- - - Updated - - -



Yep runs nice & clean now:
Windows Resource Protection did not find any integrity violations.

BazzaG,
I've got at least half dozen PCs that sleep WITHOUT having to do any hackery, scotch tape, or bandaids fixes to them. Don't be fooled by the "Guru" labels. Like you, I'd like to get to the root cause of why MoUsoCoreWorker isn't letting your PC sleep rather than just forcing it to be ignored by the powercfg override proposal.

Let me know when you try the Windows Update Reset please.

It was time for the evening meal and some TV news & streaming.

I haven't done anything beyond what I mentioned above, but I just ran Powercfg /requests and MoUsoCoreWorker.exe is no longer listed.

We'll see what happens but if this continues to be a problem I suspect I will need to follow reset WU Tutorial. For me, the MoUsoCoreWorker issue only started in February, prior to that I didn't have any sleep or wake problems and hadn't even heard of MoUsoCoreWorker.exe!!!

I also see that another thread has been opened on this issue. It seems to me that there's a bug in Win10 & MS needs to fix it.

Anyway, thanks to all.

Thanks for the update. Let us know stays this way or not. Feel free to report your experience to M$. You will find that others experience the same issue, but the numbers seem relatively small.