20H2 broke my Windows 10 sleep mode

Topic

New Reply

[JohnW]

Was running Win 10 Pro 2004, and decided to upgrade. I took an image yesterday, and then set target to 20H2, and allowed WU to install the update.

Everything seems to have went very well, except that I noticed my PC never idled to sleep last night. That’s usually never happened, and if so, there is an application preventing it. That is normally easily resolved, and the culprit can be identified by issuing this command from an Administrator command prompt window: “powercfg /requests”.

However in this case the results are:

C:\Windows\system32>powercfg /requests
DISPLAY:
None.

SYSTEM:
None.

AWAYMODE:
None.

EXECUTION:
[PROCESS] \Device\HarddiskVolume4\Windows\System32\MoUsoCoreWorker.exe
USO Worker

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

Google tells me that many other folks have been seeing this issue since last year, but nobody has a definitive fix for it. Lots of ideas, but no luck. MoUsoCoreWorker is a part of Windows update service, so disabling that is not the answer.

I have tried the Powercfg “override” command, which as no effect in this case. I have run the troubleshooters for Windows Update and Power. Have rebooted several times, and stopped and restarted Windows update. And “SFC /scannow” is clean. No updates waiting either.

I can manually invoke sleep mode, so sleep itself is not broken. It is just this task preventing idle to sleep.

I’m about at my wits end and considering a rollback to yesterday’s image, but would rather not. Has anybody here seen this?

Thanks for any help!

Windows 10 Pro 22H2

• This topic was modified 4 years, 1 month ago by JohnW.

Reply | Quote

Replies

Is Fast-start disabled after the upgrade?
Try running powercfg -lastwake to establish what prevented sleep mode being entered. Connected devices can also be a problem IIRC, worth checking out.
Could also be powersaving from ethernet/wifi adapters in networking, untick them.

Windows - commercial by definition and now function...

Reply | Quote

Thanks for the feedback!

I never use fast start and hibernate is disabled.

“powercfg -lastwake” shows the event from last using my USB keyboard to wake from sleep. I can go to “Power > Sleep” and it sleeps just fine, and stays asleep. Then hitting a key wakes it up.

Never use powersaving in networking.

“powercfg /requests” clearly show Windows update is interfering.

C:\Windows\system32>powercfg /requests
DISPLAY:
None.

SYSTEM:
None.

AWAYMODE:
None.

EXECUTION:
[PROCESS] \Device\HarddiskVolume4\Windows\System32\MoUsoCoreWorker.exe
USO Worker

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

C:\Windows\system32>

Windows 10 Pro 22H2

Reply | Quote

ok, a workaround may be to kill WU when finished using the device.

::Stop the Windows Update service
net stop wuauserv
exit

C&P into notepad and save as a .bat file, create a shortcut on the desktop and run as admin. just restarts..not much use

Windows - commercial by definition and now function...

Reply | Quote

Another weird thing that I have noticed, is that sometimes the USO Worker entry in Powercfg goes away after a reboot, and the system can sleep.

But then USO Worker returns after the next sleep session. So Windows will not idle to sleep when the USO worker is an active request.

Bottom line is that sleep was working perfect before the 20H2 update, and none of my settings were changed by the update.

Windows 10 Pro 22H2

Reply | Quote

Ran the .bat file.

Rebooted. Same status.

Windows 10 Pro 22H2

Reply | Quote

Perhaps MS don’t want your device to sleep so they can extract-behind-your-back?
Try this: https://appuals.com/mouso-core-worker-process-mousocoreworker-exe-constantly-wakes-computer-from-sleep/

Reply | Quote

Well, it’s not just me. If you take a look around via Google search, lots of folks have been noticing this issue.

So I’m done with 20H2. Wish I could say it’s been fun, but I’m not wasting any more time on Microsoft’s bugs. They need to fix this.

Back to Win 10 2004 we go, via Macrium image from yesterday! Engage the flux capacitor, professor!

Windows 10 Pro 22H2

Reply | Quote

Whoa! Hold the phone…

I made a trip to the supermarket, was gone about an hour, and when I returned I was gathering my gear for the restore, like my bootable flash recovery drive and my backup image drive.

Then I happened to notice that my PC was actually sleeping! Woke it up, and now saw no sign of the USO Worker in Powercfg!

After several cycles of letting it fall asleep, waking it, and then rebooting, all appears to be well now.

The only last thing  that I had done (no idea if this had anything to do with it working again – as correlation doesn’t necessarily equal causation), is to allow Windows update to install some outstanding drivers. It downloaded and installed some Intel, HP Printer, and NVIDIA drivers that were apparently queued up, but had been blocked by my settings. But the USO Worker was still blocking sleep immediately after the driver install. So DOH! Have no idea now.

Will let this rig soak for another 24 hrs, and if still good, we’ll let 20H2 live on…

Sorry to blab on, but Windows sleep is a showstopper feature for me! I have several jobs that run at night, wake the computer up, and then it goes back to sleep when they are finished. I have no desire to run up my power bill with my PC doing nothing!

I have done battles with Windows sleep back in the WinXP and Win 7 days, and that has been one thing I have to say Win 10 has been mostly free of problems for me. Until 20H2 that is!

Windows 10 Pro 22H2

Reply | Quote

So far, so good. Except for the head fake regarding Windows sleep mode, 20H2 appears to be the most problem free Win 10 update yet!

Windows 10 Pro 22H2

1 user thanked author for this post.

LHiggins

Reply | Quote

I see you solved the issue. If it happens again there’s a solution. Windows update process is stuck and manual stop, start and restart will let you continue the update process (in the regular way through windows update). Your computer should go to sleep now.

Reply | Quote

At some point, after am update, I noticed some of my Win 10 PCs were not dimming the screen or going into sleep after the specified time.

Turns out it was the Lock Screen slideshow. If it is set to Slideshow, it turns off the screen dimming and sleep function.

If you go into Settings, Power and Sleep (not the control panel Power app) with the Lock Screen slideshow set, there is a notice at the top of the page letting you know that the screen and sleep settings are disabled, but the boxes with the values are not greyed out, so you really need to pay attention to notice that “feature”.

Not sure when this “feature” showed up, but I could have sworn it was working with the Lock Screen slideshow at some point in the past. I suspect it happened when I updated to Win 10 21H2 this past winter.

Reply | Quote

Steve wrote:

Turns out it was the Lock Screen slideshow. If it is set to Slideshow, it turns off the screen dimming and sleep function.

I have set slideshow on my Windows 10 (currently 21H2) and the display turs off after the set time. I don’t use sleep.

Reply | Quote

If you are using Sleep mode, and it’s not going to sleep, a good item to always check is with a Command Prompt in Administrator mode, and type “powercfg /requests”.

If you get these results, you should be all clear to sleep. Otherwise a process may be listed here that is preventing sleep mode, and you will need to investigate further.

C:\WINDOWS\system32>powercfg /requests
DISPLAY:
None.

SYSTEM:
None.

AWAYMODE:
None.

EXECUTION:
None.

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

Windows 10 Pro 22H2

1 user thanked author for this post.

windbg

Reply | Quote