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

Page 3 of 9 FirstFirst 12345 ... LastLast

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

    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.
      My Computer


  2. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #22

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


  3. Posts : 16,933
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #23

    steve108 said:
    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.
    steve108 said:
    Chop the arm off because it hurts is not a good solution, Denis.
    steve108 said:
    Chop the arm off because it hurts is not a good solution, Denis.
    Bazza,

    I am not suggesting that you chop your arm off. I am suggesting that you solve your reported problem.
    BazzaG said:
    ... My problem though is MoUsoCoreWorker.exe prevents my PC from going to sleep ...
    Try3 said:
    You seem to have overlooked that posted solution. It directly addresses your reported problem and it works.
    Denis
      My Computer


  4. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #24

    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?
      My Computer


  5. Posts : 28
    Win10 Pro 64Bit
    Thread Starter
       #25

    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.
      My Computer


  6. Posts : 1,203
    11 Home
       #26

    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
      My Computers


  7. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #27

    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.
      My Computer


  8. Posts : 28
    Win10 Pro 64Bit
    Thread Starter
       #28

    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.
      My Computer


  9. Posts : 21,421
    19044.1586 - 21H2 Pro x64
       #29

    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.
      My Computer


  10. Posts : 28
    Win10 Pro 64Bit
    Thread Starter
       #30

    It's back.

    I had been doing ad-hoc powercfg /requests over the last few days and great nothing listed.

    Powered on the PC this morning, then I had to leave to help my elderly father do some shopping, when I came back the PC was still awake.

    powercfg /requests now has MoUsoCoreWorker.exe listed.

    WU has:

    2021-02 Cumulative Update Preview for Windows 10 Version 20H2 for x64-based Systems (KB4601382)

    listed as an OPTIONAL update and nothing else.

    This is ridiculous ...




    Update...

    I decided to reboot my PC to see if that would remove MoUsoCoreWorker.exe. After entering my PIN code, I went to make a cuppa. Upon my return I had a notification in bottom right-hand corner:

    "Your device will restart to update outside of active hours" etc. etc.

    Opening WU, we now have:

    2021-02 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10, version 20H2 for x64 (KB4601554)
    Status: Pending Restart

    This was NOT listed before I rebooted my PC. Given this is a *PREVIEW* release, I did NOT ask Windows to install it or for that matter any other update.

    So it's DAMN .NET AGAIN ...

    Seems that I have 2 choices:

    1. Reset Windows Update & loose my WU history (which for me only goes back to November 2020), or
    2. Change WU to how it worked until Win8.1, ie. tell me, but let me choose when.

    #2 is my MUCH preferred option and something that I've been meaning to do ... will just have to find the thread here as to how to do so.

    Anyway, time to reboot my PC ....




    Ok straight after rebooting my PC, powercfg /requests now has:

    PS C:\Windows\system32> powercfg /requests

    DISPLAY: None.

    SYSTEM:
    [SERVICE] \Device\HarddiskVolume3\Windows\System32\svchost.exe (Schedule)
    Windows will execute '\Microsoft\Windows\.NET Framework\.NET Framework NGEN v4.0.30319 64 Critical' scheduled task that requested waking the computer.
    [SERVICE] \Device\HarddiskVolume3\Windows\System32\svchost.exe (Schedule)
    Windows will execute '\Microsoft\Windows\.NET Framework\.NET Framework NGEN v4.0.30319 Critical' scheduled task that requested waking the computer.

    AWAYMODE: None.

    EXECUTION: None.

    PERFBOOST:
    [DRIVER] Legacy Kernel Caller
    Power Manager

    ACTIVELOCKSCREEN: None.

    A quick Google search returns some items dating back to 2013!!!!

    A 2nd powercfg /requests & now the above entries are gone.

    -----

    Looking at this, I *think* I can understand what's happening & what's MS is trying to do. If this normal monthly update then OK; sort of, but this time it was PREVIEW update that shouldn't have installed automagically.

    A problem here is that Windows does NOT tell us that it's installing an update BEFORE it does so, nor did it AFTER it partially installed the update. It took a reboot to announce that ANOTHER reboot was required to finish the install.
    Last edited by BazzaG; 25 Feb 2021 at 20:33.
      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 02:35.
Find Us




Windows 10 Forums