Update: Microsoft has released out-of-band non-security updates to address the Windows 10 printing crash issue.
The Windows 10 KB5000802 and KB5000808 cumulative updates released yesterday are causing Blue Screen of Death crashes when printing to network printers.
Yesterday, Microsoft released the Windows 10 KB5000802 and KB5000808 cumulative updates as part of the March 2021 Patch Tuesday.
Since then, there has been a constant stream of complaints that printing is causing Windows 10 to crash with an "APC_INDEX_MISMATCH for win32kfull.sys" blue screen of death crash.
According to posts by system administrators on Reddit [1, 2], the Windows 10 crashes began immediately after installing yesterday's KB5000802 and KB5000808 updates and attempting to print.
"Hey Jen, several folks over in r/sysadmin, myself included, are seeing a BSOD post-update (on at least Win10 20H2 so far) when sending print jobs to any Windows Server printer share using a type 3 Kyocera KX driver. (i.e., type 4 KX driver and other generic type 3/4 drivers don't exhibit the issue)," one Reddit user posted.
"KB5000802 broke all Kyocera printing at one of my clients. BSOD's in the same style as the problem with printing back in June 2020," confirmed another user, while stating that none of the normal fixes appear to be working.
Some of the printer brands known to be affected, include Kyocera, Ricoh, and Dymo.
Using virtual machines that received these updates yesterday, BleepingComputer has rolled back to the March preview updates and is no longer offered the KB5000802 cumulative update like we were yesterday.
This indicates that Microsoft has pulled the updates from Windows Update while they look into the issues. However, the updates are still available via the Microsoft Update Catalog.
Furthermore, some of our machines are being offered the KB4601382 Preview cumulative update released on February 24th, but not yesterday's KB5000802 update, indicating that a security update is likely causing the crashes.
Yesterday, Microsoft released two security updates, tracked as CVE-2021-1640 and CVE-2021-26878, to fix a privilege elevation vulnerability in the Windows Print Spooler.
Microsoft does not include security updates in the Preview cumulative update offered last month, which is likely why users did not experience the same crashes when printing.
During the June 2020 Patch Tuesday updates, a bug was also introduced that prevented users from printing. To resolve these printing issues, Microsoft released out-of-band updates for Windows users.
How to fix the win32kfull.sys crashes when printing
Unfortunately, attempts to fix the issue by upgrading printer drivers have been mainly unsuccessful.
Instead, Windows 10 users have been forced to uninstall the KB5000802 or KB5000808 updates for printing to work correctly again.
If you are affected by the printing bug, you can uninstall the Windows 10 KB5000802 cumulative update by closing applications and opening a command prompt. In the command prompt, enter the following command:
wusa /uninstall /kb:5000802
To uninstall the Windows 10 KB5000808 cumulative update, use this command instead:
wusa /uninstall /kb:5000808
You can use this guide for more help uninstalling the updates.
BleepingComputer has contacted Microsoft for further information but has not heard back as of yet.
Update 3/10/21: The updates are back and Microsoft states nothing was changed.
H/T WindowsLatest.com and thx to Opera for the tip!
Comments
aldfort - 3 years ago
Luckily in the UK, at least where I am, we don't get offered the update until Wednesday and it is not offered on either of my 20H2 PC's KB4601382 is on offer on one. I think I installed it on the other already a few days ago.
andreasoc - 3 years ago
thanks for the info and the tips.. we have the same problem with our PC with Win10 with network printer Kyocera.. pc crash
An-Tax - 3 years ago
Thanks for this.
I had 5000802 installed printing to Kyocera FS-1120d KX driver causing me blue screens.
Just had a customer call up printing to a Konica Minolta C360i Series but with PCL driver causing the same BSOD.
Going to add an exception to this KB until resolved.
eLPuSHeR - 3 years ago
Windows 10 20H2 19042.867
No issues here printing at Ricoh Aficio MP C3501 connected via ethernet (Mostly PCL5c and PCL6). I am using MS built-in drivers not Ricoh ones.
Pinpon10 - 3 years ago
I was having the same issue on two computers. Aditionally, the update also breaks Archicad license manager, it crashes the computer when trying to access the lincenses in the network. Unistalling the kb:5000802 sorted both problems.
aldfort - 3 years ago
update:
KB5000802 offered today on both PC's installed on both.
No issues but home metwork with an old Canon printer.
jobriathboy - 3 years ago
can confirm... multiple locations, kyocera and okidata printing causing system crash, as well as opening files in Corel Draw 7 and Libre Office causing same stop code crash... good times!
stevecor - 3 years ago
I had a problem with Dymo LabelWriter 400, it was printing blank labels. Removing kb5000802 cure. Also, this page helped very much with my Kyocera bsod problems
Cebic - 3 years ago
I have had same issue. Removing KB5000802 solved it. Printer is a Kyocera. I will report to Microsoft.
RJ_the_PC_Whisperer - 3 years ago
hahaha
"Update 3/10/21: The updates are back and Microsoft states nothing was changed."
And on Twitter: "I applied KB5000802 an hour ago, and got repeated APC_INDEX_MISMATCH BSOD's. I'd have to agree - nothing was changed. And nothing was fixed."
I concur that the issue is still happening. We have a few customers calling in and using Kyocera and Oki network printer drivers. Removing KB5000802 solved it for us as well.
realm - 3 years ago
we experienced same issue with a user everytime they tried to print to a kyocera cs printer - removing KB5000802 (and rebooting) solved issue
Renta-Geek - 3 years ago
I do not get BSOD, but Brother MFC printers now have two blank bars across photo printer. Document printing is not affected. Removing the KB5000802 update corrects the problem.
QQQQ - 3 years ago
Uninstalled KB5000802 on 6 computers yesterday and the blue screens stopped. Microsoft reinstalled them overnight and they are blue screening again, thanks a lot Microsoft!!!
Where do I send the bill?
QQQQ - 3 years ago
Just a heads up guys, MS is still forcing this update today 3-12-21, I just uninstalled it again and upon rebooting and checking for updates it automatically starts downloading. I had to pause updates for 7 days.
ISOHaven - 3 years ago
I have no clue how you people are uninstalling the update. Tells me and countless other people NO, cannot be uninstalled.
Anyway, this worked for us:
rundll32 printui.dll,PrintUIEntry /Xg /n "PRINTER NAME"
If you see ‘direct’, that means direct printing has been turned on and you had the right settings, and this method will not help.
If ‘Direct printing’ is off, run the following command:
rundll32 printui.dll,PrintUIEntry /Xs /n "PRINTER NAME" attributes +direct
Except for us, I had to use the full UNC path for the printer name.
Y0ssarian - 3 years ago
After you uninstall the updates you can prevent them from being reinstalled using Microsoft's Show or Hide Updates tool.(no longer available from MS?) I downloaded it from here: https://www.majorgeeks.com/files/details/wushowhide.html
mhanna87 - 3 years ago
No BSOD's here but I did have the white bars across page when printing 2 per page photos from Windows Print app on Canon printers, but also occurred on CutePDF, Adobe PDF, but strangely NOT Microsoft's PDF printing utility (or maybe not so strange). Reversing this update KB5000802 and preventing the reinstall with Y0ssarian's help above fixed this issue for us.
zRISC - 3 years ago
I manage around 40 Kyocera printers (between M36XX and M62XX) and easily 200 Ricoh P502
It seems that MS closed some kernel level access for printer drivers that use some functions that are now blocked or non-existent
In my case with Kyocera printers without uninstalling the update, the solution is:
- Use XPS based Drivers (forget the KX line).
- Use an old PCL5e based driver.
There are specific Kyocera KX-driver versions that don't make windows crash, but forgot the number; I fixed the issue with the XPS based driver, since I need a specific paper size and definition (8.5" x 13" ) that doesn't come in the PCL5e driver.
I haven't seen in Ricoh printers crashes yet with a PCL6 based driver specific for the printer model. Still I'm ready to test with a PSv4 driver (PSv4 MS signed and certified driver). A shame that we are fixing the issue as it appears in the Kyoceras :(
Lawrence Abrams - 3 years ago
I suspect that when they fixed a security vulnerability, they changed apermission or some other behavior that is causing this.
My guess is a out-of-band update will be released this week/next to fix these issues.
zRISC - 3 years ago
Seems there is already an OOB update for this, as I read on another article on the site.
For the specific printing issue, and "office computer usage", the workaround of XPS or PSv4 driver works fine in my case.
I also think they fixed some kernel 0-day and it blocked drivers that make use of that "feature".
But if there are another use cases: gaming gpu access or others... well, I better postpone updates until the next patch tuesday in personal machines. And seems like we'll need some testing vms (user, with all possible scenarios; and some servers) and a proper organization by groups in a WSUS for applying mass updates.
article:
https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-temporary-fix-for-windows-10-printing-crashes/
Lawrence Abrams - 3 years ago
Microsoft hasn't released an OOB update for this particular issue yet.
They released one for a similar printing issue in June;
https://www.bleepingcomputer.com/news/microsoft/windows-10-out-of-band-updates-released-to-fix-printing-issues/
zRISC - 3 years ago
Hi, thanks!
I see that now.. it was more of an unofficial fix.
Kind of miss the days that the updates were single and for specific issues (old 'w7 glory days').
Hope they fix it for the next batch of updates, or put an OOB. Anyways, for the "kyocera army" that we have deployed, the XPS drivers are working just fine.
RECBmore - 3 years ago
I found a 'fix' that worked for me since the XPS driver was not working.
Installing an older driver has fixed it.
Went here: https://ca.kyoceradocumentsolutions.com/en/download-center.html
put in my Printer Model and used the
KX V4 Driver / 6.0.1527 driver.
I installed the PCL6 and I am no longer BSOD.
Hope this helps a little.
Boggle_UK - 3 years ago
Hello, The Fix is live and lives in the Optional Updates in Windows Updates.
https://support.microsoft.com/en-us/topic/march-15-2021-kb5001567-os-builds-19041-868-and-19042-868-out-of-band-6e0844a2-7551-4b2d-9c4b-4274a5949bf3
Hope This Helps :-)
Renta-Geek - 3 years ago
I tried the KB5001567 update today and it did not correct the white bar problem in photo printing with Brother MFC printers. No BSOD, but still need a fix to move forward. Has anyone found a fix for the white bars problem?
Renta-Geek - 3 years ago
The KB50001649 update has corrected the white bar problem in photo printing with the Brother MFC printers for us.
Ripla - 3 years ago
"The KB50001649 update has corrected the white bar problem in photo printing with the Brother MFC printers for us."
You've got an extra 0 in there, but thank you this has helped with Brother printers!
I've had issues with Kyocera's and BSOD and this is the fix for those...
https://www.catalog.update.microsoft.com/Search.aspx?q=kb5001567
Also now having issues with Riso and white bars appearing when printing images - No fix for these yet
And had an issue with DYMO label printer printing black bars instead of text, the fix for that is here: https://www.dymo-label-printers.co.uk/news/troubleshooting-dymo-labelwriter-prints-blank-labels-or-advances-incorrectly.html
I have not come across a single PC which has KB5000808 installed, they've all been KB5000802 regardless of version of W10
When is this going to end? The issue seems to be expanding and affecting different printers in different ways!