The updates released yesterday are causing Blue Screen of Death crashes when printing to network printers. Apparently, after the new updates, some users experienced BSoD errors while trying to use a network printer in Windows. Here’s how one of them is complaining on Reddit: Another user comments on the same Reddit post about the same issue hinting at uninstalling the update to fix the issue:
How can I fix the Windows 10 network printing issue?
1. What are the errors triggered by KB5000802 and KB5000808?
Until now, from the user testimonials, the brands affected by these printing bugs are Kyocera, Dymo, and Rycoh. The BSoD error triggered by the updates is the APC_INDEX_MISMATCH which we already covered. However, updating the printer driver recommended in that solution didn’t work this time. In the meantime, Microsoft has been notified about the issue and they rolled back the updates from the Windows Update. However, they are still available in the Microsoft Update Catalog so the first step to stop this problem is to avoid installing the KB5000802 and KB5000808 updates. Update: Microsoft acknowledged the issue and resolved it with the out-of-band update KB5001649, so if you check for updates and install the KB5001649, the issue will be resolved. To check for updates, type updates in Windows search and select Check for updates. You should see the Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5001649). Click on Download and install button under it to proceed with the installation. If you can’t find it and didn’t install it already, you can also find it in the Microsoft Update Catalog.
2. Force uninstall the KB updates
One of the best solutions for fixing this problem and going back to normal printer usage until now is to force uninstall the KB updates. SPONSORED So, if you are one of those who already installed the new KB5000802 and KB5000808 updates, you can fix this by running the following commands in an elevated Command Prompt window and pressing enter after each one: The first command is for uninstalling the KB5000802 update and the second is for uninstalling the KB5000808 update.
3. Manually uninstall the updates
Another great solution would be to rollback your system to a previous restore point. If you don’t know how to create a restore point, we have an excellent article that will guide you all the way.
4. Enable Direct Printing
5. Use a third-party tool to get rid of BSoD errors
Because BSoD errors never have a clear cause, it’s hard to pinpoint exactly what measures should be taken to fix them, so you’re only solution is to use a software tool that can go through several troubleshooting procedures.
6. Uninstall and reinstall the drivers
6.1 Uninstall the printer driver This software can also help you by creating a restore point before starting the repairs, enabling you to easily restore the previous version of your system if something goes wrong. This is how you can fix registry errors using Restoro: As soon as the fixing process is completed, your PC should work without problems, and you will not have to worry about BSoD errors or slow response times ever again. ⇒ Get Restoro Disclaimer: This program needs to be upgraded from the free version in order to perform some specific actions. One of our readers managed to solve this problem by deleting the drivers, so make sure you try this also. 6.2 Update the drivers automatically The manual remove of the driver will trigger the system to install a default driver that might not be the best for your printer. Of course, you can also visit the manufacturer’s website, download the exact driver and install it but it’s a lot easier to use a dedicated, third party tool like the one recommended below. It’s light, easy to install, and it will repair or update all your drivers in a fraction of the time needed for the manual procedure. ⇒ Get DriverFix We hope that you managed to get back to your printing activities after uninstalling the updates. Do you have any other solutions? Let us know in the comments below so that others can also benefit.
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
