New
#220
KB5000802 CU Windows 10 v2004 build 19041.867 and v20H2 19042.867 Win Update
-
-
New #221
KB5001567 would hopefully be the anticipated fix for the printer issues, and has also just appeared in the Update Catalog, issue date 15/03/2021.
Release notes have (literally) just appeared...
March 15, 2021—KB5001567 (OS Builds 19041.868 and 19042.868) Out-of-band
Highlights
- Updates an issue that might cause a blue screen when you attempt to print to certain printers using some apps.
-
New #222
This was a wild update. I tried it on my 11 year-old Lenovo Thinkpad. I had the standard Microsoft Defender update, the Malicious Software Removal Tool, the Adobe Flash Removal Update, the Microcode Update (KB4589212, which for my old system there was no update), the old KB4023057 (which I keep getting several times a year), and the Servicing Stack Update (10.19041.860). The infamous KB5000802 also appeared and was waiting application after the others. The others appeared to apply ok but I did not notice any % done as it was working. It eventually restarted and came back with KB4589212 waiting for restart and KB5000802 starting to download. The download would not complete. I retried several times and got the same result. Finally I decided to restart the system. KB5000802 finally downloaded, installed, restarted, and came back fine. Apparently I had to do the restart after applying the microcode update before it would touch the cumulative update. Ever since v2004, when certain multiple updates are available at the same time (especially .NET and regular cumulative updates), it installs one and displays the "RESTART" button while the other update is still installing. This is really confusing. In this case why did it not restart after applying the microcode update before starting the download of the cumulative update if one was required to finish before processing the first? Something is really amiss with Windows Updates these days.
JohnD
-
New #223
Hopefully this fix solves my sleep issue.
Since KB4601382 (.844) I've had sleep issues. I did have it fixed per my post here; but then KB5000802 (.867) brought the sleep issue back, though the "fix" for 844 is still there
Hopefully that out of band fix (KB5001567) helps fix the issue.
Anyway, anyone else with sleep issues after the last couple of updates?
-
New #224
If you have sleep issues open command prompt or powershell with admin rights.
type powercfg /requests
If you see MoUSOCoreWorker.exe that is what is keeping you awake.
type
net stop wuauserv
It might end in a fail. Regardless restart computer. Check for updates.
You will likely see updates being processed.
I went a step further on one machine. After my updates were in I ran Shawn's Windows Update reset.
-
New #225
Thanks Ken,
I've done part of that per the link in my post above. I just didn't do the "net stop wuauserv", but instead unticked "Allow this device to wake to wake computer" under mouse properties in Device Manager. That worked until update .867, and now is working again after updating to KB5001567 (.868) so
PC went to sleep and stayed that way for the first time since the issue reappeared again. Fingers crossed XX
Thanks
-
New #226
Without the net stop the USCoWorker just survives the restarts.
I've had this issue on multiple computers, multiple clients.
Somebody better have a sit down with the update folks.
-
New #227
For me, simply unticking "Allow this device to wake to wake computer" worked without issue until I installed KB5000802. Once I installed KB5001567, the issue went away again. Weird
And yeah, maybe someone should have a sit down with the update folks. That said, I wonder how prevalent the issue is?
-
New #228
I have four computers at home with issue.
Three clients. That I've talked to. A lot don't use sleep or call me until computer is on it knees.
I started randomly checking for power requests
-
-
New #229
Thanks, glad to know I'm not the only one who's had this issue. BTW after my post above went out and come home and PC was sleeping like a baby so...
Quote
Related Discussions
