Desktop failing to sleep

Windows 10 Pro, v20H2, build 19042.804

Well I'm back here again. This has been an ongoing problem where my recently installed Win10 & fully updated Win10 desktop fails to go into sleep mode unless I force it manually. Have had a history of problems with Windows 10 going back years on different computers doing this. Have checked the settings in Control Panel incl advanced power settings. As I said there is history here so I know what I'm doing.



When I run the command below MoUsoCoreWorker.exe is the culprit. I have previously disabled the Update Orchestrator (UOS) Service as this is the service of the MoUSO Core Worker Process. This solution worked until Win10 ran an update a few days ago and now everything has been reset including obviously this service.



Disabling the Update Orchestrator (UOS) Service is not a long term solution and obviously Microsoft seems to be unable to get Win10 sleep to work reliably. Does anyone have any fixes? Or is this an area of Win10 that's broken?





Microsoft Windows [Version 10.0.19042.804]

(c) 2020 Microsoft Corporation. All rights reserved.



C:\Windows\system32>powercfg -requests

DISPLAY:

None.



SYSTEM:

None.



AWAYMODE:

None.



EXECUTION:

[PROCESS] \Device\HarddiskVolume1\Windows\System32\MoUsoCoreWorker.exe

USO Worker



PERFBOOST:

None.



ACTIVELOCKSCREEN:

None.



C:\Windows\system32>

[PROCESS] \Device\HarddiskVolume1\Windows\System32\MoUsoCoreWorker.exe

I see that once in a while. In fact I just saw it this morning.

That indicates that Windows Update is preventing sleep.

Go to Setting > Update & Security
Click on Check for updates
Wait for it to find and install updates

If any updates fail you can try to restart the Windows Update service

• Right click on This PC
• Select Manage
• Select Services and Applications
• Select Services
• Scroll down to Windows Update service
• Right-click on Windows Update service and select Restart
  
• When it finishes exit Computer Management
  

Go back to Setting > Update & Security
Click on Check for updates
Wait for it to find and install updates

I know that this is annoying but restarting the Windows Update service and doing a manual checking for updates has always cleared this up for me.

I do appreciate the replies but I haven't had time to try these on my PC yet and when I do I'll update. thanks again

Try3 said:

Try mngerhold's solution in post #9 of another thread

It worked for me.

Denis

For me MoUsoCoreWorker.exe preventing sleep indicated a problem with Windows Update. If you override that you won't know about the problem. Isn't it better just to fix the Windows Update problem? If you do that sleep will go back to normal.

When will MS resolve this once and for all. It's all very well for those of us who sub to these forums and tinker with computers but for the vast majority of people who've never even seen a command line this isn't good enough.

MisterEd said:

For me MoUsoCoreWorker.exe preventing sleep indicated a problem with Windows Update. If you override that you won't know about the problem. Isn't it better just to fix the Windows Update problem? If you do that sleep will go back to normal.

I'm with you on this and won't throw a band-aid over the problem like they keep suggesting to do here "because it solves the problem" - but I feel like we're in the minority club here. My analogy is chop the arm off because it hurts rather then try to get to the root cause of why it hurts/MoUsoCoreWorker.exe is running and preventing sleep. I have multiple PCs where I haven't had to resort to chopping off the arm that sleep just fine - laptops and desktops, young and old.

One old PC (originally came with Vista - Core 2 Duo - 4GB RAM - now runs Windows 10 2004) would not sleep yesterday for this very MoUsoCoreWorker.exe reason. I rebooted it, checked for Windows Updates manually, problem solved - MoUsoCoreWorker.exe finished doing its thing and the PC went to sleep without forcing any overrides.

To each his own, I suppose, but overrides remind of suggestions to do a clean install when there's a problem without first trying to address the underlying issue .

steve108 said:

I'm with you on this and won't throw a band-aid over the problem like they keep suggesting to do here "because it solves the problem" - but I feel like we're in the minority club here. My analogy is chop the arm off because it hurts rather then try to get to the root cause of why it hurts/MoUsoCoreWorker.exe is running and preventing sleep. I have multiple PCs where I haven't had to resort to chopping off the arm that sleep just fine - laptops and desktops, young and old.

One old PC (originally came with Vista - Core 2 Duo - 4GB RAM - now runs Windows 10 2004) would not sleep yesterday for this very MoUsoCoreWorker.exe reason. I rebooted it, checked for Windows Updates manually, problem solved - MoUsoCoreWorker.exe finished doing its thing and the PC went to sleep without forcing any overrides.

To each his own, I suppose, but overrides remind of suggestions to do a clean install when there's a problem without first trying to address the underlying issue .

I imagine plenty of people would have tried what you suggested i.e. manually run Win Update and reboot only for the problem to keep recurring. I think for a lot of folk like me who are running 20 or so different programs and don't want to have to reboot apart from maybe once a week.

I still believe that this issue should not be arising on such a mature OS regardless.

Gusgf said:

I imagine plenty of people would have tried what you suggested i.e. manually run Win Update and reboot only for the problem to keep recurring. I think for a lot of folk like me who are running 20 or so different programs and don't want to have to reboot apart from maybe once a week.

I still believe that this issue should not be arising on such a mature OS regardless.

Oh, I agree, I don't reboot every day and avoid reboots, clean installs, etc - that's why I use sleep - the reboot was a one-off weird exception ......... but y'all do what's best for you. This particular PC had not been used/updated/rebooted in a while, so maybe that was a factor :