Should MoUsoCoreWorker.exe preventing sleep be ignored?


  1. Posts : 2,189
    Windows 10 Pro 64-bit v22H2
       #1

    Should MoUsoCoreWorker.exe preventing sleep be ignored?


    I have seen several threads here complaining about this
    Code:
    powercfg /requests
    
    [PROCESS] \Device\HarddiskVolume6\Windows\System32\MoUsoCoreWorker.exe
    USO Worker
    I don't take that as something to get rid of but a warning that there is a problem with Windows updates

    I just got that and then went into Windows Update

    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_36_291.jpg

    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_36_523.jpg

    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_37_004.jpg

    All seemed OK but based on past experience I knew there was something wrong with Windows Updates
    I then restarted the Windows Update service

    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_40_071.jpg

    I then retried Windows Update again

    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_42_021.jpg
    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_42_192.jpg
    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_42_253.jpg
    Should MoUsoCoreWorker.exe preventing sleep be ignored?-2021_03_12_21_42_354.jpg

    That showed there actually was a problem with Windows Update.

    If we configured Windows so that MoUsoCoreWorker.exe no longer prevented sleep how are we to know when there is a problem with Windows Update?

    In other words shouldn't we take this more seriously and listen to what Windows is telling us instead of trying to hide it?
      My Computers


  2. Posts : 1,746
    Windows 10 Pro x64 22H2
       #2

    I wouldn't be surprised if there is a time limit on how often you can really manually check for updates, once update process is complete any subsequent checks should result in no-op.

    If there is indeed such a thing restarting the service would certainly reset that limit as well and would allow you force manual check, but that limit is just my assumption for which I believe it makes sense for a service such as Windows update for obvious reasons, and I think we can even prove that thesis...

    If we configured Windows so that MoUsoCoreWorker.exe no longer prevented sleep how are we to know when there is a problem with Windows Update?
    I'm not sure how you do this but if you want to track WU operation you can do so in event viewer in the following location:
    Application & Services logs -> Microsoft -> Windows -> WindowsUpdateClient

    Here go ahead and watch events by refreshing them, you keep checking for updates manually and you'll notice a new message each time telling you basically the same thing over and over again regardless whether something was downloaded/installed or not, I believe this is fair proof of a limit mentioned before.

    Why?
    Now go ahead and reboot service then check for updates again (manual check ofc.), you may notice the message didn't change, in my case it says that there was 1 update found while none was found, it is referring to 1 update that I installed before doing this test, so I'm fairly certain there is a limit, but could be ofc. wrong.

    Regarding you original concern, the powercfg entry seems to imply that computer must not go to sleep until WU completes it's job, if you can't find anything in event viewer (I can't because I don't have this problem) then you can test out the option in WU advanced settings that says:
    Restart this device as soon as possible...

    I have this option always turned off, so that may the reason why I don't have this issue, but you'll have to test it.
      My Computer


  3. Posts : 2,189
    Windows 10 Pro 64-bit v22H2
    Thread Starter
       #3

    The screenshots were from my laptop computer. I only investigated because my laptop hadn't gone to sleep since I booted it 6 hours before. Once I fixed the Windows Update the computer promptly went to asleep after the 15 minute timeout I had set.

    Now I noticed that my Desktop #2 had not gone to sleep all day. I checked and it had the same problem with MoUsoCoreWorker.exe preventing sleep. It also showed no updates available. Once I restarted the Windows Update service it found several updates. Once all the updates were installed the "MoUsoCoreWorker.exe" message went away and the computer was able to sleep again.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:24.
Find Us




Windows 10 Forums