Bluescreen of death and restarts after KB5000802

The same here on Windows 10 20H2 2 PCs with bluescreen, W10 2004 works fine.

Hi all,

If you are running into a problem APC_INDEX_MISMATCH BSOD while printing, I recommend trying out these steps to mitigate the issues until Microsoft addresses the problem with the update.

Section 1 - Enable Direct Printing. This should allow 32bit apps to print on 64bit OS without crashing.

1. Identify the name of your printer. E.g., "Kyocera TASKalfa 820 KX"

2. In an elevated command prompt, run rundll32 printui.dll,PrintUIEntry /Xg /n "Kyocera TASKalfa 820 KX". If Direct appears on the line of attribute:, that means direct printing has been turned on and you had the right settings - stop here and proceed to section 2.

   1. Note - replace the Kyocera TASKalfa 820 KX text with your printer's name

3. If Direct setting is not on, in an elevated command prompt, run rundll32 printui.dll,PrintUIEntry /Xs /n "Kyocera TASKalfa 820 KX" attributes +direct

   1. Note - replace the Kyocera TASKalfa 820 KX text with your printer's name

Often times, apps like Acrobat and OpenOffice runs as 32bit apps and this should be enough to workaround around the problem until Microsoft addresses the issue. But this will not solve the problem for 64bit applications printing on 64bit OS, nor 32bit applications printing on 32bit OS.

Section 2 - Enable PrintIsolationAware appcompat fix to your printer. This should allow 64bit applications printing on 64bit OS and 32bit applications printing on 32bit OS without crashing.

1. Follow the directions from the following page to acquire the Application Compatibility Tookit Download: Application Compatibility Toolkit (ACT) for Windows 10. | Microsoft Docs

2. Follow the instructions - Creating a Custom Compatibility Fix in Compatibility Administrator (Windows 10) - Windows Deployment | Microsoft Docs - to use the Compatibility Administrator tool to apply the “PrinterIsolationAware” fix to the affected application

Thank you,

Christopher

hey Christopher
Thanks for the input 
I've spend the whole day yesterday just rolling back systems in multi customer sites and some needed to drive to since the internet is so bad and does not allow remote and I was in such a hurry I didnt cancel auto update and it got reinstalled in some it been a hassle would love it if this wouldn't have happen in the first place :'( 

Having the same issue with Kyocera TASKalfa printers, removing the update only thing that fixed it so far.

Thanks Cristopher, have posted your valuable information in another major thread related to the same issue. Also, there are some more problems reported with the March Patches with respect to Printing.

APC INDEX MISMATCH BSOD error Today reported for more that 10 Dell - Microsoft Community

Many reports like this thread where JPEG isn't printing correctly.

Problem printing jpeg files - Microsoft Community

We have uninstalled back on 3/10 but the update keeps coming back to be installed on some users. Any suggestions?

Hi all,

If you are running into a problem APC_INDEX_MISMATCH BSOD while printing, I recommend trying out these steps to mitigate the issues until Microsoft addresses the problem with the update.

Section 1 - Enable Direct Printing. This should allow 32bit apps to print on 64bit OS without crashing.

1. Identify the name of your printer. E.g., "Kyocera TASKalfa 820 KX"

2. In an elevated command prompt, run rundll32 printui.dll,PrintUIEntry /Xg /n "Kyocera TASKalfa 820 KX". If Direct appears on the line of attribute:, that means direct printing has been turned on and you had the right settings - stop here and proceed to section 2.

   1. Note - replace the Kyocera TASKalfa 820 KX text with your printer's name

3. If Direct setting is not on, in an elevated command prompt, run rundll32 printui.dll,PrintUIEntry /Xs /n "Kyocera TASKalfa 820 KX" attributes +direct

   1. Note - replace the Kyocera TASKalfa 820 KX text with your printer's name

Often times, apps like Acrobat and OpenOffice runs as 32bit apps and this should be enough to workaround around the problem until Microsoft addresses the issue. But this will not solve the problem for 64bit applications printing on 64bit OS, nor 32bit applications printing on 32bit OS.

Section 2 - Enable PrintIsolationAware appcompat fix to your printer. This should allow 64bit applications printing on 64bit OS and 32bit applications printing on 32bit OS without crashing.

1. Follow the directions from the following page to acquire the Application Compatibility Tookit Download: Application Compatibility Toolkit (ACT) for Windows 10. | Microsoft Docs

2. Follow the instructions - Creating a Custom Compatibility Fix in Compatibility Administrator (Windows 10) - Windows Deployment | Microsoft Docs - to use the Compatibility Administrator tool to apply the “PrinterIsolationAware” fix to the affected application

Thank you,

Christopher

Hi Christopher

Microsoft's update is a disaster. I am the technical support manager for KYOCERA printers in my country.

We experience hundreds of phone calls from customers whose computers crash following anKB5000802 update.

Someone at Microsoft must urgently address the damage they have created.

Gad Cohen

Though I am not seeing the BSOD, but, my HP 2520HC printer has gone crazy after this update. Nothing is getting printed fully, and all are partial prints. When I try to print an image by right-clicking on the image in explorer, going to the print option in the popup menu, I get partial prints. Moreover, this update does not give me an uninstall option. Doesn't Microsoft test its updates before rolling out?

I heavily depend on printing requirements for my work and I am screwed. The update is:

Security Update for Microsoft Windows (KB5000802)

Servicing Stack 10.0.19041.860

> Updated MS advice here: https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-2004#1570msgdesc 

> https://www.ghacks.net/2021/03/13/microsoft-publishes-workaround-for-printing-bluescreen-issue-in-windows/

EXACTLY!!!!!!!!!!!! Totally 100% agree!

Microsoft Plz DO TESTING!  BEFORE releasing to PUBLIC! 

it's 101 basic knowledge with software developers

Otherwise the NEXT BEST SOLUTION >> will be to  switch to APPLE Computer!

and NO MORE  of these silly & time wasting  BUGS

I call it "Kinda Surprise" by microsoft!