March madness drives printers to blue screen

Topic

New Reply

PATCH WATCH By Susan Bradley The month of March is not starting off well for those of us who patch Windows 10 machines. Patchers who have installed th
[See the full post at: March madness drives printers to blue screen]

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

lmacri, erbkaiser, abbodi86

Reply | Quote

Replies

About “March brings the end to legacy Edge” – it puzzled me why Internet Explorer is installed on Server 2016. Do you really need a web browser on a server? OK, suppose you really do – then you want that browser to be IE? Don’t think so. But Edge isn’t offered as update; according to Microsoft: The Long-Term Servicing Branch (LTSB) versions of Windows, including Windows Server 2016, don’t include Microsoft Edge or many other Universal Windows Platform (UWP) apps. These apps and their services are frequently updated with new functionality, and can’t be supported on systems running the LTSB operating systems. For customers who require the LTSB for specialized devices, we recommend using Internet Explorer 11.

Hmm, ‘don’t include Microsoft Edge or many other UWP apps’. Really? Then why are there Xbox-services installed?

This is something I stumbled across this week: “…update history after the system rebooted and did not find that update listed.”. I had installed the much-talked-about Exchange patch, but when I checked Update history under Update & Security, it wasn’t there. So I checked ‘ye ole Control panel > Programs & Features > View installed updates and sure enough, there it was.

Reply | Quote

Xbox services junk comes preinstalled with LTSB?!?!

Reply | Quote

Sorry for offtopic, but no, LSTB does not come with Xbox apps. Services maybe, but you can disable them. The only Xbox thing on LSTB is built-in Xbox control panel, which is present in every Windows 10 installation, I think. LSTB comes only with “productive tools”, no bloatware like Candy Crush Saga.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

1 user thanked author for this post.

Save_Us_from_MS

Reply | Quote

Interesting experience. Today I ran into the BSOD with APC_IDEX_MISMATCH stop code (first in our company since the patch was instaled last week). So I went to

‘ye ole Control panel > Programs & Features > View installed updates

Where it should be listed, and I uninstalled the faulty patch.
Then I tried to print again and it works. In the history, there is still mentioned that I installed KB5000822 on 10th of March, but its not listed in the old control panel anymore.
Be aware, that there could be difference in those two control panels. Old control panel shows what updates that are installed now. New control panel shows the history (lets say log) of your updates.

I must check the xbox app in LSTB on our production machines, I dont think, there is much bloatware with LSTB.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

[EP]

what kind of printers do you have, doriel?

I do NOT seem to have the blue screen problem with my LTSC 2019 machine after installing KB5000822 manually from MS catalog and I’m using only certain HP brand printer models (ex. HP Envy 4500 and HP Envy Photo 7800 series)

• This reply was modified 2 years, 6 months ago by EP.

Reply | Quote

We have Zebra ZT410, Zbra ZM400 and Zebra ZD620 and Kyocera 3055 and 3155.
BSOD was happening only on one computer in our company. So I uninstalled this buggy update and it seems OK now.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-20h2#1570msgdesc

“Next steps: We are working on a resolution and estimate a solution will be available in the coming week.”

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

This note about a patch was updated last Friday (3/12).  So “upcoming week” should be this week

Reply | Quote

new Win10 updates Susan and sheldon released Mon March 15 2pm pacific local time on MS Catalog:

KB5001567 for Win10 v2004/20H2
KB5001566 for Win10 v1909
KB5001568 for Win10 v1809 enterprise/education/LTSC 2019
KB5001565 for Win10 v1803 enterprise/education

MS support articles soon to be published

Reply | Quote

https://www.bleepingcomputer.com/news/microsoft/emergency-windows-10-updates-released-to-fix-printing-bsod-crashes/

“The cumulative updates containing the fix released today are published as optional updates so they will not be installed automatically via Windows Update.”

If you broke me automatically, you should fix me automatically.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

mcbsys, Alex5723

Reply | Quote

So, if we are waiting for DEFCON 3+ to install the March updates, what does this mean? The info for KB5001566 says “If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.” I still have KB5000808 (for Version 1909) still waiting in wushowhide (it was never pulled), so that means I haven’t installed the ‘earlier update.’ and so KB4001566 is of no use until I do.

I don’t know whether my Dell printer is affected by the problematic update or not, since I haven’t installed the faulty one. But, I clearly don’t want to install it to find out, when DEFCON 3+ arrives. And, I don’t want to wait until I install the April patches to get whatever else was in KB500808 that was working.

And I don’t know if this issue is further complicated, because I was planning on upgrading to 2004, when DEFCON is 3+ for the March updates.

Reply | Quote

Win10 patches are cumulative. If you install KB4001566 manually, it contains KB500808 plus the fixes.  You do not have to install KB500808. You should have Build 18363.1441.

If you upgrade to 2004, it will depend on which Build is installed, whether or not you have to install the OOB CU. If it’s the March Build 19041.867, then you will need the fix. If it’s 19041.868, you are OK.

2 users thanked author for this post.

WCHS, Alex5723

Reply | Quote

I read the negative of the statement to mean “if you didn’t install the faulty update, then the new fixes in KBKB4001566 will not be downloaded and installed on your device,” i.e., an exception in this case — the CU is not cumulative. But, you’ve explained it well for me.

PKCano wrote:

If you upgrade to 2004, it will depend on which Build is installed, whether or not you have to install the OOB CU.

When I change TRV to 2004, is it the luck of the draw as to whether I get 19041.867 or 19041.868?

Reply | Quote

On my 20H2 installation, I was being offered 2021-03 KB5000802 March CU from Patch Tuesday in the WU queue.
I downloaded 2021-03 KB5001567 March OOB CU with printer fix.
I manually installed KB5001567 manually.
On reboot, KB5000802 was no longer in the WU queue and winver reported v20H2 Build 19042.868

The patches are cumulative.

2 users thanked author for this post.

ECWS, WCHS

Reply | Quote

What happened to the microcode KB4589212? I have the 1909 correlate (KB4589211) hidden and it would be ideal if I could keep KB4589212 hidden.

Reply | Quote

Oh, I hid that one before I started (so it disappeared too as well:-) ) and the Defender update was faster installing than I could capture the shot, but I didn’t think either was pertinent to the demonstration.

1 user thanked author for this post.

WCHS

Reply | Quote

@WCHS –

After your machine reboots and finishes the 2004 installation and you’re back at your desktop, I would immediately run wushowhide to hide KB4589212, so WU doesn’t even get so much as a sniff of it.

However, I don’t know if WU will try installing it during the upgrade from 1909 to 2004 instead.

@PKCano or any of the other MVPs here: Do you have any insight on this concept…will WU try installing KB4589212 during the upgrade process even though its 1909 equivalent has been hidden by @WCHS  or will it be possible to hide it after WU finishes the upgrade from 1909 to 2004?

Reply | Quote

Susan, I am not getting printer BSODs. Well, not yet. But both a client and I had our little Dymo printers print blank labels, instead of usable ones. I removed KB5000802 for client’s system and mine after asking myself what had changed, when I was told that client’s Dymo worked the day before. This is with Windows 10 Pro Version 2004, because I do not want to subject my production system to 20H2… Ben Myers

Reply | Quote

Dymo is also having issues

https://www.dymo.com/en-US/software-fix

Solution 2: Downloading and installing our DYMO Label Software v.8.5.4.

You can install the older version of DYMO Label Software to be able to use your DYMO printer.

Important note about the version 8.5.4:

• It is not compatible with the LabelWriter Wireless printer. In case you have LabelWriter Wireless, please see Solution 1 above.
• You will not be able to open your saved labels created in the latest DYMO software versions.
• Make a copy of labels saved in ‘Documents’ folder in order to use them when the issue is resolved.
• The Address Fixer tool (US only) will not work.

Please follow the steps below:

1. Go to Control Panel > Programs > Programs and Features, right-click on DYMO Label Software or DYMO Connect Software > Select uninstall.
2. Use the following link to download and install the previous version of the software:

DYMO Label Software 8.5.4

Alternative link: DYMO Label Software v.8.5.4

 

Thank you for your understanding.

A permanent solution will be introduced shortly.

We sincerely apologize for all the inconvenience caused.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Well, yes, Dymo is having issues, because I am having issues with two computers running Win 10 Pro 2004 and Dymo printers attached.

Dymo may be aware of the problem with the March 2021 update to Win 10 2004, but they get no kudos.

The suggested Dymo solution of going back to an earlier version may not work, because Dymo also states that it has changed the format of its address book.  Oh, joy!  And with which release of the Dymo software did it change?  Dymo is moot here, so I backed out KB5000802 and tested my client’s Dymo printer again and it worked.  So there is my workaround, no matter what Dymo says.

What I now see is that the Dymo driver interface to its USB printers is different from the usual driver interface.  Except… What printer uses a “standard” interface nowadays?  Most every set of printer drivers is cobbled up with add-ons to promote their consumables.  HP inkjet drivers are the worst for their bumbling complexity… Ben Myers

1 user thanked author for this post.

SkipH

Reply | Quote

I have not installed KB5000802 yet. So glad I not because just checked my printer driver type per link below and found I have Type 3 printer drivers, not Type 4. Type 3 is the one that causes then BSOD.

In addition, I have a middle of road Brother B&W laser printer DCP-L2540DW and Brother printers were NOT mentioned as ones affected by the patch bug.

I know a fix has been released even now via the windows update screen, but will still hold off a while.

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-20h2#1570msgdesc

Has anyone checked your printer driver type?

Reply | Quote

I am running Win 10 Pro 20H2 and I have an HP ENVY 5640 printer attached via USB.

The HP ENVY 5640 printer driver is shown as Type 3.

Microsoft said that the APC_INDEX_MISMATCH crash related to only a subset of Type 3 drivers but did not specify which subset.

I delayed installing KB5000802 until the fix (KB5001567) was released.

After installing KB5000802 I have printed a couple of pages without getting a crash and the printout looks OK.

I was offered KB5001567 as an optional update but have not installed it as things seem OK without it so far.

However I notice that there are reports that some people are still having some printing problems after installing KB5001567:

https://borncity.com/win/2021/03/17/windows-10-weiterhin-probleme-mit-der-druckausgabe-mrz-2021/

AP

Reply | Quote

On my Win10 20H2 with 3-day update deferral, neither KB5000802 nor KB5001567 have been offered so far. I’m guessing they pulled the first one within three days and I won’t see the second until it has been out for three days.

Meanwhile, Server 2016 with 3-day deferral has been bugging me for several days to install KB5000803. Was this update not affected by the printer bug? I don’t see an out-of-band patch following KB5000803.

I want to patch these in-house systems soon so I can verify stability before patching customers’ systems.

Reply | Quote

[mcbsys]

Correction:  on my 20H2 with 3-day deferral, KB5000802 did install overnight on March 12; I just didn’t notice. The KB4589212 Intel microcode update installed itself and rebooted on March 17. KB5001567 is not offered even when I manually Check for updates. Why not?

• This reply was modified 2 years, 6 months ago by mcbsys.

Reply | Quote

KB5001567 is not offered even when I manually Check for updates. Why not?

Because KB5001567 has been issued as an Optional update, from what Susan and others have said in their posts above.

So, launch WU, but click on the “View optional updates” link below the “Check for updates” button.

Some have also suggested setting Feature Updates to Not configured and TRV to Not configured as well in Group Policy.

Reply | Quote

With the fix from Microsoft for the BSOD/Printing bug and no other known bugs isn’t time for Defcon-3 ?

Reply | Quote

According to findings over on borncity there are still issues.

Can’t confirm that it works. A customer of ours with 6 clients. 5 out of 6 installed this this morning and the problem with the printers (Kyocera in that case) still persists.

No problem can be solved from the same level of consciousness that created IT- AE

2 users thanked author for this post.

Geo, Alex5723

Reply | Quote

On Win 10 20H2 x64 Pro, and I have not been seeing the new patch for the printer fixes in wushowhide, NOR have I seen it in WU itself.

Well, I think I know why. Although it doesn’t say so as a prerequisite in the KB article, you have to have the normally issued update installed in order to see the revised update. In other words, I think you have to have the update issued on the 9th of March installed in order to see the new patch that was issued on the 15th.

Since I don’t have the original patch for 20H2 for March installed (KB5000802), I’m not seeing the revised patch offered in either WU nor in wushohide. Unhiding KB5000802 had no effect in wushowhide as far as revealing the new patch for the month, despite the fact that it’s listed as superseding the earlier patch in its KB article. After rehiding KB5000802, I “forced” WU to run, and it didn’t find the new update either, not even listed as an Optional update.

All of this testing was done with Quality Update deferrals set to 0 (zero) in Group Policy.

So, for those of us running Windows 10 who haven’t yet installed the March 9th update, we’ve got two choices: 1. Install the March 9th update when DEFCON goes to 3 or higher and see if we can print afterwards, installing the newer March patch if needed or, 2. Manually d/l the March 15th patch using @EP ‘s links provided above and manually install the revised update instead of using WU to install it when DEFCON reaches 3 or higher.

I downloaded the March patch from the Catalog and am patiently waiting for DEFCON 3 or higher to install it. Since both of my computers have HP printers with type 3 drivers, I’m not taking any chances.

Reply | Quote

Bob99 wrote:

On Win 10 20H2 x64 Pro, and I have not been seeing the new patch for the printer fixes in wushowhide, NOR have I seen it in WU itself.

Well, I think I know why.

The new patch, KB5001567, is an optional update. Do you have GP Windows Update for Business | Select when Preview Builds and Feature Updates are received | Semi-Annual Channel = 0 or 1 days? If so, this is likely why you don’t see it.

I am still on 1909 (with TRV=1909) and I have the corresponding Advanced options/GUI setting for Feature Updates. I don’t see the new patch either. But, with this setting I never see optional updates. See post by @abbodi86 – #2309326

Reply | Quote

[ECWS]

Installed KB5000802 then uninstalled it after reading about the printer issues and noticing I had some printers at Type 3.

Placed a 7 day hold then removed it after reading about PK Cano’s experience #2351114 with installing the update KB5001567.  Both KB5000802 and KB5001567 were available for update.

Updated KB5001567 and the update for KB5000802 disappeared.

Winver is Pro10 20H2 Build 19042.868

• This reply was modified 2 years, 6 months ago by ECWS.

Reply | Quote

Both KB5000802 and KB5001567 were available for update.

Was that within Windows Update or was that within wushowhide or one of the other update management tools?

Reply | Quote

An OoB printer fix has been issued by MSFT for those who are currently having issues with installed March 2021 patches.

KB5001639 for Win7 & Server 2008 R2
KB5001640 for Win8.1 & Server 2012 R2
KB5001641 for Win8 embedded & Server 2012
KB5001642 for Server 2008 SP2

More info over on bleepingcomputer

No problem can be solved from the same level of consciousness that created IT- AE

2 users thanked author for this post.

PKCano, doriel

Reply | Quote

AKB2000003 has been updated for both Win7 and Win8.1

1 user thanked author for this post.

Microfix

Reply | Quote