The patch waiting game — September edition

Topic

New Reply

PATCH WATCH By Susan Bradley For those of us in the northern hemisphere, September can be a time when days seem to be noticeably shorter — the d
[See the full post at: The patch waiting game — September edition]

4 users thanked author for this post.

Myst, woody, grams, abbodi86

Reply | Quote

Replies

thanks so much for this (and the past and future) easy to understand posting about Win7 updates!

Reply | Quote

No problems with September’s Windows 7 Security Only patches the same as for the July 2019 Security Only patches. That’s because They are Not Security Only and I’ll only install the actual Security Only patches.

No worries about patches breaking things if they are never going to get installed in the first place and no waiting as well. So on to October this time just like it was on to August after the previous month’s “Security Only” patches where skipped.

Reply | Quote

Tracey Capen wrote:

PATCH WATCH By Susan Bradley

If you also receive KB 4480730, a “Reliability improvement to Windows 10 update components” patch, it’s a sign that your system hasn’t been getting updates as it should. The patch’s information page states: “This update will be downloaded and installed automatically to Windows 10 devices [that] haven’t installed the most recent cumulative update in a timely manner.”

I recommend not installing it.

Why? Reliability is a bad thing for cumulative updates?

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

Reply | Quote

Running Win10 Pro x64 ver 1803 Group A, Patched through August except for .NET 4.8

So where are we on .NET 4.8?  In August I deferred (hid) KB4486153 per Susan’s advice.

Now Susan shows there is a KB4514357 for September (which I am not receiving?) Is this a replacement/update for KB4486153?

Is advice still to defer/hide .NET 4.8 updates? Do I need both now?

Can’t find it, but seem to recall some other posters recommended installation and that it even made their system more responsive or something like that.

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

Reply | Quote

KB4486153 is the installer for .NET Framework 4.8
KB4514357 is the Cumulative Update for .NET 4.8

1 user thanked author for this post.

Tex265

Reply | Quote

PK thanks.
Is advice still to defer these (until needed by some program)?
Or is there a benefit to installation?  If so, do I need to install both?

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

Reply | Quote

Why do you ask? Keep Taking Susan’s advice.

1 user thanked author for this post.

Microfix

Reply | Quote

It’s near impossible to block .net 4.8 on an unmanaged machine.  They are now sending out security updates ergo why I’m tracking it.  The only way to block .net 4.8 is to use the registry key to block it.

Block it if you are savvy enough to do so, but if you aren’t I’ll be monitoring for side effects.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Microfix

Reply | Quote

Susan,
Running Win 10 Pro ver 1803, Group Policy WUpdate set at 2 (ask before downloading) I had no problem hiding the .NET 4.8 Install KB4486153 in August with the wushowhide utility and it is still hidden.
But because of not installing it (I think) it is now the reason that I am not receiving the September .NET update KB4514357.

That is the reason for my post, as to whether continuing to hide KB4486153 and now not receiving KB4514357 is OK for my system long term whether I need it or not?

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

Reply | Quote

Correct, you only get the Sept 4.8 offered if you installed the base 4.8.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

P.S. you are still getting security updates for .net but they are smooshed/bundled into the operating system.  In the 4.8 era the .net patches will be independent from the OS.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

OK, so again – should I allow the installation of .NET 4.8 and the September update to get my system up-to-date, or continue to block its installation forever or until a program needs it to be installed?

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

Reply | Quote

Your question was answered in #1954585.

Reply | Quote

If it ain’t broke.don’t fix it is my advice.
Do you NEED .Net framework 4.8?

Edit: my MS bad, your on W10 so you’ll be getting it like it or not in the near future 🙂

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

Reply | Quote

I’d like to know why KB 4480730 is only available via Windows Update and Microsoft Update and not via Windows Catalog or WSUS?

I have some Windows 10 machines that cannot install 1903 unless I physically get on the machine and run Windows Update manually to acquire what I believe to be this update. It installs rather quickly and then the pc is able to install 1903.

Red Ruffnsore

Reply | Quote

It’s deemed to be a “consumer”/unmanaged only.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

See MS support article 4480730:
https://support.microsoft.com/help/4480730/

Applies to: Windows 10, Windows 10 version 1511, Windows 10 version 1607, Windows 10 version 1703, Windows 10 version 1709, Windows 10 version 1803

this does not seem to apply to those using 1809 or 1903

Reply | Quote

Tracey Capen wrote:

PATCH WATCH By Susan Bradley

Instead, consider it a warning that you should probably upgrade to a newer version of Windows 10. To do so, hop over to the Microsoft Software Download page and click the Update now button. Be aware, however, that it will automatically bump you to Win10 Version 1903.

But the Master Patch List updated the previous day says;

“Version 1903: Test only at this time, do not install on production machines.”

Shouldn’t the advice be a little more consistent between the blog, newsletter and patch list?

(The same applies to whether Home users should upgrade to Pro, or not.)

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

Reply | Quote

My bad.  I’m actually running 1903 here at the office with no (noticable anyway) issues.  My point was that if that patch gets offered up to you, it’s a sign that big brother sees your system is having problems.  Rather than install the patch – IMHO – it’s wiser to use the ISO/download/upgrade now page as that will identify any issues and be the best way to solve it.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

Mr. Natural, b

Reply | Quote

It’s a lot quicker for me if I just get on a pc and run windows update vs. running an ISO upgrade. I can log in or switch user on the problem pc’s, run Windows Update, allow the patch to install in about a minute ,and then log off and allow everything to continue updating and installing without further babysitting.

If this was available via WSUS I could create a group of all the machines showing install failure, put them in that group and approve the install for only that group.

Thank you Susan!

Red Ruffnsore

Reply | Quote

[EP]

but installing a feature update thru ISO is better than downloading/installing a feature update thru WU or WSUS and the ISO method provides very high sucess rate

• This reply was modified 4 years ago by EP.

Reply | Quote

Has anyone else experienced KB4494452 and KB4512575 installing, rebooting the machine, and then they install again, over and over, always needed but since they are already installed they fail, so it retries again…

I’m using BigFix, so they may have a pony in this race.  I’ll open a ticket with them, but I just wanted to check here to see if it’s a common thing or not.

Reply | Quote

[EP]

MikeM wrote:

Has anyone else experienced KB4494452 and KB4512575 installing, rebooting the machine, and then they install again, over and over, always needed but since they are already installed they fail, so it retries again…

I’m using BigFix, so they may have a pony in this race.  I’ll open a ticket with them, but I just wanted to check here to see if it’s a common thing or not.

those two updates [KB4494452 and KB4512575] are for 1709 enterprise & education editions only, MikeM.
they fail to install on 1709 home & professional editions as those editions went EOL (aka “out of support”) on April 2019. you need to upgrade to 1803, 1809 or higher

• This reply was modified 4 years ago by EP.

Reply | Quote