March patching madness begins

Topic

New Reply

It’s that time of the month that I take a quick look at the patches that are released to see if there are any that I think we need to quickly act on.
[See the full post at: March patching madness begins]

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

lmacri, WShstruve, jburk07, Seff

Reply | Quote

Replies

AKB 2000003 has been updated for Group B Win7 (ESU) and Win8.1 on March 9, 2021.

There is a Security-only Update for those with Win7 ESU subscriptions.
There is a March IE11 CU  KB5000800 for Win7. Download 32-bit or 64-bit.

March Rollup KB5000841 Download 32-bit or 64-bit. for those with Win7 ESU subscriptions.

You must have at least the August Servicing Stack KB4570673 previously installed to receive these updates).
The latest is the December Servicing Stack KB4592510 – Download 32-bit or 64-bit for those with Win7 ESU subscriptions.

There is a revised Licensing Preparation Package KB4575903 dated 7/29/2020 for Win7 ESU subscriptions, if you need it.

There are .NET updates listed for Win7. See #2349123.

 

****UPDATE: On 3/22/2021, Microsoft released a fix for printer issues caused by the March Patch Tuesday updates.
Out-of-Band update KB5001639 – Download 32-bit or 64-bit.
.

6 users thanked author for this post.

L95, Microfix, jburk07, woody, SueW, abbodi86

Reply | Quote

For the 5th month in a row after EOL in October 2020, Office 2010 got updates again. Five security updates have been released. It makes me wonder why and how long they will continue doing this (if so). I thought that after 3 months MS would certainly stop, but no.

3 users thanked author for this post.

L95, Microfix, jburk07

Reply | Quote

You and me both. Some large company somewhere is still getting updates and needs them badly.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I remember someone here telling me two or three months ago (when I registered surprise that Office 2010 updates were still appearing) that it was completely normal and what had happened with previous EOL products.

I wonder if they still feel the same way. It still seems odd to me, but increasingly so with every passing month.

Reply | Quote

No, Office 2010 case is very unusual

for what it worth, Windows Embedded Standard 7 was silently extended (without ESU) from January 2020 till October 2020

3 users thanked author for this post.

L95, Pim, jburk07

Reply | Quote

Govt departments/ public services/ medical services for reliability and security without the cloud guff. There’s a lot of clout in local/ national authorities worldwide.

If debian is good enough for NASA...

1 user thanked author for this post.

Pim

Reply | Quote

I received four new Office 2010 updates and one Visio update.  I’m not complaining.

Being 20 something in the 70's was far more fun than being 70 something in the insane 20's

Reply | Quote

Neither am I 😉

Reply | Quote

Got the Malicious Software Removal Tool and
KB4589212 Update for Windows 10 Version 20H2 for x64-based Systems
KB5000802 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems

There was a hiccup between KB4589212 and KB5000802.  After it stalled and I rebooted, I launched Windows update again and clicked Retry.  It was smooth the second time around.

Other than that, all systems nominal.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

My NAS got the push last night.  All systems nominal.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

bbearren wrote:

There was a hiccup between KB4589212 and KB5000802. After it stalled and I rebooted,

For me too March 2021 patches installed with a little hiccup. Windows Update reported a KB5000802 download error.

I did not reboot, but just hit [Retry]. From then on everything proceeded normally.

Up to now no issues that I can see.

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)

Reply | Quote

2021-03 Security Monthly Quality Rollup for Windows 8.1 (KB5000848) is pulled from WU

4 users thanked author for this post.

JD, PKCano, Microfix, DrBonzo

Reply | Quote

I see a revision 200 in WSUS tonight so it may just be a detection issue.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

[abbodi86]

2021-03 Security Monthly Quality Rollup for Windows 7 (KB5000841) is pulled from WU

KB5000822 (17763.1817) also pulled
apparently the found bug is epidemic

• This reply was modified 4 years ago by abbodi86.

2 users thanked author for this post.

Pim, PKCano

Reply | Quote

But the two patches for Win7/8.1 haven’t been pulled from the Catalog. ????

Reply | Quote

One thing I found that is odd, is the catalog name date/tags?!!
Affected are Win7/ Server 2008 NET Framework patches.

These should start with 2021-03, instead of 2021-02 (February)

Looking in the MS Catalog under February 2021-02 displays MARCH updates once re-arranged by Last Updated.

If debian is good enough for NASA...

Reply | Quote

[PKCano]

I noticed the “2021-02” designation yesterday (3/9) on the Ghacks information and wondered about it.
I patched my Win8.1 yesterday through WU and it shows “2021-03.” Had no problems this morning.

• This reply was modified 4 years ago by PKCano.

Reply | Quote

yeah informed Martin who has now corrected the issue quicker than MSFT 🙂

If debian is good enough for NASA...

Reply | Quote

The “2021-02” is not wrong 🙂
the rollup belong to February, it’s not new
they just fixed issue with digital signature of the files

Reply | Quote

The new Rollups (i.e. new Update ID) were pulled because they were causing frequent detection issue for .NET 4.6-4.8 patches (KB4579977 keps getting re-offered)

so they added the updated binaries to the old Rollups (i.e. old Update ID), which maintain their original titles, regardless revision date

see

abbodi86 wrote:

Both refreshed rollups pulled

however, the updated files were added to the old rollups: 2021-02 (KB4603002), 2020-10 (KB4579977)

1 user thanked author for this post.

Pim

Reply | Quote

These are the same .NET updates that have been released in February, but were rereleased yesterday. Maybe that is the explanation? However, this update appears as “2021-03” in WU, if you hadn’t installed it before.

I did notice an even weirder case though. KB4579977 in the catalogue: “2021-10” for Windows Server 2008 R2! Apparently MS can now time-travel 😉

Reply | Quote

See #2349123.

1 user thanked author for this post.

Pim

Reply | Quote

Thanks. I had just read that post and was editing mine because of it, as you wrote yours. However, “2021-10” for Windows Server 2008 R2 is definitely a typo (see attached picture in my previous post).

Reply | Quote

Well, that’s Microsoft for you! 🙂

Reply | Quote

The typo don’t appear in English UI of the catalog

1 user thanked author for this post.

Pim

Reply | Quote

Huh, that’s weird. I would expect that the month is language independent. I guess it’s not.

Reply | Quote

[Bob99]

For those interested, KB4589212 is one of the microcode update patches for Windows 10 all versions from 1507 on. It showed up in the list of available patches to hide, and I promptly hid it where it will stay.

Although MS tried giving it to me, my research indicated that I didn’t need it, as my CPU wasn’t listed at all in any of the revised Intel bulletins nor in the lengthy list that Microsoft provides in KB4589212.

SO, before blindly accepting it and trying to install it, make darn sure it’s really for you…DON’T blindly take Microsoft’s “word” for it. Installing microcode that’s not meant for your individual processor doesn’t sound like a great idea to me, especially when the maker of you processor even says your processor doesn’t need the revised microcode.

 

• This reply was modified 4 years ago by Bob99. Reason: added the fact the patch is for Windows 10

Reply | Quote

Bob99 wrote:

Installing microcode that’s not meant for your individual processor

My CPU, an i7-4810MQ, is NOT listed in KB4589212, though the i7-4800MQ is.

Now you tell me I should NOT have installed and then ruthlessly hidden microcode patch KB4589212.

There’s just a little problem: I saw and see NO option to reject and hide KB4589212.
I have NO list of available patches to hide, nor any way to hide patches.

Confusing, isn’t it?

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)

Reply | Quote

Is the device’s OEM issuing any Firmware updates that may include the Intel micro-code patches there. Business laptops tend to get more OEM Love for Firmware updates and that firmware usually includes more up to date Intel Micro-Code there. But at least Windows 10, like Linux Always has, is got that Micro-Code via the OS shim update capability whereas 7/8.1 do not have an easy method of end user micro-code shimming available.

Reply | Quote

Bob99 wrote:

For those interested, KB4589212 is one of the microcode update patches for Windows 10 all versions from 1507 on. It showed up in the list of available patches to hide, and I promptly hid it where it will stay.

Strange … KB4589212 is listed in the MS Catalog, but only for 2004 and 20H2.

However, I am still on version 1909 and I found it waiting to be hidden in wushowhide.

1 user thanked author for this post.

Microfix

Reply | Quote

not paying attention: wushowhide has it as KB4589211 for 1909.

Reply | Quote

KB4589212 is for 2004 / 20H2

For Intel Microcode updates for other Windows 10 versions, see the following articles:

KB4589198: Intel microcode updates for Windows 10, version 1507

KB4589210: Intel microcode updates for Windows 10, version 1607 and Windows Server 2016

KB4589206: Intel microcode updates for Windows 10, version 1803

KB4589208: Intel microcode updates for Windows 10, version 1809 and Windows Server 2019

KB4589211: Intel microcode updates for Windows 10, version 1903 and 1909, and Windows Server, version 1903 and 1909

Reply | Quote

I’m stuck at 19042.844 20h2 but windows update is not offering me the KB5000802  update.

Any ideas?

Reply | Quote

Update has been pulled due to BSOD, printing problems

Reply | Quote

KB5000802 update is still being offered thru WU on my father’s Toshiba laptop running Win10 home edition version 2004 (not 20H2).

so KB5000802 is NOT pulled completely

Reply | Quote

Perhaps this post would explain why your daddy’s toshiba is still seeing it.

Reply | Quote

[Berserker79]

Windows 10 Home version 20H2 here (build no 19042.804) and I am not seeing KB5000802 either so far.

According to wushowhide I’m currently offered the microcode update (KB4589212), MSRT v5.87 and a trio of “Intel System” updates. Oddly enough, the Intel System updates keep showing up as “unhidden” even if I marked them for hiding in three consecutive wushowhide scans.

Does anyone know if there us a way for Windows 10 Home users to entirely skip the offer of these drivers (Intel Systems, etc.) through Windows Update? According to post #2349147 the answer is to use WUmgr or WUmt to hide driver updates.

• This reply was modified 4 years ago by Berserker79. Reason: Found answer to my own question in other thread ^^;

Reply | Quote

See my post for a possible explanation.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

Reply | Quote

Beware of the Windows 10 security updates. MS is patching a printer vulnerability again (first patch was in Dec. 2020). I received massive reports, that these updates are causing BSODs on printing. Reinstalling the printer driver should fix it – I’m not sure, if the updates are pulled (some users reporting, that the updates are no more offered, but there is nothing mentioned from MS).

Windows 10 Updates KB5000802/KB5000808 causes BSOD when printing

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

5 users thanked author for this post.

WCHS, Microfix, lmacri, Berserker79, Alex5723

Reply | Quote

KB50000808 breaks printing from Dymo label software (v8 and latest version).  Labels come out blank.  Removing KB restores functionality.

1 user thanked author for this post.

Microfix

Reply | Quote

KB5000802 update also breaks all the Kyocera Drivers. Only way to fix is to remove the update. What happens if you go to print and it’s tries to go to print preview windows crashes with blue screen of death and unhappy face  🙁

Need to pause updates to keep this from happening. I updated every form of Kyocera driver and this is the only fix.

Reply | Quote

Berserker79 wrote:

Oddly enough, the Intel System updates keep showing up as “unhidden” even if I marked them for hiding in three consecutive wushowhide scans.

Known bug. Move to WUmgr / WUmt. Hidden updates remain hidden.

1 user thanked author for this post.

Berserker79

Reply | Quote

Thanks for your reply Alex. Is there any particular reason to prefer WUmgr or WUmt over the other? Or any of them will do?

Reply | Quote

wushowhide still works as always. But the MS download site was SHA-1 and they have removed it  (SHA-2 for everything now). So you can download wushowhide from OlderGeeks.com or MajorGeeks.com. It’s the same thing.

Or you can use WuMgr as Alex suggests.

Reply | Quote

Thanks for the information PK. Actually, I already have wushowhide (and use it regularly as part of my ‘patching process’), but for some reason it seems unable to hide two “Intel System” updates that are currently offered to my system. My question following Alex’ post was whether I should give preference to WuMgr (Update Manager for Windows) or WUmt (Windows Update MiniTool) between these two.

Reply | Quote

I’m being offered the MSRT v5.87 (KB890830) as well as an Intel microcode update for v1909 (KB4589211). Since my CPU’s codename is mentioned within the update, is it worth installing it (at a later date) or should I just hide it?

Reply | Quote

I understand that the general consensus here is not to install the microcode updates even if your CPU is mentioned within the update. At this time I’d simply hide it, but before deciding whether to install it (or not) at a later time I would wait for some of the more experienced users here to drop their view on this.

2 users thanked author for this post.

Coldheart9020, LHiggins

Reply | Quote

If you do install them and don’t want to uninstall them, especially on consumer machines I recommend using the https://www.grc.com/inspectre.htm to disable the impact.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

jburk07, Coldheart9020

Reply | Quote

March cumulative update has been pulled by Microsoft, they wreck systems on a large scale with bsod’s, printer related once again. If you’re one of the unlucky ones that did get the update: uninstall it asap. Total messy mayhem once again.

1 user thanked author for this post.

jpkage

Reply | Quote

Anyone seeing issues printing out labels from DYMO printing software post updates?  Label comes out but it’s blank after several of our corporate machines ran updates last night.  Windows printer test page works though?!?

Thanks,
Josh

Reply | Quote

The behavior of getting blank labels from a Dymo printer after installing the March update is documented in a post just above here. Post number 2349356. The solution is to uninstall the latest update for March. Although that post mentions KB5000808 specifically, the same probably holds true for KB5000802 as well. As of this writing, both patches have been pulled by Microsoft for printing problems that have caused Blue Screens Of Death for many machines, as documented in several posts just above this one.

Reply | Quote

I’ve come across two machines already that have bugchecked with an APC_INDEX_MISMATCH error in win32kfull.sys after installing KB5000802.

Reply | Quote

Oh No! The dreaded August 2015 anti-malware platform update for Windows Defender in Windows 8.1 and Windows 8 (KB3038936) patch has appeared as an “Important” update after installing the March 2021 patches.

Anyone else get this…. should I ignore it?

Reply | Quote

On Win 10 2004 and only update i get offered is the Malicious Removal Tool. There not a cumulative security update this month?

Reply | Quote

There is an update that’s been offered for this month, but it has been pulled by Microsoft due to causing problems after being installed. The problems amount to not being able to print…if you try to print, Windows crashes and then reboots. Please see the majority of the posts above for further info.

Hopefully Microsoft will figure this out in the coming days or weeks to enable us to successfully install an update for this month that won’t crash our computers, especially since this month’s update was supposed to patch a security vulnerability in Windows 10 that’s currently being actively exploited!

Reply | Quote

It appears servicing stack updates (SSUs) are now included in the monthly cumulative updates according to the March CU description.

Is this correct?  Does this mean there are no more standalone SSUs?  Can CUs still be downloaded and installed manually from the update catalog without a separate SSU being installed first?

Reply | Quote

The newer releases (2004/20h2) now include the SSUs in a single bundle. I would not recommend ever installing a CU without a SSU first on the Windows 10 platform. Note that if you patch via Windows update all this sorting/order of patching is done for you.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

See #2346916

Reply | Quote

Thanks.  Just to clarify…if I have the latest standalone SSU (from January 2021) installed, there will no longer be any separate SSUs in the update catalog.  I could manually download the monthly CU and it will automatically install any SSU changes from that single file.  Is that right?

Reply | Quote

[Alex5723]

Berserker79 wrote:

Thanks for your reply Alex. Is there any particular reason to prefer WUmgr or WUmt over the other? Or any of them will do?

I personally prefer WUmgr. You can test both. Both are portable.

• This reply was modified 4 years ago by Alex5723.

1 user thanked author for this post.

Berserker79

Reply | Quote

Windows 10 updates are back to WU
or maybe for those without printer only

1 user thanked author for this post.

Berserker79

Reply | Quote

Monthly Rollup for Windows 8.1 (KB5000848) / Windows 7 (KB5000841) are back to WU too

Reply | Quote

so is KB5000802. I’m recently receiving it thru WU running Win10 home v2004 (build 19041.844)

Reply | Quote

Windows 10 Home 20H2 and today I’m offered KB5000802 through WU. I have a Samsung printer connected to my computer, so it seems the offer is not limited to those without printer only. Anyway, I’ve hidden the patch pending Susan’s all-clear to install.

Reply | Quote

Like  @Berserker79 with a printer connected, I have a two computers (Win1o Pro, version 1909) with a Dell printer connected.  I received KB5000802 through WU on March 9.   It’s still hidden in wushowhide, although WU has already refreshed twice — which is to say it hasn’t been pulled on my machines.

Reply | Quote

Berserker79 wrote:

Oddly enough, the Intel System updates keep showing up as “unhidden” even if I marked them for hiding in three consecutive wushowhide scans.

Dump wushowhide.
Move to Wumgr / WUmt.

Reply | Quote

Thanks. I switched to Wumgr, it seems this tool has been more recently updated than WUmt and it works pretty nicely as far as I can tell. It sure is way more quicker with hiding patches compared to wushowhide, it just takes a click to do it compared to the several minutes of tinkering that it takes wushohide to hide (or unhide) patches.

Reply | Quote

Don’t miss the re-released NET Framework Updates KB4579977 and KB4603002.

KB4579977 = 2020-10 (v1) and 2021-03 (v2)
inkluded:
ndp48-kb4578977-v2

KB4603002 = 2021-02 (v1) and 2021-03 (v2)
inkluded:
ndp48-kb4600944-v2

Reply | Quote

those net updates are for Win7 and Server 2008 R2 only though

Reply | Quote

I have Win 10 Pro 64 20H2 with all previous updates (including microcode) installed on an Intel NUC8i3BEH. Attached to it are a Brother HL-L2370DM (via ethernet) and an HP Envy Photo 7130 (via WLAN).

Last night I did the March updates about 15 minutes after they came out (Berlin, Germany local time).

This afternoon I read here about the printing-related BSODs, so I tested printing on both of my machines.

I’m happy to report that both worked slicker’n snot.

Reply | Quote

I installed on a test Lenovo Laptop (old machine T530 with latest Windows 10 64 on it)

No problems with update. Printing to Brother printer worked as before.

No issues.

Reply | Quote

[EP]

posting this screenshot from my dad’s Toshiba laptop receiving the KB5000802 update for Win10 home v2004 as of Wed. March 10, 2021 at 11:46am pacific local time (for visual evidence to back my claim)

even some folks in Tenforums are also recently receiving KB5000802 thru WU as well

• This reply was modified 4 years ago by EP.
• This reply was modified 4 years ago by EP.

Reply | Quote

Quick question – in light of the DEFCON 1 – would now still be a good time to set up getting Win 10 v2004 – while all other patches are either hidden in wuashowhide or withdrawn from Windows Update? I was hoping to let my 1909 laptop get moved to 2004, but with this latest DEFCON, I wasn’t sure if that upgrade is also on hold. Thanks!

1 user thanked author for this post.

WCHS

Reply | Quote

What printer do you have? I don’t see HP printers reporting issues so if you have a consumer-ish HP you may be just fine.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Susan Bradley wrote:

What printer do you have? I don’t see HP printers reporting issues so if you have a consumer-ish HP you may be just fine

LHiggins wrote:

Quick question – in light of the DEFCON 1 – would now still be a good time to set up getting Win 10 v2004 – while all other patches are either hidden in wuashowhide or withdrawn from Windows Update?

My question was not about a printer – it is whether it is OK to try to set the laptop to get the v2004 upgrade now while we are at DEFCON 1 – and everything else is hidden from downloading? If OK I can start the process – if not, I’ll wait.

Thanks.

Reply | Quote

“It’s fine to update if you have an HP printer” seems to the the answer.

cheers, Paul

1 user thanked author for this post.

LHiggins

Reply | Quote

Today I find that .net applications can not display jpg files.

 

W7x64  ESU, I did the two .net 4.8 V2 updates followed by 2021-March Rollup.

 

Anyone else in same boat?

Reply | Quote

Which .NET applications?
Cannot display, throw an error, do something else?

cheers, Paul

Reply | Quote

I posted here with info and conclusion:

https://www.askwoody.com/forums/topic/ms-defcon-1-blue-screens-of-death-triggered-by-patches/#post-2349725

I repeat it here for your convenience:

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…

-=Paul=-

 

 

Reply | Quote

Running Win 10 Pro x64 ver 2004

Is there anyway to tell the original release of the March KB5000802 (on 3/9/21) from the re-issued KB5000802?

I received the original release and hid it via wushowhide on 3/9/21. On 3/10/21, after issues had surfaced, I checked my hidden items again and KB5000802 was gone.  I never saw another KB5000802 in my Windows Updater today 3/11/21, so I checked wushowhide again and it appears again under hidden (even though I didn’t see it or hid it a second time).

So do I have the re-issued KB or did the original decide to re-appear in wushowhide?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

1 user thanked author for this post.

WCHS

Reply | Quote

Tex265 wrote:

Is there anyway to tell the original release of the March KB5000802 (on 3/9/21) from the re-issued KB5000802?

And KB5000802 in the MS-Catalog has a release date of 03/08/2021.

I’d like to know, too. KB5000802 is still in my wushowhide, and it hasn’t disappeared. Could it be the re-issue??

Reply | Quote

It’s not different

1 user thanked author for this post.

WCHS

Reply | Quote

abbodi86 wrote:

It’s not different

Are you saying that MS issued KB5000802, had problems and pulled it, but then simply re-issued the exact same KB50008002 with no changes and no corrections of the reported problems?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Yes, nothing changed in updates binaries

the temporary “pull” was not only for KB5000802, they pulled all March updates for all Windows OSs, then republished them unchanged

4 users thanked author for this post.

WCHS, doriel, PKCano, Microfix

Reply | Quote

For clarity this was within WU and not in the catalog.

If debian is good enough for NASA...

2 users thanked author for this post.

WCHS, abbodi86

Reply | Quote

Hey my posts are lost!

Affected versions:

KB5000802: Windows 10 2004/20H2 & Windows Server 2004/20H2
KB5000808: Windows 10 1909 & Windows Server 1909
KB5000822: Windows 10 1809 & Windows Server 2019
KB5000809: Windows 10 1803 & Windows Server 1803

Source BleepingComputer

We do not use GENERIC UNIVERSAL drivers and we are all good here with KB5000822

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

We have Kyocera FS4200, P3050 and P3055. Also very lot of Zebra ZT410, ZM400 and ZD620. All have corresponding drivers from vendors installed on the printserver and no crash here, even WSUS shows, that KB 5000822 is installed on more than 90 workstations and other are qeued now.. Looks like we “survived this one”. 🙂 Wish you the same.

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

Caught in the spam bucket. You need to be more patient.

cheers, Paul

1 user thanked author for this post.

doriel

Reply | Quote

[darynman@gmail.com]

I am so grateful I found Ask Woody and all the great people here!

I am pretty sure my 3 AMD Ryzen Desktops don’t need Intel Microcode KB4589212, even though WU is determined to give it to me.

But I have the knowledge from here to avoid it.

Thanks All.

• This reply was modified 4 years ago by darynman@gmail.com.

Reply | Quote

javacat wrote:

re: W7 x64 KB5000841 March 2021 Quality Rollup …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.

Hi javacat:

I don’t know if this is relevant, but many users had a similar problem in 2020 with the iTunes store where they would see a grey box as a placeholder instead of the album art. See my 29-May-2020 post on page 11 of Gray Boxes in iTunes Store – Windows describing how a solution posted <here> by okcameradude to change the high DPI settings in the iTunes.exe properties fixed the problem for most iTunes users. It’s possible the March 2021 KB5000841 includes an update for your Win 7 graphics components that is triggering a similar problem in Album Art Downloader, so if Microsoft doesn’t fix this in a future Win 7 SP1 Monthly Rollup you might want view the properties for your Album Art Downloader executable (look on the Compatibility tab) and see if it allows you to adjust the high DPI settings for this app.
————-
64-bit Win 10 Pro v2004 build 19041.804 * Windows Defender v4.18.2102.3

Reply | Quote

Thanks for the tip.  As of this time, the compatability tab doesn’t have a “Change High DPI” button, just the older checkbox to “disable display scaling…”.  But I’ll keep this tip tucked away for future ref.

I have not heard anywhere of others with this or similar issue, perhaps it was just my bad experience, but removing KB5000841 did “fix” it, I will hold off trying that update again for 4 weeks or so and see what develops…

 

Reply | Quote

Not sure if it’s helpful or not, but I had about 10 systems in a test lab expire their WU deferrals and go get – you guessed it – the March updates.

So far not a one of them has had any problems.

-Noel

Reply | Quote

Win 10 version?  Brand of printers used?

Reply | Quote

Multiple different versions of Windows, including some 20H2.

Those systems don’t test printing. My data point implies there aren’t other problems I guess…

-Noel

Reply | Quote

Microsoft have published some more information on the printer issue:

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-2004

A couple of extracts from this:

• “This issue affects a subset of Type 3 printer drivers and does not affect printer drivers that are Type 4.”
• “We are working on a resolution and estimate a solution will be available in the coming week.”

AP

 

1 user thanked author for this post.

b

Reply | Quote

Same for other versions (1803, 1809, 1903, 1909, 20H2).

See #2350096 for workaround provided by Microsoft.

1 user thanked author for this post.

Microfix

Reply | Quote

I spoke too soon. When launching NiceLabel and opening label from network folder, I get BSOD. I can repeat this. When accessing labels from local disc, it works just fine. Hope it wont take long to release repair.

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

[John782]

Alex5723 wrote:

Move to Wumgr

If you use Wumgr, then do you still need to set a date, in the Advanced Windows’ Update Settings ( to pause WU), and use metered WiFi or does Wumgr alleviate those needs?

 

• This reply was modified 3 years, 11 months ago by John782.

Reply | Quote

[John782]

John782 wrote:

Alex5723 wrote:

Move to Wumgr

If you use Wumgr, then do you still need to set a date, in the Advanced Windows’ Update Settings ( to pause WU), and use metered WiFi or does Wumgr alleviate those needs?

 

• This reply was modified 3 years, 11 months ago by John782.

On Home version you still need ‘metered’ if you want to check what’s new and hide/install.
On Pro, setting GP : Notify… = 2 is enough.

• This reply was modified 3 years, 11 months ago by Alex5723.

1 user thanked author for this post.

John782

Reply | Quote

WUmgr does not replace WU, is uses WU to provide an alternative view with options. You still need to stop WU updating your PC.

cheers, Paul

1 user thanked author for this post.

John782

Reply | Quote

I cannot install KB5000802. I get 0x800f0831 error. Attached is my CBS.log. Any ideas how to resolve it?

 

 

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

[Alex5723]

radosuaf wrote:

I cannot install KB5000802. I get 0x800f0831 error. Attached is my CBS.log. Any ideas how to resolve it?

 

 

Try by downloading directly from Microsoft catalog and install.

• This reply was modified 3 years, 11 months ago by Alex5723.

Reply | Quote

[radosuaf]

Didn’t install. Any other ideas? 🙂

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

• This reply was modified 3 years, 11 months ago by radosuaf.

Reply | Quote

radosuaf wrote:

I cannot install KB5000802. I get 0x800f0831 error. Attached is my CBS.log. Any ideas how to resolve it?

Hi radosuaf:

What is the current version and build of your Win 10 Pro OS at Start | Settings | System | About | Windows Specifications? Did the February 2021 Patch Tuesday cumulative update KB4601319 (OS Builds 19041.804 for v2004 or 19042.804 for v20H2) install successfully? Your CBS.log excerpt includes references to build 10.0.19041.867 but it’s hard to tell which build actually installed successfully.

I’m not an expert at reading CBS.log files but I noticed that there are multiple errors in your CBS.log file related to a “CBS_E_STORE_CORRUPTION” (e.g., Store corruption, manifest missing for package: Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~amd64~~10.0.19041.546; Store corruption, manifest missing for package: Microsoft-Windows-Printing-PremiumTools-Package~31bf3856ad364e35~amd64~~10.0.19041.572). According to the MS support article Error 0x800f0831 When You Install an Update, this error occurs when you install a cumulative update “because the update that can’t be installed requires the manifest of a previous update package” and recommends that you download those failed packages from the Microsoft Update Catalog and run them manually. However, someone else following this thread might be able to suggest a better way to resolve those store corruption errors.

In the mean time, you might want to run the free Belarc Advisor (currently v9.7, available at https://www.belarc.com/products_belarc_advisor) to build a profile of your system and see what missing Windows security updates this utility finds.
————-
64-bit Win 10 Pro v2004 build 19041.804 * Windows Defender v4.18.2102.4

Reply | Quote

OS build is 19042.804.

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

I decided it was time to see if KB5000802 would cause problems here. So far, no issues to report. I’ve printed a screen capture and a 2 pages of a 7 paged .pdf, in duplex, with no problems.

I’m running Windows 10 Pro 20H2 (winver says I’m at OS Build 19042.867). I have a Brother MFC-L3770CDW multi-function printer.

Reply | Quote

I’m still seeing issues with people in businesses with businessy printers having issues.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote