Even .net thinks 21H2 should be out

Topic

New Reply

So I’m recapping the updates for the Master patch list tonight and listing the early issues I’m tracking and I realize that even the .NET blog thinks
[See the full post at: Even .net thinks 21H2 should be out]

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

CAS, GreatAndPowerfulTech

Reply | Quote

Replies

I thought 21H2 is Windows 11 and if you are on Windows 10 and want to move to Windows 11 you would allow the update. Otherwise, you would use GPedit and make sure you do not move beyond Windows 10 21H1. I’ve never felt confused before in the past about updates, but this is VERY confusing.

Reply | Quote

Windows 10 AND Windows 11 have the same version numbers (ex. 21H2).
Group Policy now has another setting = “Product Version” = Windows 10 OR Windows 11, depending which one you are on or which one you want to stay on/maintain. The new setting in Win10 is found under Windows Update\Window update for Business and in Win11 under Windows Update\Manage updates offered from Windows Update.

2 users thanked author for this post.

Cee Arr, Seattle27

Reply | Quote

I agree it is confusing but, according to MS in THIS JULY 15 BLOG POST, there is a 21H2 release for Windows 10.

Reply | Quote

I find it confusing because I was under the impression that Windows 11 would get a feature release only once a year.

Reply | Quote

It will only get one feature release a year.  Again Windows 11 21H2 is not the same as Windows 10 21H2.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

My point is that it’s confusing that they’d choose to use the same naming scheme as Windows 10 for Windows 11, when that naming scheme is based on there being two releases per year.  The name 21H2 means “second release of 2021.” But this is Windows 11’s first release, ever.

Reply | Quote

.NET updates are already a mess

i miss the good old days of a simple .NET update whenever due

1 user thanked author for this post.

WCHS

Reply | Quote

But at the same time, I don’t miss the old days when they would break everything

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

My computer already installed the latest cumulative update. When I turned on my computer again, I got a nasty surprise of unable to read drive or something to that effect. I had to rebuild windows. Don’t install.

/Breaker

Reply | Quote

I haven’t seen any other reports of severe side effects.  I’d scan your hard drive as it may be failing.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

deuxbits

Reply | Quote

Does anyone have any idea when 21H2 will be available?

Reply | Quote

Probably today or next Tuesday

Reply | Quote

‘Fun Valley’ aka Windows 10 21H2 has been publicly released by MSFT.
New MCT over on: MediaCreationTool21H2

Windows - commercial by definition and now function...

Reply | Quote

??
Still 21H1

Reply | Quote

PKCano wrote:

Windows 10 AND Windows 11 have the same version numbers (ex. 21H2).
Group Policy now has another setting = “Product Version” = Windows 10 OR Windows 11, depending which one you are on or which one you want to stay on/maintain. The new setting in Win10 is found under Windows Update\Window update for Business and in Win11 under Windows Update\Manage updates offered from Windows Update.

Thank you! I had set that some time ago and forgotten….memory as I age is just not as good as it used to be.

Now I know why, when I uncheck the setting to Disable Windows Update in WinAero Tweaker that I have used since XP days and reboot and check Windows Update, I am not offered 21H2 for Windows 10. I had set Target Feature Update Version to 21H1.

Reply | Quote

For one more version label anomaly, the Malicious Software Removal tool delivered to Win 10 21H1 in the November release is labeled as a “Windows 11” item.

Reply | Quote

Mu laptop is running Windows 10 v.21H2. It just finished installing the .NET update. I really wonder what is going on at Microsoft. Why haven’t they update more Windows 10 users to v.21H2? It appears to be flawless to me. I’ve upgraded some customer machines to v.21H2 using USB stick created with Rufus.

GreatAndPowerfulTech

Reply | Quote

@GreatAndPowerfulTech

Win10 21H2 did actually / officially come out on November 16 (3rd Tuesday of Nov. 2021). MS simply released it a little later than some people expected

Reply | Quote

GreatAndPowerfulTech wrote:

Why haven’t they update more Windows 10 users to v.21H2?

21H2 for Windows 10 isn’t public yet.

Reply | Quote

[TJ]

I’ve never understood how or when (or not) to update .NET [Framework], and probably never will.

I’m on Version 21H1 Build 19034.1288 and according to Accessibility.dll I’m currently on .NET version 4.8.4084.0 with date 12-7-2019.
My log shows that the last .NET update I installed was August cumulative update 5004331.

So now there’s a November update for Framework 3.5, 4.8 called 5006365.
Should I install it?

Thx

P.S.: I always update manually only.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

• This reply was modified 3 years, 6 months ago by TJ. Reason: Added update info

Reply | Quote

I now see that 5006365 is a Preview update, so I won’t install it.

But is my system up-to-date with that August Cum.NET update 5004331?

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Reply | Quote

no TJ your system is not up to date

KB5006365 is no longer a preview .NET update anymore

1 user thanked author for this post.

TJ

Reply | Quote

But these .net updates don’t include any new security patches, so you may not be offered them.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

TJ

Reply | Quote

Thanks for clarifying that, Susan.

LMDE is my daily driver now. Old friend Win10 keeps spinning in the background

Reply | Quote

while that .NET blog may say that KB5006365 is out for Win10 21H2, the MS Update Catalog site currently only mentions KB5006365 for Win10 v2004, 20H2 & 21H1 and not 21H2

Reply | Quote