Microsoft patch failed to fix problems with printing documents on Windows 10 – it can still cause BSOD

0
409

Microsoft patch failed to fix problems with printing documents on Windows 10 – it can still cause BSOD

This month Microsoft released another cumulative update for Windows 10, the installation of which, in some cases, results in a blue screen of death (BSOD) when trying to send a document to print. Later, the developers recognized the problem and released a patch that fixes it a few days ago, but, as it turned out, the difficulties with printing documents in Windows 10 do not end there.

microsoft
Microsoft

Earlier it was reported that in some cases, installing the March Cumulative Update for Windows 10 leads to a BSOD with an APC_INDEX_MISMATCH error when the user tries to print a document on the printer. Now it became known that the problem with printing is more varied and can be expressed because the printer prints only part of the document or does not print anything at all, giving out blank sheets.

The issue affects updates KB5000802, KB5000808, KB5000809 and KB5000822, which target different versions of Windows 10. Previously, the Microsoft support document stated that these packages could cause BSODs, but the developers have recently posted more information. For each of the four previously listed updates, the developers added the same description.

“ After installing the updates released on March 9, 2021, and March 15, 2021, you may receive unexpected results when printing documents from some applications. Problems can be expressed in the following:

  • Document elements may be printed as solid black/colored rectangles or missing, including barcodes, QR codes, and graphics such as logos.
  • Table rows may be missing. There may also be other alignment and page formatting issues.
  • Printing from some applications or to some printers may result in a blank page, ”Microsoft said in a statement.   
Also Read:   Microsoft releases cumulative update for Windows 7

It is worth noting that there is currently no temporary fix for this problem. Most likely, it can be solved by uninstalling the last cumulative update. Microsoft is working on a corresponding patch and promises to release it within a few days.