Microsoft releases some “optional, non-security C/D Week” patches. Avoid them.

Topic

New Reply

The folks at MS have decided that we’re no longer in a “public health situation” that’s worthy of a moratorium on useless, error-prone patches. Late y
[See the full post at: Microsoft releases some “optional, non-security C/D Week” patches. Avoid them.]

2 users thanked author for this post.

abbodi86, Elly

Reply | Quote

Replies

Woody … just some additional telemetry and a question regarding the optional updates:

https://www.askwoody.com/forums/topic/1909-2004-feature-update-notification-blocking-optional-updates-2/

Thoughts?

1 user thanked author for this post.

woody

Reply | Quote

See #2282438 under your recent Topic.

Reply | Quote

I don’t know if MS is doing some sort of weird A/B testing – holding off on optional updates for those of us in Tennessee because, I dunno, the folks in Seattle are envious of sunny skies?

Seriously, the lag in updates being offered is probably tied to some sort of server lag.

Reply | Quote

I’m in upstate New York ;-).

At any rate … I’m on Pro, and WU settings are the default (never changed them or setup deferrals, etc. I know, I know …)

🙂

1 user thanked author for this post.

woody

Reply | Quote

I’m down in southern California, howardagoldberg
hope things are better there instead of where I reside

I haven’t been offered the optional C/D patches like KB4559003 & KB4559004 when checking for updates on my 1909 & 1809 PCs – only the .NET preview ones like KB4562900 & KB4562901 somehow got through

Reply | Quote

I’m going to make a conjecture that has absolutely no basis in fact.

I’m going to bet that a VERY large percentage of the folks who willingly and knowingly install Previews are enrolled in the Windows Insider program.

Why doesn’t MS make the Previews an Insider ring????

1 user thanked author for this post.

Elly

Reply | Quote

Probably b/c some businesses want to test the upcoming changes on a test production machine that is not an Insider. If the Preview causes problems in a real-time environment, then they know to watch the Patch Tues update closely to verify if the problem has been fixed.

1 user thanked author for this post.

woody

Reply | Quote

[Susan Bradley]

I’m not on insider.  These are not the same as the insider ring stuff.

Susan Bradley Patch Lady

• This reply was modified 2 years, 10 months ago by Susan Bradley.

1 user thanked author for this post.

woody

Reply | Quote

Susan Bradley wrote:

These are not the same as the insider ring stuff.

How so? They’re beta (or gamma?) test versions….

The Release Preview Ring, as originally envisioned years ago, matched up with these Previews precisely. The Release Preview Ring has gone through some major changes (and lots of neglect), but it seems to me to be exactly what these optional, non-security updates should be going through.

Reply | Quote

The Release Preview Ring has gone through some major changes (and lots of neglect), but it seems to me to be exactly what these optional, non-security updates should be going through.

They are. The previous week:

Finally, for those in the Windows Insider Program or Windows Insider Program for Business, in-development versions of these non-security updates will be released to the Release Preview Channel in the “B” week.
Resuming optional Windows 10 and Windows Server non-security monthly updates

Reply | Quote

[woody]

Right… but I didn’t see them last week in the Release Preview Ring. And why are they being pushed out Windows Update?

… hang on… I think I understand now. The promised B week Release Preview versions only apply to Win10 version 2004 Preview Cumulative Updates. But there aren’t any version 2004 Preview Cumulative Updates. So we didn’t get them last week.

At least, I think that’s how it works.

Circles within obfuscatory circles.

• This reply was modified 2 years, 10 months ago by woody.

Reply | Quote

I am (of course) NOT an insider and not on 2004 but 1903, still got this weird one pushed. Even with all possible deferrals on, there was no way to escape it. Strange.

Reply | Quote

Got a mysterious KB 456290p pushed, just before shutting down systems here (https://www.tenforums.com/windows-10-news/161089-kb4562900-cumulative-update-net-framework-3-5-4-8-windows-10-july-21-a.html). So we’re now all officially used as Guinee pigs, even while running pro and update deferral active. So tired of Windows, happy to have only a back-up laptop left over to maintain. The rest is replaced by Mac and Linux. Why? Precisely because of this blubber that Microsoft keeps delivering.

1 user thanked author for this post.

ymo1965

Reply | Quote

I almost never check for these C/D updates when they come in.  Just for giggles, took a look.  Nowhere is the word “preview” used.  Maybe they just haven’t arrived yet in the action center/WU.  No worries, I won’t install the rollup (now hidden) & am waiting on DC3+ for .NET approval.

2020-07 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4565541)

Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1, RT 8.1, and Windows Server 2012 R2 (KB4566519)

Win 8.1 (home & pro) Group B, Linux Dabbler

Reply | Quote

Those updates in that screen are not preview releases.  That’s the main security updates for July. https://devblogs.microsoft.com/dotnet/net-framework-july-2020-cumulative-update-preview/  They didn’t release previews for Win7 .net versions.

Susan Bradley Patch Lady

2 users thanked author for this post.

Purg2, Elly

Reply | Quote

[geekdom]

Woody’s article:

In my tests, though, clicking to Resume Updates on a Win10 1909 system installed the .NET patch. I did not click Download and install. The Preview just installed itself.

How do you find out what’s out there? You can’t click. You can’t see. The update just moves in. NEVER CLICK Check for updates.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox114.0b8 MicrosoftDefender

• This reply was modified 2 years, 10 months ago by geekdom.
• This reply was modified 2 years, 10 months ago by geekdom.

Reply | Quote

PowerShell is the only way that you can “check” without installing…. especially now that they’ve turned optional updates back on again.

Susan Bradley Patch Lady

Reply | Quote

From what I understand now is, that the pushed preview repairs a ‘serious’ bug regarding LTE. Fine with me, but I don’t have a laptop with built in modem. So why didn’t the ingenuous artificial ‘intelligence’ of the Windows update mechanism didn’t detect that and thus not bother me with a probably shabby preview? And even more worrying: why is .net vital for the functioning of LTE?

Reply | Quote

LTE is not mentioned within the 21 issues addressed by KB4562900

Reply | Quote

@geekdom  How do you find out what’s out there?

If you have Windows 10 Pro and wuShowHide app, use Group Policy to set Windows Update to option 2 which will notify you of updates but not automatically download and install them.  You can check wuShowHide periodically to see what is out there or use it once they appear in the Windows Updater. Use wuShowHide to hide them and they will no longer show as installable (once Windows Updater runs again) until you unhide them.

I received this new Preview KB4562900 this morning and hid it per above.

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

1 user thanked author for this post.

Coldheart9020

Reply | Quote

https://www.deskmodder.de/blog/2020/07/22/kb4559004-windows-10-1903-1909-manueller-download-als-optionales-preview-update/

Reply | Quote

KB4559004 is not KB4562900 (.Net).

The only mention of latter on that page is, “In addition, the KB4562900 was also used as the .NET Framework Update.”

1 user thanked author for this post.

R

Reply | Quote

Why we shouldn’t install KB4559004 if it fix some bugs. It is usefull.

Reply | Quote

Yeah, I also do not completely understand it. Some sites mention this update together with the unwanted but forced preview. Guess we will never really know what this all was about. For now, I think that a majority of Windows users are running some kind of shabby and probably insecure preview/beta of .NET. Wish this whole Java-surrogate didn’t exist at all anymore for several reasons. Oh well, in the end this whole miserable Windows 10 is a continuous preview so I care less and less. Don’t do vital work on Windows systems anymore, gave it up years ago.

Reply | Quote

most 1903/1909 users don’t really need KB4559004 if it doesn’t fix their specific problem(s)

plus Win10 v1903/v1909 users have to manually download & install it

Reply | Quote

Nope. It was an auto download  and install here. Which is even more strange because that’s not how those pesky .net-patches usually work. It’s an absolute total mess.

Reply | Quote

Today, KB4562900 downloaded & installed itself and I have not seen “Woody’s Approval” for this update.

I’m running Win10 Pro 64 and have followed @PKCano’s AKB2000016 setup, paying particular attention to Steps 3 & 4.  I ran wushowhide, selected to hide this update, and it downloaded and installed anyways.  (My other  PC with same setup did hide this update.)

My question is:

• Should I uninstall this update, or let it go and keep it?

Thanks everyone.

ASUS TUF SABERTOOTH Z170s Motherboard, Intel i7-6700k CPU, Corsair 32GB DDR4-3200 RAM, ASUS ROG STRIX GeForce GTX-1070 Video Card, 1x BPX M.2 240GB NVMe SSD, 1x Samsung 850 EVO 1TB SSD, 2x WD Black 6TB HDD, Windows 10 Pro 64bit v1909

Reply | Quote

On the PC it did install, after you hid it with wushowhide, did you clear the Windows Update queue. If you do not clear the queue, and the .NET update was still visible there, it will download and install. Go back to the Guide and read about that and check the link to AKB2000013.

What you see in the queue is what you get, even when you think you have hidden it. 🙂

Reply | Quote

Thanks for the quick reply. I know this subject has been beaten to death (after reviewing multiple threads) but I surprisingly need further clarification please.

KB4562900 was the first update I received since setting up my PC’s using the KB articles and I am one to wait until we get the “approved by Woody” to install any approved monthly updates.  I’m still trying to “put this all together.”

No, I did not clear the queue and I now understand why the update installed.

I reviewed AKB2000013 which states:

• Be sure your Network connections are set to metered connections each time before shutting down the computer. That way, you are on Metered connections when you boot up.

However, AKB2000016 states:

• **NOTE: If you use the above “2” setting, and then set Metered connections ON too, there may be a caveat. After using this, when I later went back an turned Metered connections to OFF, without FIRST running wushowhide and hiding anything, the pending updates downloaded/installed without respecting the “2” (notify download/install) setting. I do not recommend using Metered connections if you are using deferrals and GP “2.”

I’m confused.  I’m not following or I’m failing to understand the process steps to prevent unwanted updates from installing since these appear to contradict each other.

• AKB2000013 says metered connections on at every shutdown, whereas
• AKB2000016 says metered connections off, otherwise updates will not respect the GP2 setting and download/install anyways.

Could you further elaborate on this please?

My problem with understanding these steps may be that I’m trying to “dissect” everything or integrate both KB articles together.

In the future, are these the steps I should follow?

• Boot PC (metered connections off), open WU, see if updates appear without clicking on Check for Updates.
• If updates appear as Download Pending, this means GP 2 setting worked.
• Run wushowhide, selecting any updates to hide. Go back into wushowhide to verify updates are hidden.
• If updates still appear or begin downloading on its own, immediately enable metered connection to stop the download and complete the remaining steps in AKB2000013.

Questions:

1. I opened up Windows Update Service to peek around and become familiar with it.  I did not see Disable or Apply, however I did see Stop.  I have to imagine your instructions were to select whichever option is available to he user.  Yes/No?
2. While I was in there, I saw Manual appearing in the Startup Type, however under Action only saw Stop, Start, Pause, Resume, and Restart.  How does a user select Manual?

• After following AKB2000013 and clearing the WU queue, either wait for WU to run/update (approximately 36 hours) or select Check for Updates to ensure updates no longer appear?

Lastly, I am not setup on MS Insider Program so I really should not have received KB4562900 (Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903…).

Since KB4562900 is a preview only, I could uninstall the update and use this as a “practice” scenario using wushowhide and Windows Update Service.  Do you see any risk or potential problems if I did this…or should I just let it go, and try again next time?

Thanks again…Speed

Reply | Quote

Ok, I see your confusion about the metered connections. Skip setting the metered connections in clearing the queue in if you have Pro and the “2” set. I need to revisit those instructions which were aimed at Home users when the AKB was written.

When you open Services, you have to double click on the Windows Update Service to open the popup settings box.

3 users thanked author for this post.

Perq, Coldheart9020, Elly

Reply | Quote

More on this.
I have always been able to clear the WU queue using the procedure in AKB200013. Sometimes, it has taken several reboots after I hid the patch, but it has always worked.
Microsoft may have changed something with the .NET patches.
I am currently working with my Insider Preview. After having problems with installing a new Build, I tried to hide the pending .NET CU (not Preview) update so the Build would be the only thing installed.

I could not clear the queue after I hid the .NET CU, even I went through the procedure several times.

It remains to be seen if this behavior becomes the default for .NET and also if it applies to other types of updates. Unfortunately, that is going to take at least another update cycle.

3 users thanked author for this post.

Perq, Coldheart9020, Elly

Reply | Quote

I have group policy set per Section 4 of KB2000016.  I checked Settings to see if anything showed up and KB4562900 is pending download.  Since it is a preview, should I hide it?

Reply | Quote

Yes, hide it. Whatever patches it contains will be in the Aug Rollup for .NET.
Be sure it’s gone from the WU queue before you download. If you can still see it after hiding, it will download.

2 users thanked author for this post.

Coldheart9020, redknight

Reply | Quote

I hid it via wushowhide.  So the next time Windows Update runs, it will not show up?

Reply | Quote

That should be correct. If you see it in the queue, it will download (even you think it is hidden). That cache doesn’t clear till WU checks for updates (or you use AKB2000013).

Reply | Quote

So I should let Windows Update run on it’s own schedule to check for updates to clear the queue (assuming nothing else shows up then) or is it safe to run check for updates myself now to clear the queue.  The only other update in wushowhide is a Silverlight update KB4481252 but it does not show up in Windows Update, only KB4562900 does.  Should I hide KB4481252 also?

Reply | Quote

Never click “Check for updates.”

It is not a “check.”
It is a “download and install NOW”

Reply | Quote

[Coldheart9020]

redknight, I would recommend following the steps in AKB2000013 in order to clear the Windows Update queue. Follow every step and it will definitely remove it.

I installed KB4565483 and KB4565633 successfully yesterday, but hid KB4562900 which I saw was queued up in wushowhide, and would otherwise have eventually made its way to the Windows Update main screen ready to be downloaded.

• This reply was modified 2 years, 10 months ago by Coldheart9020.

Reply | Quote

Question. I hid KB4562900.  This .NET preview will be replaced with the actual .NET rollup in August which I assume will be ok to install then.  Both won’t be available for install will they, just the actual Aug .NET?  Should I just let it ride and wait for when the ok is given to install the Aug patches when that day comes.

 

I am on Pro. Reading KB2000013.  Windows Update service (wuauserv) is Manual (Trigger Start).  Windows Update Properties says Startup type: Manual, Service status: Stopped

 

A bit confused.  Reading KB2000013.  wuauserv says the service is already Manual and Stopped.  wushowhide says KB4562900 is hidden.

Reply | Quote

[Coldheart9020]

redknight wrote:

Question. I hid KB4562900. This .NET preview will be replaced with the actual .NET rollup in August which I assume will be ok to install then. Both won’t be available for install will they, just the actual Aug .NET? Should I just let it ride and wait for when the ok is given to install the Aug patches when that day comes.

That is correct. Assuming there will be another .NET security CU this month, and MS-DEFCON gives it the go-ahead, that will make the July Preview (KB4562900) redundant and so that will almost certainly disappear from hidden updates in wushohide, since Microsoft will by then have pulled it.

Since you are on Pro, I’d also recommend PKCano’s other very helpful AKB2000016 – Sections 3 and 4 in particular – if you have not done so already. Once you have the Group Policy (‘2’ in particular) and other settings adjusted, re-read AKB2000013 again, but you can ignore the part about setting your internet connection to metered – provided the settings are correct.

I had a very similar issue to you in hiding the v2004 update, but those two articles together allowed me to hide it and then the July Preview .NET update which I did just last night.

• This reply was modified 2 years, 10 months ago by Coldheart9020.
• This reply was modified 2 years, 10 months ago by Coldheart9020.

Reply | Quote

I checked Settings and Windows Update ran on its own about 45 minutes ago and since I hid KB4562900, it does not show up and there are no updates to download.  I am up to date according to Windows Update.  Build info is 1909 18363.959

1 user thanked author for this post.

Coldheart9020

Reply | Quote

redknight wrote:

Build info is 1909 18363.959

Yeah, you’re all up to date with the required updates. 🙂

1 user thanked author for this post.

redknight

Reply | Quote