Windows crashes when printing or is unable to print.
Symptoms
Windows BSOD (Blue Screen Of Death), Windows crashes, printing application crashes, ...
GDI Objects reaches the limit of 10.0000. This can be seen in Windows Task Manager
> Details
tab > GDI objects
.
(If this column is not available right-click on the column headers and click Select columns, this will show an overview of columns to add, including the GDI objects column.)
When having multiple installations with the same OS and same Windows Updates installed and you see that some environments don't have problems with printing, this could be an indication that these might have different print drivers which might not be affected.
Cause
Microsoft released a new update on March 9, 2021. This happens when installing Windows Update KB5000802 on Windows 10, KB5000822 on Windows Server 2019 and possibly KB5000808. All is related to a security fix CVE-2021-1640 that breaks printing. This affects printing to physical printers and virtual printers.
From the Microsoft release notes:
Improvements and fixes
Addresses an elevation of privilege security vulnerability documented in CVE-2021-1640 related to print jobs submitted to “FILE:” ports. After installing Windows updates from March 9, 2021 and later, print jobs that are in a pending state before restarting the print spooler service or restarting the OS will remain in an error state. Manually delete the affected print jobs and resubmit them to the print queue when the print spooler service is online.
- KB5000802: Windows 10/Windows Server version 2004, 20H2
- KB5000808: Windows 10/Windows Server version 1909
- KB5000822: Windows 10 version 1809, Windows Server 2019
Also including the FILE: port fix:
- KB5000848 / KB5000853: Windows 8.1 / Windows Server 2012 R2
- KB5000841 / KB5000851: Windows 7 SP1
For a full list of specific Windows Update KB numbers for a specific OS, see the website below regarding the vulnerability CVE-2021-1640.
Resolution
Resolution 1:
Install the corresponding Windows Update to fix this issue.
KB5001567 fixes KB5000802
Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803
Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803
https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-20h2#1570msgdesc
https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-2004#1570msgdescKB5001566 fixes KB5000808
Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803
Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803
https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1909#1570msgdescKB5001568 fixes KB5000822
Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803
Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803
https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1809-and-windows-server-2019#1570msgdescKB5001565 fixes KB5000809
Client: Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803
Server: Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803
https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-1803#1570msgdesc
Resolution 2:
Uninstall the specific update and reboot:
- Open Windows Control Panel.
- Click on Programs.
- Click on Programs and Features.
- On the left side click on View installed updates.
- Uninstall
Security Update for Microsoft Windows (KB5000802)
.
(or the other mentioned KB depending on your OS.) - Wait for Microsoft to fix this issue! (2021-03-16: Fixed by Microsoft)
Via an internet forum there is a workaround in the wild in case you suffer from the APC_INDEX_MISMATCH BSOD: https://www.reddit.com - sysadmin
Extra
- Confirmed and tested by Winking on 11/03/2021.
- All hardware brands and software might be affected.
See also
- Windows Print Spooler Elevation of Privilege Vulnerability CVE-2021-1640 Released: Mar 9, 2021https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-1640
- March 9, 2021—KB5000822 (OS Build 17763.1817) https://support.microsoft.com/en-us/topic/march-9-2021-kb5000822-os-build-17763-1817-2eb6197f-e3b1-4f42-ab51-84345e063564
- March 9, 2021—KB5000802 (OS Builds 19041.867 and 19042.867) https://support.microsoft.com/en-us/topic/march-9-2021-kb5000802-os-builds-19041-867-and-19042-867-63552d64-fe44-4132-8813-ef56d3626e14
- Windows-update veroorzaakt BSOD bij gebruik van verschillende netwerkprinters https://tweakers.net/nieuws/179092/windows-update-veroorzaakt-bsod-bij-gebruik-van-verschillende-netwerkprinters.html
- Windows 10 KB5000802 (March) update is crashing PCs with BSOD https://www.windowslatest.com/2021/03/10/windows-10-kb5000802-march-update-is-crashing-pcs-with-bsod/
- Kyocera Drivers Patch Tuesday BSOD - sysadmin reddit.com Forums https://www.reddit.com/r/sysadmin/comments/m1jkuz/kyocera_drivers_patch_tuesday_bsod/gqj91b3/