If you installed the latest Windows 10 update, you might be very frustrated right now. Are you staring at a BSOD (blue screen of death) right now? There are reports that some printers caused a BSOD after the Windows 10 update was installed.
BSOD Caused by Printers
Windows Latest was the first to report the issue. Kyocera, Ricoh, and Zebra printers are causing these crashes. When a file is sent to one of the printers, the PC will crash, and the user will get a BSOD. The error code of “APC_INDEX_MISMATCH for win32kfull.sys” will show up.
Usually, this particular code is indicative of hardware or drivers not being compatible. But you know your printer is compatible, and if there hasn’t been a new driver, it may leave you perplexed.
The Windows 10 update (KB 5000802) is causing Windows to react as if the printer drivers aren’t installed or linked. Hopefully, you saved your Word, Notepad, or other document right before trying to print. Otherwise, you’ll be left even more frustrated when you get that BSOD.
This Windows 10 update is affecting various Windows versions, both client and server. Microsoft is aware that printers are causing a BSOD. However, at this point, no fix has been released.
“We are presently investigating and will provide an update when more information is available,” it says on Microsoft’s support page.
Possible Fixes for the BSOD
There was a fix posted by a Microsoft employee on the SysAdmin subreddit. This fix will have you enabling direct printing and using the Application Compatibility Toolkit.
An additional problem is that the KB 5000802 update includes necessary security updates. Certainly, a workable option would be to drop back to a previous Windows 10 version, but that leaves your machine at risk.
It’s definitely a frustrating issue and not what you want to be dealing with heading into the weekend. Worse yet, you may still be working from home, so don’t have the luxury of just walking over to your co-worker’s desk to borrow their PC and/or printer.
Hopefully, it will have a quick fix by Microsoft and won’t lead to long-standing problems. That was the case with an update in 2019. It caused issues with Chromium-based browsers. By last May, it was still causing issues. Microsoft issued a patch, but that caused files to be deleted without warning. Clearly, the company was going in the wrong direction.
Comments
Post a Comment