{"id":83976,"date":"2021-03-18T04:42:01","date_gmt":"2021-03-17T17:42:01","guid":{"rendered":"https:\/\/itt.com.au\/?p=83976"},"modified":"2021-03-18T04:42:01","modified_gmt":"2021-03-17T17:42:01","slug":"the-latest-windows-10-update-is-causing-pcs-with-bsod-crashes","status":"publish","type":"post","link":"https:\/\/itt.com.au\/the-latest-windows-10-update-is-causing-pcs-with-bsod-crashes\/","title":{"rendered":"The latest Windows 10 update is causing PCs with BSOD crashes"},"content":{"rendered":"\n

There are some crashes in relation to the latest Windows 10 update (the affected updates are KB5000802, KB5000808, KB5000809, and KB5000822<\/strong>).<\/p>\n\n\n\n

This update is causing users to experience BSOD (Blue Screen of Death) when they use printers. Windows 10 version 1909 Users facing similar issue as well.<\/p>\n\n\n\n

KB5000802 is an automatic security update so It means that it is downloading and installing Automatically for some customers. Users won\u2019t have a say in whether or not Microsoft should install the update and break their computers with BSOD.<\/p>\n\n\n\n

This update seems to be causing blue screens when printing to Kyocera (Ricoh, Zebra, and others) Universal Print drivers. <\/p>\n\n\n\n

To make matters worse, Windows 10 simply crashes when users try to print via Notepad, Office, LibreOffice and other apps. This happens only when your device is using an affected printer\/printing driver.<\/p>\n\n\n\n

win32kfull.sys BSOD Caused by KB5000802\u00a0<\/h3>\n\n\n\n

some users discussing on reddit that Windows 10 KB5000802 broke all Kyocera printing for their clients.<\/p>\n\n\n\n

This problem will not be being solved with printer driver update.<\/p>\n\n\n\n

Some reports indicating Microsoft has temporarily removed the rollout of the March 2021 cumulative update, while others said that they\u2019re still seeing the cumulative update on the Windows Update page.<\/p>\n\n\n\n

Fix the win32kfull.sys BSOD<\/h3>\n\n\n\n

changing driver to the Microsoft PCL XPS driver PCL6 driver Kxv4_v511708 may work for some users but the best solution is, to delete the patch which will undo the changes that were made. If you have installed the security update KB5000802 on Windows 10 20H2 or 2004 or KB5000808 on 1909 and encountered win32kfull.sys BSOD so follow the easy methods ahead.<\/p>\n\n\n\n

  1. Open Settings > Update & Security > Windows Update.<\/em><\/strong><\/li>
  2. Click on \u2018View Update History<\/em><\/strong>‘<\/li>
  3. Click on \u2018Uninstall updates\u2019 link.<\/strong><\/em><\/li>
  4. Locate the update and click on \u2018Uninstall\u2019.<\/strong><\/em><\/li>
  5. Select \u2018Yes\u2019.<\/strong><\/em><\/li><\/ol>\n\n\n\n

     If it\u2019s not possible to uninstall the patch through Control Panel, so try with following Command Prompt or PowerShell command to remove the patch manually:<\/p>\n\n\n\n

    wusa \/uninstall \/kb: [id]<\/em><\/strong><\/p>\n\n\n\n

    In the above, it is needed to replace the KB ID with the one that you wish to uninstall.<\/p>\n\n\n\n

    If you\u2019re on v2004 or 20H2, the command would be wusa \/uninstall \/kb:5000802<\/strong>. For version 1909\/1903, the command is wusa \/uninstall \/kb:5000808<\/strong>.<\/p>\n\n\n\n

    Another solution is to switch to Microsoft PCL6 printer drivers or removing the printers completely (including drivers).<\/p>\n\n\n\n

    Once you\u2019ve followed the above steps, open Settings > Update & Security > Advanced options and pause the updates.<\/p>\n\n\n\n

    If it\u2019s not possible to uninstall KB5000802,<\/h3>\n\n\n\n

    In the case of using Command Prompt or PowerShell, the process could fail with the following error:<\/p>\n\n\n\n

    Security Update for Microsoft Windows (KB5000802) is required by your computer and cannot be uninstalled.<\/p>\n\n\n\n

    In this case, rolling back to the previous version of Windows is needed by using the Recovery Options. If you don\u2019t want to uninstall the update, you can also try the second, third and fourth method highlighted below.<\/p>\n\n\n\n

    1. For advanced users, the second method requires you to enable Direct Printing which allows 32-bit apps to print on 64-bit OS without crashing the OS. regarding this solution, you need to follow below steps:<\/li>
    2. Identify the name of your printer. (Eg: Kyocera TASKalfa 820 KX).<\/li>
    3. Open Command Prompt (admin\/elevated) and run the following command.<\/li><\/ol>\n\n\n\n

      rundll32 printui.dll,PrintUIEntry \/Xg \/n “Kyocera TASKalfa 820 KX”<\/p>\n\n\n\n

      if the outcome is \u201cdirect \u201cso it means that direct printing has been turned on, and this method will not help.<\/p>\n\n\n\n

      If \u2018Direct printing\u2019 is off, run the following command:<\/p>\n\n\n\n

      rundll32 printui.dll,PrintUIEntry \/Xs \/n “Kyocera TASKalfa 820 KX” attributes +d<\/p>\n\n\n\n

      In the above example, replace the \u201cKyocera TASKalfa 820 KX\u201d text with your printer\u2019s name.<\/p>\n\n\n\n

      If direct printing is already enabled and Windows is still crashing, you can try the second advanced fix involving Microsoft\u2019s PrintIsolationAware feature:<\/p>\n\n\n\n