KB5000802 CU Windows 10 v2004 build 19041.867 and v20H2 19042.867 Win Update

ashleyg · 11 Apr 2021

steve108 said:

Same. MS will probably just push out a fix and leave the KB the same.
https://www.catalog.update.microsoft...q=KB5000802%20

Am investigating the BSOD print problem further for a colleague. Initially we resolved the issue when trying to print by uninstalling that faulty CU KB5000802. (He is one of the unfortunate few who are printing to a large colour Kyocera printer).

From information discussed on this thread, I put windows updates on hold for 2-3 weeks waiting for a fix to be published. We re-enabled the updates just recently and KB5000802 got reinstalled again and apparently reintroduced the problem. When removing the KB5000802, the problem resolves ie. printing works again.

I am about to go visit him and load the latest fix - ie. cumulative update posted here being KB5001567.
I'd like to clarify first -
1. Do I need to have the print issue present on the system ie. KB5000802 installed before I update with KB5001567 or
2. Should I uninstall it and use the 'Hide or Show Windows Updates' tool to keep it from reinstalling before running windows update to find and apply KB5001567

Does this approach sound ok? Any other considerations?
Thanks.

(edited 13/4 to show the fix correctly as KB5001567)

sygnus21 · 12 Apr 2021

There have since been updates that supposedly fixed the printer issues.

That said, neither of my Epson printers were affected.

ashleyg · 12 Apr 2021

sygnus21 said:

There have since been updates that supposedly fixed the printer issues.

That said, neither of my Epson printers were affected.

Yes, the discussion took a turn about 3 weeks back and it has been quiet with no solid feedback from those who originally were in discussion.

Agree it seems to have been fixed and I think the answer is to apply that KB5001649 update, but i'm lost as to why that bad KB is still around after 3 weeks and where it fits in with the fix. Cheers

LaurieD227 · 12 Apr 2021

Just to add some data points:

I heard about the March Updates causing BSODs so I put mine on hold until today. I have 3 laptops - ProStar and Dell D5579 (as listed in my profile), plus a Dell D7386 13 inch that I use as a backup and/or travel machine and occasional test bed. All were running Version 2004, Build 19041.804.

I followed the same sequence of steps for each one and was successful, so I wanted to share key information in case it is of use.
1) Backed up all documents, did a Macrium Reflect system image for each machine yesterday, then did a System Restore point this morning.
2) Told Windows Update to 'resume updates', then watched it download and install them. All machines received the Malicious Software Removal Tool (KB890830) and the Cumulative Update (KB5000802). The two Dell machines also received the Microcode update (KB4589212) and the .NET preview (KB4601554). (NOTE: I didn't pick and choose which updates to apply, Windows Update did so on its own.)
3) Ran SFC Verify Only and DISM CheckHealth - no issues on any machine
4) Printed a test page from MS Office 2016 and 2019 on an HP 8630 multipurpose printer/fax/scanner - no issues. Did the same on a Brothers HL 2140 printer - no issues
5) Printed a page from the Internet with a big colorful image on it from all machines, on both printers - No issues. No blue screen, no messed up graphics.
6) All machines now show Version 2004, Build 19041.867.

So, looks like HP 8630 and Brothers HL 2140 printers are not part of the BSOD problem - at least so far.
Hope that's helpful to know.

ashleyg · 12 Apr 2021

@LaurieD227

That would appear to prove that KB5000802 is still floating around and it could be that your printers were never affected.

Does your windows update history show if both CU's are installed on your system?
Cumulative Update KB5000802 and the subsequent Update KB5001567. Thanks

jbcarreon123 · 12 Apr 2021

KB5000802 is a optional update.

KB5000802 CU Windows 10 v2004 build 19041.867 and v20H2 19042.867-image.png

LaurieD227 · 13 Apr 2021

@ashleyg

Nope, KB5001567 was not installed (I watched to see if Windows Update would add it or offer it), so I think you're right - my HP and Brothers drivers escaped the BSOD issue.

And yes, KB5000802 IS still floating around, because, when I paused updates in March, the March 9th updates had not yet downloaded to my machines. Then when I resumed updates yesterday all 3 machines downloaded KB5000802 at that time and I installed it with bated breath.

The reason I provided my information was, when people wonder "might my printer be affected," they can see names of printers that are okay, and if they have a similar one it might raise their comfort level a bit if they need to proceed with the updates.

ashleyg · 14 Apr 2021

Thanks everyone for your input with this.

I went on-site yesterday to investigate further and somehow the issue has resolved in the meantime

.

Updates were still paused (via the settings option)
KB5000802 was installed
KB5001567 was not installed (nor waiting to be)
Test printing to the Kyocera worked(!)

Not sure how this resolved, maybe a targeted fix was sent through from MS or just gremlins .

I am unable to explain what happened here but I'm taking it as a win and moving on - life's too short

steve108 · 14 Apr 2021

ashleyg said:

Thanks everyone for your input with this.

I went on-site yesterday to investigate further and somehow the issue has resolved in the meantime

.

Updates were still paused (via the settings option)
KB5000802 was installed
KB5001567 was not installed (nor waiting to be)
Test printing to the Kyocera worked(!)

Not sure how this resolved, maybe a targeted fix was sent through from MS or just gremlins .

I am unable to explain what happened here but I'm taking it as a win and moving on - life's too short

Ready for the April CU that came out yesterday?

......... KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928

ashleyg · 14 Apr 2021

steve108 said:

Ready for the April CU that came out yesterday?

......... KB5001330 CU Windows 10 v2004 build 19041.928 and v20H2 19042.928

Yes indeed.. it was there waiting for me so I let it install wile I was feeling lucky.
Installed without problem and printing still worked.

Now on v20H2 b19042.928