KB5001649 CU Windows 10 v2004 build 19041.870 and v20H2 19042.870

Bree · 19 Mar 2021

y2jman said:

19042.868 if i wait don't maually update this will be avaiable again though windows update 1 day next week right?

First, do you actually need it? It only contains one fix that isn't already in your .868: "Updates an issue that fails to print the graphical content in a document after installing the March 9, 2021 update." If you don't have that printing issue, then you don't need it.

If you do need it, it will probably be offered through windows update again shortly, and in any case will be included in the Patch Tuesday update on April 13th.

If you need it urgently, you can download the standalone msu installer from the links in post #1. That one will install, it's just the delivery by WU that's broken.
:

Ghot · 19 Mar 2021

y2jman said:

yeah I don't have a printer so just wait ok then

You'll be fine.

buglocker2 · 19 Mar 2021

AllenChicago said:

The Standalone link worked. Was stuck at about 10% installed for 10 minutes, then suddenly completed. Asking for a computer restart now.

The same here.

i486 · 19 Mar 2021

pietcorus2 said:

Unless you have severe printer-problems , better wait for next CU ............!

Things dont get better by udating each update again.........

That turkey is in the oven, should be ready in about three weeks.

y2jman · 19 Mar 2021

so apparently my windows update install kb4589212 I thought it would had been this but wasn't

I assumed nobody do have that install eh

AllenChicago · 19 Mar 2021

pietcorus2 said:

" Unexpected results when printing from some apps or to some printers
Issues might include missing or solid color graphics, misalignment/formatting issues, or printing of blank pages/labels. "
YEEEES ! This update fixed my Canon MP520 !!

Fixed the print quality problems I was having with my Brother MFC-875 Printer-Scanner-Copier too. I thought the ink cartridges were plugged up. Now I have an extra set.

Strange for Windows to have printing problems. Printing is a basic (supposedly) time-tested Windows task.

steve108 · 19 Mar 2021

AllenChicago said:

.....

Strange for Windows to have printing problems. Printing is a basic (supposedly) time-tested Windows task.

I was wondering the same thing. Would love to hear the inside scoop/explanation on how they managed to break printing.

jimbo45 · 20 Mar 2021

Hi there
This build has totally hosed up Networking (About par for the course with Windows !!!!) - Endless loop / hang if I try and browse Network with file explorer -- needs re-boot. Even attempting to cancel the task won't work because explorer is so ingrained into Windows kernel stuff.

Image shows hang -- you can see from the weird task icon for file explorer (red squiggly line to taskbar)

KB5001649 CU Windows 10 v2004 build 19041.870 and v20H2 19042.870-nwf.png

I've given this build 3 boots -- FAIL !!!! so I've also given it a "Physical boot" -- I.E to the bin.

Printing problems surprise me - that was one of the first tasks ever required by computers from early days so unless people have really weird hardware that should be bog standard in almost every OS - can't say I've had printing issues.

Networking though has always been hit and miss on Windows -- even way back to Windows for Workgroups 3.11 when the networking available was built on MS DOS - I think was it called DOS Novell LAN or something similar -- and as for that totally incomprehensible WINDOWS NT system that came out back some years ago Windows Networking seems to have been on a backward journey ever since then - except for 2 OS'es where I never had problems - Windows 2003 Server and Windows 2K19 server so why not use Networking from those OS'es as they obviously work.

I'll wait until the next CU . However also playing with other releases so plenty more to test.

Cheers
jimbo

dencal · 20 Mar 2021

Did a System Update for me.

Zardoc · 20 Mar 2021

jimbo45 said:

Hi there
This build has totally hosed up Networking (About par for the course with Windows !!!!)
Networking though has always been hit and miss on Windows -- even way back to Windows for Workgroups 3.11 when the networking available was built on MS DOS - I think was it called DOS Novell LAN or something similar -- and as for that totally incomprehensible WINDOWS NT system that came out back some years ago Windows Networking seems to have been on a backward journey ever since then - except for 2 OS'es where I never had problems - Windows 2003 Server and Windows 2K19 server so why not use Networking from those OS'es as they obviously work.
I'll wait until the next CU . However also playing with other releases so plenty more to test.
Cheers
jimbo

Hi Jimbo,
Totally agree with you on Networking issues. I can't even get my NAS to transfer faster than 30MBs while the rest transfers a 100-120MBs.

MS got rid of Homegroup that was a wild waste of time. I think networking needs an overhaul also.