If you are one of the people who has been affected by the newest Windows bug that causes the dreaded blue screen when using a printer, Microsoft has released a palliative solution to the problem, until a new official operating system update is released.
According to the developer, the problem “affects a subconfiguration of Type 3 printer drivers and does not affect drivers that are Type 4.”
Click here to find out the type of printer installed on your PC.
The temporary solution consists of the following steps:
To print using 32-bit applications (eg, Acrobat, OpenOffice) on Windows 64-bit Windows without errors, Microsoft recommends using your printer’s Direct Printing, using the following procedure:
Open a command prompt with administrator privileges and run the following command to find out if the function is enabled (Replace printer name with the name of your printer):
- rundll32 printui.dll, PrintUIEntry / Xg / n PRINTERNAME
If Direct Printing is not enabled, run the following command at the command prompt with administrator privileges (replace printer name with the name of your printer):
- rundll32 printui.dll, PrintUIEntry / Xs / n PRINTERNAME attributes + direct
To print from a 64-bit application on a 64-bit operating system or use a 32-bit application on a 32-bit OS, you need to download and install the Application Compatibility Pack to apply the PrinterIsolationAware patch to the affected areas using the Compatibility Administrator tool.
Will it still take a long time to come up with a definitive solution to the problem?
What a bad impression: bug in Windows 10 causes a blue screen of death when using the printer
Windows 10 updates continue to give some users headaches. Yesterday we already announced that the latest version is causing problems in the File History and now a new bug has appeared causing the dreaded blue screen of death when using the printer. Understand now how you can avoid this problem.
According to Bleeping Computer, some users are reporting the problem that makes the blue screen appear suddenly when using a printer via sharing on Windows Server. The complaints started to arise after Microsoft started distributing the KB5000802 and KB5000808 updates for Windows 10, so we believe they are the cause of the problem.
As you can see above, the error described by the blue screen is “APC_INDEX_MISMATCH for win32kfull.sys”. Users who have encountered the problem say that it occurs on printers of various brands such as Kyocera, Ricoh and Dymo, and many others.
Microsoft claims that it has already acknowledged the error and has removed the automatic download of updates from Windows Update, however, they are still available via manual download for Windows 10.
For now, tests of Bleeping Computer on virtual machines have indicated that the problem may be related to a security update released in February.
So far the only solution found has been to uninstall the KB5000802 and KB5000808 versions of the system from the Windows 10 update center by going to Update History> Uninstall updates. However, it is worth remembering that this is not recommended, as they include new security definitions and other corrections that may be essential for the system.