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

Page 2 of 9 FirstFirst 1234 ... LastLast

  1. Posts : 21,421
    19044.1586 - 21H2 Pro x64

    I wouldn't recommend the brute force disable of MoUsoCoreWorker.exe at this point. Sure, it will work, but I've never had to resort to that and multiple PCs sleep just fine. Arm hurts, so let's amputate it.
      My Computer

  2. Posts : 28
    Win10 Pro 64Bit
    Thread Starter

    steve108 said:
    I did have a similar scare where my PC wouldn't sleep for the same reason, but it turned out that it wasn't finished installing a Dot NET update. I think I just left it on for a while, then it finished, powercfg output was clear, and sleep resumed working again.
    Actually this seems to bring a memory from the deep ... I believe I recall having an install issue to the .DOT update back at the start of February. At the time, I managed to get the install finished and like you the problem "went away" and everything seemed fine, only to return in the last few days.
      My Computer

  3. Posts : 21,421
    19044.1586 - 21H2 Pro x64

    Interesting. There was a Dot NET update last Tuesday on my PC. I wonder if you have it too or if it's causing this issue. I suggest you try the Windows Update Reset tutorial.
      My Computer

  4. Posts : 28
    Win10 Pro 64Bit
    Thread Starter

    I rebooted my PC to do a full backup ... I needed to one anyway & it gives me an option to restore my PC if something goes wrong.

    Upon reboot, waited about 2-3 mins and then ran Powercfg /requests and:

    [PROCESS] \Device\HarddiskVolume3\Windows\System32\MoUsoCoreWorker.exe
    USO Worker

    Went WU and did a manual scan ... nothing found.

    Running these cmds now:

    sfc /scannow
    dism /online /Cleanup-Image /ScanHealth

    Will update this post shortly with the results...

    1st Up SFC /scannow:

    PS C:\Windows\system32> sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    The log itself is long but there's:

    2021-02-19 16:56:11, Info                  CSI    000001fc [SR] Repairing 1 components
    2021-02-19 16:56:11, Info                  CSI    000001fd [SR] Beginning Verify and Repair transaction
    2021-02-19 16:56:12, Info                  CSI    000001fe [SR] Repairing file \??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\\OneDrive.lnk from store
    2021-02-19 16:56:12, Info                  CSI    000001ff CSIPERF - FilePI Queue 140ms
    2021-02-19 16:56:12, Info                  CSI    00000200 [SR] Repair complete
    I also notice that there's a cab file in the C:\Windows\Logs\CBS directory:
    Date of: Wed, 10, Feb 2021, 2:45pm
    Size: 63mb

    No idea about this at all. Will check it later, too big for Notepad. Have to use Notepad+.

    The log itself has a date of the 9/Feb/2021 and *seems* to be about the monthly update.

    Moving onto the DISM cmd ... the last time I ran this cmd was under Win8.1 & I think it took ages but I then did a clean install of Win10 back in October 2020. Back soon.

    Win10 must be a bit faster:

    PS C:\Windows\system32> dism /online /Cleanup-Image /ScanHealth
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.746
    Image Version: 10.0.19042.804
    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.
    Last edited by BazzaG; 19 Feb 2021 at 01:17.
      My Computer

  5. Posts : 21,421
    19044.1586 - 21H2 Pro x64

    I'm hoping there's a stuck update that the reset will clear and yes, making a backup is always prudent.
      My Computer

  6. Posts : 21,421
    19044.1586 - 21H2 Pro x64

    Check your Windows Update history for February CU KB4601319 installation and a .NET CU update around the same day within this past week.
      My Computer

  7. Posts : 28
    Win10 Pro 64Bit
    Thread Starter

    WU History has:

    2021-02 Cumulative update for Windows 20H2 KB4601319 successfully installed on 10/Feb/2021
    2021-02 Cumulative update for Net Framework 3.5 & 4.8 for Windows 10 KB4601050 successfully installed on 10/Feb2021

    Given that I'm in Australia that would be 9/Feb2021 US.
      My Computer

  8. Posts : 21,421
    19044.1586 - 21H2 Pro x64

    Okay, that looks good.
      My Computer

  9. Posts : 17,015
    Windows 10 Home x64 Version 22H2 Build 19045.4170

    BazzaG said:
    ... My problem though is MoUsoCoreWorker.exe prevents my PC from going to sleep ...

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

      My Computer

  10. Posts : 21,421
    19044.1586 - 21H2 Pro x64

    Try3 said:

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

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


  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 20:49.
Find Us

Windows 10 Forums