• MS-DEFCON 1 – Blue screens of death triggered by patches

    Home » Forums » Newsletter and Homepage topics » MS-DEFCON 1 – Blue screens of death triggered by patches


    PATCH WATCH By Susan Bradley Don’t patch! I’ve moved the patching alert status to DEFCON 1. I don’t do this lightly but we are seeing issues with prin
    [See the full post at: MS-DEFCON 1 – Blue screens of death triggered by patches]

    Susan Bradley Patch Lady

    5 users thanked author for this post.
    Viewing 39 reply threads
    • #2349551

      Why is a public service announcement for the better of everyone a Plus-only thing? Explanations about changes in the MS-DEFCON rating had always been available for free before the Plus system came in, and the whole idea of Plus was that it would be something extra.

      I think that something as important as an emergency change in the MS-DEFCON rating should be publicly available. Not only is this good for non-paying users, but it allows us to link and share the information.

      1 user thanked author for this post.
      • #2349560

        Remember you can be a plus member for any amount of donation.  Secondly you can look at the top and see the change so it’s not being limited.  Emailing out an alert – which is what these are hooked to – is reserved for those that donate to the site.

        Susan Bradley Patch Lady

        2 users thanked author for this post.
      • #2349584

        Agree totally. This is not “Ask Woody” behavior. Change the site name to “Ask Susan”.

      • #2349656

        Susan made a post here detailing the issue for free users. A link to Ghacks also provides me with the information I need to know about the buggy patch. So no, I don’t think us non-subscribers are being left out of the loop, even though it might seem that way. Anyways, I can see MS-DEFCON 1—that’s good enough for a non-techsavvy user.

        2 users thanked author for this post.
    • #2349552

      Haven’t updated to 20h2 yet. Currently using an HP Office jet printer. Should I be be concerned about this if I
      finally take the update plunge? Thanks


    • #2349562

      Running 20H2 Pro OS Build 19042.867, printer is HP Officejet 8600 All-in-one.

      No issues.  Printing works, scan to computer works, no BSOD’s.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We were all once "Average Users". We all have our own reasons for doing the things that we do to our systems, we don't need anyone's approval, and we don't all have to do the same things.

      2 users thanked author for this post.
      • #2349972

        Based on the replies from bbearen and RetiredGeek, (especially the bbearen’s reference to the HP printer), I just finished installing kb5000802 and the accompanying  service stack. I’m now running Win 10 Pro 10.0.19041.867.

        My All-in-1 printer, HP Officejet Pro 6978 works just fine. No problems printing or scanning. No BSOD.

        My computer is a Preloaded Win 10 refurbished Lenovo ThinkCentre E73 that I bought last year for $185 when Win 7 became unusable for me. It’s not fancy but it serves my needs.

        Hope this helps, Susan. As an aside, I’m happy to contribute money to this site, especially given all the excellent support I’ve received.



    • #2349567

      I’ll see if I can gather a list of machines having issues:

      Here’s one:  “Kyocera seems to be the catalyst. Install the specific PCL6 driver instead of the universal print driver that seems to be causing the problem”

      Another “Reports of printer failures include Kyocera, Ricoh, Zebra, and others”

      “It seems that the most affected are Kyocera/Triumph-Adler/Utax/Copystar copiers family.

      If you have PC with Win 10 versions 1909, 2004, 20H2 and Kyocera family type 3 KX print driver, after this update you’ll get BSOD APC_INDEX_MISMATCH.”

      Susan Bradley Patch Lady

      2 users thanked author for this post.
      • #2350525

        7 or 8 of my clients have recently updated their Win 10 Pro machines with no problems whatsoever, running Dell desktops and notebooks of all ages and RAM capacities and Heinz 57 printers, both laser and ink jet (although they are all HPs). Just lucky? Who knows…

    • #2349568

      How does one undo the patch?


      • #2349572

        If it didn’t trigger a blue screen upon printing, I would leave it.

        However to uninstall it, click on start, settings, update and history, view update history, uninstall updates. Scroll to the listing of Microsoft Windows patches and double click. It will ask to uninstall. Follow the prompts and reboot.

        Susan Bradley Patch Lady

        1 user thanked author for this post.
    • #2349577

      Edition: Windows 10 Pro 64-bit
      Version: 2009 20H2
      Build: 19042.867
      Installed: 12/23/2020 10:26
      Printer: Brother HL-L2350DW

      NO PROBLEMO! 😎

      May the Forces of good computing be with you!


      PowerShell & VBA Rule!
      Computer Specs

      2 users thanked author for this post.
    • #2349602

      I installed KB 5000802 on my test machine. After reading about the problems, I decided to uninstall  it. The OS says that “It is not able to be uninstalled”.


    • #2349607

      Don’t patch!

      Up to now, Windows Update March 2021 presented NO issues whatsoever, that I could see.

      I have:
      Clevo portable (socalled laptop, purchased new Febr. 2015)
      Windows 10 Home 64bit, installed Oct. 2015
      now updated to version 20H2, build 19042.867, March 09, 5 PM Seattle time.
      Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz 2.80 GH + 32 GB RAM
      NVIDIA GeForce GTX 970M
      2-in-1 printer/scanner Canon G6000 series, driver
      9 (yes nine!) external USB hard disk drives (27 TB in total)
      1 external eSata hard disk drive (only connected for system partition images)

      1 Desktop Win 11
      1 Laptop Win 10
      Both tweaked to look, behave and feel like Windows 95
      (except for the marine blue desktop, rgb(0, 3, 98)
      1 user thanked author for this post.
    • #2349639

      With pre-patched images on standby, the following patches were installed
      NOTE: both obtained from the MS catalog:
      Win8.1 x64 March SMQR KB5000848 (on two devices, haswell desktop and ivybridge laptop) connected to a local Canon Pixma printer (via USB)
      Win7 x86 (w/ESUBypass) March SMQR KB5000841 on a core2duo laptop and connected to the printer later.
      Findings: NONE exhibit ANY printer printing/comms/crash issues and print queues as expected with no violations via SFC integrity check, all good here.

      Keeping IT Lean, Clean and Mean!
      1 user thanked author for this post.
      • #2349658

        Well MSFT have ‘fessed up to the APC_INDEX_MISMATCH error with a blue screen when attempting to print for the following:

        Affected platforms:

        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

        Source MSFT

        Keeping IT Lean, Clean and Mean!
        3 users thanked author for this post.
    • #2349698

      Interestingly I just re-scanned for updates (wuMgr) and 4589212, and 5000802 are both marked “for 20H2”. They weren’t yesterday. I am running 20H2. I did not apply them, but I could easily image and apply then and run a test if that would be helpful. I have a HP color laserjet pro m254dw. Let me know.

      - Thinkpad P15s Gen1 20T4-002KUS, i7-10510U, UEFI/GPT, 16GB, Sammy 500GB M.2.
      - Mint Cinnamon 21 current, Win 10 22H2. WuMgr. HP laserjets M254dw & P1606dn, Epson 2480 scanner.

    • #2349700

      Why is a public service announcement for the better of everyone a Plus-only thing?

      We have not changed the behavior. When newsletters and alerts go out, they are numbered, such as 18.9.0, 18.9.1, etc. 0 is a newsletter, higher digits are alerts. If the suffix of an issue is a digit, it is paid content. Always has been, as best I can tell.

      If the issue number is something like 18.9.F, that is free content.

      Why paid only? Because it’s not free for us to do the mailing – we pay every time we mail. Without the community support, without your donations, we couldn’t do any of this.

      Remember that two things are always public. The first is the MS-DEFCON banner at the top of every page on the site, accessible not only to paid and registered members, but to anyone who visits. We invite everyone to stop by, at any time, to see Susan’s take on patch safety. The second is this very forum topic, also accessible to all.

      1 user thanked author for this post.
    • #2349710

      What are insiders / beta testers good for ?

      • #2349715

        Insiders don’t test security patches.  Insiders test the NEXT version of windows.  It’s totally not the same code.

        Susan Bradley Patch Lady

        1 user thanked author for this post.
    • #2349701

      confirmed BSOD on 2 PCs at work w/ 20H2 w/ the March update.

    • #2349725

      re:   W7 x64   KB5000841   March 2021 Quality Rollup

      I have confirmed that this rollup _DEFINATELY_  has a bug that causes one of my dotNet 4  based applications to no longer display jpg images [and maybe other image types too, like png’s].  The app is Album Art Downloader, a long standing well debugged app, I’ve used it for years.

      After this update the app would no longer display any pictures, just grey-box place-holders; when asked to save those images it saved perfectly fine files that could be viewed ok.  So it’s a displaying-to-the-screen issue, not a network or file issue.

      I thought the problem was the March dotNet 4.8 update, but it was not, since removing that did not fix things.

      Instead removing KB5000841 solved the problem, the app now works normally again [and the March dotNet 4.8 updates _ARE_ still installed].

      So, the March W7x64 Monthly is not ready for prime-time either…



    • #2349735

      Win 10 PRO 2004 Installed this AM and no issues.

      However, this patch was forced download and waiting to install this AM.

      I have had this PC set to PKCano settings to allow only “downloads available” for all of 1909.

      Late last month I decided to upgrade to 2004 and ever since it seems 2004 is ignoring all my previous, and re-set after 2004, settings.

      I did not Pause as I did before using PKCano settings as there was no need but I will go back to that if 2004 and onward is going to ignore our settings.

      I will follow up on PKCano’s KB and see if maybe I have missed a new change.

      • This reply was modified 2 years, 3 months ago by .
      • #2349744

        Verify your settings in the Local Group Policy editor, then open an elevated command prompt. Type in gpupdate /force and press Enter. Answer “Y” to any prompts you might get, to include rebooting the machine.

        I had the same problem you did back in November, IIRC, after I went to 2004. Doing this seemed to fix the problem for me. It’s not recurred and I have updated to 20H2 as well without my settings being messed with.

        PKCano speculated that turning metered connections on/off might trigger Windows Update to run, but I’m pretty sure I never did that here.

        It’s also worth remembering that Microsoft doesn’t promise to respect this notify me before download setting. On the main Windows Update page in the Settings application, it says this:

        *We’ll ask you to download updates, except when updates are required to keep Windows running smoothly. In that case, we’ll automatically download those updates.

        I don’t know if this is what happened to both you and me. I also don’t know what Microsoft thinks it might have to download to keep Windows running smoothly. Note that it says “Windows” and not “Windows Update”.


        • #2349781

          *We’ll ask you to download updates, except when updates are required to keep Windows running smoothly. In that case, we’ll automatically download those updates.

          Yeah I noticed that change on the Update page which was new and wasn’t displaying on 1909.

          Thanks for the hint.

    • #2349806

      KB 5000802 causes issues with virtual printers such as PDF Creator where 1/3 of the print has a white band through the resultant print when printing a photo as a pdf.

    • #2349840

      As a recent ex-Win7 user, can anyone tell me if it’s possible in x64 Win10Pro to see a list of the updates, with their associated KB numbers, as was normal in Win7? I’d really like to be able to see and evaluate the updates queued for installation before I press the Go button, but I have been unable to find such a straightforward listing. Maybe I have failed the intelligence test…

      • #2350016

        Yes, it is possible to see a list of installed updates on Windows 10 20H2 and all previous versions. They appear in two places, in the familiar Control Panel applet Programs and Features\View Installed Updates, and in the “modern” Settings app, under Update & Security, through the link “View update history”.

        It should be noted that the list in the “modern” app takes up much more screen real estate than is necessary, and you’ll do more scrolling. Even worse, it doesn’t list all of the updates that the older list shows. But it will list recent OS, Office, and .NET updates.

        Group K(ill me now)
        • #2350480

          Thanks, but I was specifically looking for the list of updates scheduled for installation, so I could block any I chose, rather than post-installation.

    • #2349842

      I also don’t know what Microsoft thinks it might have to download to keep Windows running smoothly

      Example : Microsoft will force Windows 10 upgrade 60 days after EOL of current version.

    • #2349844

      see and evaluate the updates queued for installation before I press the Go button,

      In GP set ‘notify don’t download..’ = 2 and you will get the list of updates waiting to download on Windows Update page.

      1 user thanked author for this post.
    • #2349916

      Sticking with 2004 for now. I usually don’t update until the current version is no longer supported. Usually by that time most of the bugs have been eliminated.


      • #2350019

        I skipped 2004 and waited until the minor fall update, 20H2, had been out a couple of months. The fall updates have basically been cumulative bug fixes of the major updates offered in the Spring. However, Microsoft has said that they’re reversing those releases, and will offer major updates in the fall, instead.

        Group K(ill me now)
    • #2349948

      DEFCON 1.
      Also knocked out Dymo Label printers…
      Installed before I read the warning, Never Again…
      Dymo update severs are jammed, my fault…
      Really upset w/ myself…

      • #2349953

        Uninstall the updates.

        • #2350006

          I uninstalled update KB5000802 just to be on the safe side.

          Should I uninstall the other two updates?

          KB4601382 (Servicing Stack Update?) and KB4589212?



          • #2350015

            KB4601382 (Servicing Stack Update?) and KB4589212?

            The March CU, KB5000802, is most likely the cause of your problem.

            KB4601382 is a Feb Preview CU and KB4589212 is Intel Microcode.
            If the problem has gone away, I’d leave these two alone.

            1 user thanked author for this post.
            • #2350020

              Agreed. KB5000802 is the one with print driver problems.

              Also, NEVER install “preview” updates. Ever. Don’t even fantasize about it. If the thought enters your mind that it might be a good idea, consider taking a vacation, instead. Leave them for the people whom Woody called “unpaid beta testers”.

              Group K(ill me now)
              1 user thanked author for this post.
    • #2349958

      I don’t think the printing “bug” is a bug. I think it is a Microsoft’s new feature to ‘save the forests’ /s

      3 users thanked author for this post.
    • #2349967

      I installed the March 2021 updates on a personally built PC tower.
      20H2 (OS build 19042-867) was -804.
      I downloaded the March update from the MS catalog and installed while not using the PC for anything else. Rebooted after the install completed.  My normal practice.

      No blue screen so far with printing but I did lose my HP LaserJet M203-M206 PCL-6 Ethernet connected printer. “No driver” I had to “remove” the printer and re-install the driver to get it to work again.

      1 user thanked author for this post.
    • #2349990

      Alex 5723 is right on, just remove the update, now all’s well w/ printing Dymo labels & all other printing.

      1 user thanked author for this post.
    • #2350048

      Thanks for the heads up.

      Are microsoft software developers still working from home? Might have something to do with it.

    • #2350065

      Might have something to do with it.

      It has nothing to do with working from home as Windows update history taught us in the last 20 years.

    • #2350096

      Heads up!
      Microsoft have released a temporary fix for the printer bug within kb5000802. From that page:

      This issue affects a subset of Type 3 printer drivers and does not affect printer drivers that are Type 4. If you are unsure which type your printer driver is, use the following steps:

      1 Press the Windows key+r or select Start and type run and select it.

      2 Type printmanagement.msc and press enter or select the OK button

      3 If Print Management opens, continue to step 4. If you receive the error, Windows can not find ‘printmanagement.msc’. then select Start and type manage optional features and select it. Select Add a Feature and type print, select the check box next to Print Management Console and select install. You will now need to start at step 1 again

      4 Expand Print Servers, expand your computer’s name, and select Printers

      5 You can now see the Driver Type for each of your installed printer drivers.

      More info and thanks to Martin Brinkmann over on Ghacks.net

      Keeping IT Lean, Clean and Mean!
      • This reply was modified 2 years, 2 months ago by Microfix.
      1 user thanked author for this post.
      • #2350248

        I had to take a few more steps: in the right panel under your computer’s name, open up “More Actions,” select “Properties,” and open up the “Drivers” tab. Then you will see a list of installed printer drivers and their type. In my case, my Dell printer is Type 3 as are doPDF 7 and PrimoPDF. Microsoft Print to PDF and Send to Microsoft OneNote 16 are Type 4.

    • #2350157

      Corrected screenshot.

      Seems my Laser Samsung AIO is PCL3 so no kb5000802 for now.

      • #2350165

        Seems my Laser Samsung AIO is PCL3 so no kb5000802 for now.

        But it says Type 4, which is not affected.

        Windows 11 Pro version 22H2 build 22621.1778 + Microsoft 365 + Edge

    • #2350185

      Seems my Laser Samsung AIO is PCL3 so no kb5000802 for now.

      But it says Type 4, which is not affected.

      The Samsung printer is type-3. 🙂

    • #2350254

      I purchased a Dymo LabelWriter 450 Turbo a couple of days ago and got around to installing it hours ago. When I went to the Dymo website to register the product and download the Dymo software the following message was displayed atop their website:

      “DYMO Software compatibility issues with Microsoft Windows Update.

      The latest version of DYMO Connect and DYMO Label Software is not compatible with Microsoft’s recent Windows update and consumers may have user experience issues. Please follow the instructions available here to solve the issue of printing blank labels.
      Thank you for your understanding and our sincere apologies for the inconvenience caused.”

      The solution is either (1) uninstall the March Win10 update, or (2) uninstall the latest version of the Dymo software and install an earlier version, a link for which is provided. Even though I had not installed the Win10 update (we are in Defcon-1, after all).  I downloaded and installed the older Dymo version. I then successfully printed out a label.

      Now I don’t know what would have happened had I installed the March update to Win 10 Pro (2004) and the newer Dymo software version. Does “user experience issues” mean a BSOD? I dunno. But you can add Dymo to the list of printers experiencing issues caused by the update.

      • This reply was modified 2 years, 2 months ago by MikeyD215.
    • #2350313

      Seems my Laser Samsung AIO is PCL3 so no kb5000802 for now.

      But it says Type 4, which is not affected.

      It says Type-3 which is effected.

    • #2350481

      Many thanks! That was certainly intuitive…, NOT! 😉

      That was my issue too, so thanks — I feel slightly less dumberer 🙂

    • #2350509

      Since this is my first post I’ll keep it quick so I don’t make a rookie mistake. I hadn’t updated my Win 8.1 since January so a few days ago I started the process. I’m usually very careful and look up every update. I do this because I know just enough to mess things up. I figured January or February security roll ups would show up first. Well March roll ups appeared and I inadvertently installed KB5000848. I didn’t install KB4535680 as suggested. I expected some adverse conditions to pop up but so far no change in performance. I’m not savoy enough to troubleshoot my critical errors but I do try. I share this only because of the DEFCON status.

      I have an all in one HP which I’m retiring next month. Any suggestions for a new rig? I’m not a gamer but I do tones of research that requires multiple screens and open tabs and programs.

      Thanks for your patience,

      John L

    • #2350854

      I thought I was having a similar, but less severe, same issue with my two Brother printers. After patching, Windows thought they were offline and I couldn’t get them back.

      But on further checking, it seems that after applying the patches my system somehow switched from my primary wireless network to a guest network that cannot access the printers.

      The same thing happened with the June patches, I believe

      Reconnecting to the primary wireless network solved the problem.

      Any other reports of this variant?


      Don Brownlee

      Montclair VA

    • #2350990

      Microsoft has released out-of-band emergency updates to fix BSODs (error APC_INDEX_MISMATCH) caused by the March 2021 Patch Tuesday updates when printing to certain printer brands, including Kyocera, Ricoh, and Dymo. See Sergiu Gatlan’s 15-Mar-2021 BleepingComputer article Windows 10 Emergency Updates Released to Fix Printing Crashes for more information. According that article emergency updates have been released for multiple Windows OSs from Win 10 v1803 Enterprise to Win 10 v2004/20H2.

      Kudos to bjm_ for posting a link to this BleepingComputer article <here> in the Norton Tech Outpost board.
      64-bit Win 10 Pro v2004 build 19041.804 * Windows Defender v4.18.2102.3

      1 user thanked author for this post.
    • #2351063

      Has any one hit by March updates installed the “fix” ? Did it fix the BSOD/printing bug ?

      • #2351072

        No problem with anything so far…

        • #2351151

          Did you install the fix? Were you getting BSODs? Did the fix fix the problem?

          cheers, Paul

          • #2351153

            Never had any to begin with, and I have a Dymo label printer…

            • #2351375

              The reason you had no problem to begin with probably is because you may have been using an older version of the Dymo software, which was not affected by the March 2021 Windows update. Recall that Dymo’s workaround was to install an older version of the DYMO Label software.

            • #2351389

              Version to be exact…

            • #2352561

              Consider yourself lucky!  To be fair, we only encountered issues with the Dymo’s if we used their software directly.  That or, in our case, a custom program using the Dymo SDK that prints a label by essentially running it through said software.  In those cases, a blank label was produced.  If we printed direct via Windows via the Dymo printer driver, it was fine.  Unfortunately, everything relied on that custom program so we were hurting pretty badly until Dymo released 8.7.4.x.

              The problem we are facing now is that our ERP is suffering a massive speed drop after the February patches were released.  The Epicor community was patiently waiting for the March updates to **hopefully** address that problem.  WRONG!  Just added BSOD and printing issues to the mix.

    • #2351377

      Dymo is now offering new versions of its software that will solve the BSOD issue in most instances. Here is notice from their download website–

      “The latest Windows update has caused some issues with printing from our software. Our team has been able to fix the issue of printing blank labels from our DYMO Connect and DYMO Label Software by introducing a new update. In order to run the latest software update, please open DYMO Connect, click “Help” > “Check for Updates” and download the latest version. Alternatively, you can download the newest version of our software here. In order to download the latest DYMO Label software update click here.

      Please be informed that the update did not fix the issue of printing blank labels from our latest versions of DYMO ID (XTL). You can still use our software, if you follow the instructions here.”

      1 user thanked author for this post.
    • #2352553


      Are the instructions in post #2350096 supposed to work on Windows 7 as well as 10?

    • #2352817

      My HP Officejet J3600 series printer has a type 3 driver.

      I’ve also found that the Microsoft XPS Document Writer uses a type 3 driver.

      Is there any way to test if my system is part of the effected subset before the March patches are installed?

      Would installing the blue-screen fix hurt anything even if it wasn’t necessary?

      • This reply was modified 2 years, 2 months ago by Moonbear.
    • #2352894

      We are at DEFCON 1, do not patch.

      Having said that, if you want to test, make an image backup and apply the patches, then let us know if it’s OK.

      cheers, Paul

    Viewing 39 reply threads
    Reply To: MS-DEFCON 1 – Blue screens of death triggered by patches

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: