.NET Framework patch numbering screw-up?

Topic

New Reply

Message from JO: I have two .NET Framework updates pending on my Windows 7 Service Pack 1 64-bit computer.  KB3102433 – “Microsoft .NET Framework 4.6.
[See the full post at: .NET Framework patch numbering screw-up?]

Reply | Quote

Replies

This is somewhat unrelated, but I installed the
Reliability Rollup for Microsoft .NET Framework 4.6, and 4.6.1 for Windows 8.1 (KB3186208). It seemed to take a long time to install, but it eventually did install.
When I checked my update history a few days later, I discovered that the installation had failed, but then had succeeded. I only did one install.

Reply | Quote

Woody, just saw this comment in Reddit re Windows Updates. Kinda sums it all up very succinctly, no?

Reddit Sept 24, from ‘handburger’ –
“Every time Windows updates I feel like a stranger just came into my house and smeared **** all over the walls.”

Reply | Quote

Naw. The updates, by and large, are fine – except when they get into nagware or snooping territory. Then they’re germs, and they deserve to die.

Reply | Quote

There is a KB3179930 referenced in this article:
https://support.microsoft.com/en-us/kb/3179930

and it is meant for .NET 4.5.2.

So what I see is, there are 2 separate rollups. KB3179930 is for .NET 4.5.2, and KB3179949 is for .NET 4.6.x.

By the way, personally I consider .NET 4.6.1 to be useless as the softwares I have that require .NET all work under 4.5.2. So I won’t install it and have already hidden it.

Hope for the best. Prepare for the worst.

Reply | Quote

The numbering of the patch and the associated KBs are messed up. The update for all versions is Optional, has been revised once and may get another revision, at least when it will likely be moved to Recommended. It works, only that there are the cosmetic aspects noticed by the original poster which are not consistent. It is another one of the betas rushed as Optional and fixed in later revisions.
We have Relaibility Rollup for Microsoft .NET Framework 4.5.2, 4.6 and 4.6.1 on Windows 7 and Server 2008 R2 for x64 (KB3179930) which is documented in https://support.microsoft.com/en-au/kb/3179949 according to the information associated with the update. This article documents only 4.6 and 4.6.1. In fact there is a second KB at https://support.microsoft.com/en-au/kb/3179930 which documents the update for 4.5.2. This is the number consistent with the patch.
The update itself is a bundle for both versions. Only the installed one gets updated.

As recommendations, 4.5.2 is certainly a good version, although it had a recent messed up patch, fully functional, but the versioning messed up – there were 2 versions around, now it is fixed.
4.6 is obsolete and should no longer be installed anywhere, being replaced with 4.6.1 on Windows Update and 4.6.2 released recently.
At the same time 4.6 any version is supposed to completely update and replace 4.5.2, but this is not always the case.

Hope I didn’t confuse the subject more than Microsoft themselves has already done.

For anything .NET Framework check this site.
https://blogs.msdn.microsoft.com/astebner/
It is the best source of information and tools available anywhere on the Internet.

Reply | Quote

No they deserve to die when they are forced on users part. When they are of poor quality and do damage.

Reply | Quote

Had same 5.6.1 come up on my updates on my Win 7 SP 1 x64 and I installed it – restarted and it was gone. MS decided that my Win 7 variety was not suitable for this update. I do have the 5.5.1. Net. Dist. are not lined up yet..

Reply | Quote

Woody, About 4 weeks ago I got the net. dist 4.6.1 on my Win 7 SP 1 x64 and I installed it just for fun. It finished installing and I restarted and it was gone. I have had this happen before and MS, evidently sends out and has no address in mind. I do have the 4.5.1 already installed as it came in sometime this summer for some reason. I it does’t belong in your particular OS, your OS will regurgitate it. Had no problems out of this episode.

Reply | Quote

KB3179949 is the Reliability Rollup for .NET Framework v4.6 and v4.6.1
KB3179930 is the Reliability Rollup for .NET Framework v4.5.2

The “More Info” link for KB3179930 points to the wrong KB article
– however if you edit KB number (in the browser address bar) you get the correct documentation.

Reply | Quote

It is probably the safest bet to stay with 4.5.2. The server equivalent Windows 2008 R2 does not get 4.6.1 on Windows Update, although newer servers do.
It is very likely that users on 4.6.1 will never have a problem, but I think they will eventually get 4.6.2 in few months and can forget about 4.6.1 by then.
https://blogs.msdn.microsoft.com/dotnet/2016/08/02/announcing-net-framework-4-6-2/

Reply | Quote

Has anyone got a link to the documentation for this update? Does anyone know of anything to consider before installing it?

Thanks

Reply | Quote

+1

Reply | Quote

ch100: You said, “The update itself is a bundle for both versions. Only the installed one gets updated.” So, are you saying that even though the pending update on my computer (KB3179930 – Reliability Rollup for Microsoft .NET Framework 4.5.2, 4.6, and 4.6.1 on Windows 7 and Server 2008 R2 for x64) references three versions of .NET and the “More information” link references the wrong KB, installing this update should work and will simply update the .NET version currently on my computer, i. e. .NET 4.5.2? Thanks. And thanks to everyone for their replies.

Reply | Quote

I still wonder why Windows 7 get it, but not Windows 8.1
where else Server 2012 R2 get it, but not Server 2008 R2

Reply | Quote

Now I’m confused. I have .NET Framework v4.6.1 installed, but KB3179930 is showing up in the update list… What should I do?

Reply | Quote

That’s expected, both rollups are bundled under one entry in WU, KB3179930
if you choose to apply it, it will only download and install KB3179949

Reply | Quote

As DoubleO-7 pointed it out :

“Reliability Rollup 3179930 for the .NET Framework 4.5.2 on Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, and Windows Server 2008 R2 SP1”

4.5.2 only …

Reply | Quote

Nothing, you are OK. It is only the documentation which comes under different numbers. The patch for all 3 versions covered is still KB3179930.
If you did not install the patch, you should wait a little longer as the patch is only Optional at this stage.

Reply | Quote

It is really weird. I could find a reason for servers not getting it and this applies to Windows 2008 R2 and 2012 R1. This is because Exchange 2013 had until recently problems with 4.6.1, fixed only recently by one of the CUs. As I understand it, those with Exchange 2013 are still better off with 4.5.2. The original Exchange 2013 unpatched was not working on 2012 R2, so this was not an issue, although all new installations with SP1 are normally done on 2012 R2. It is all messy, however there should be no problem on the client side. So I cannot explain at all why 8.1 does not receive it in WU.
I have 4.6.2 installed without noticing any problem, but for non-experimental configurations, I would still recommend 4.5.2.
While 4.5.2 seems the standard still, it had a recent patch which was not behaving normally. I think it was related to LDR vs GDR versions which were not detected correctly. It was resolved since by expiring the LDR version.
https://support.microsoft.com/en-us/kb/3135996

Reply | Quote

This is what I say and this applies mostly to the users who have already installed it.

However, for the users who have not installed this update which is Optional at the moment, I would suggest putting it on hold at least for a while, either until Woody clears it which is unlikely to happen while it stays Optional, or if it becomes at least Recommended or otherwise wait at least 3 months from now if it will still be Optional by that time. In 3 months it will be clear if there will still be any unresolved issues. I am aware of good Optional updates (for Windows 8.1 and 2012 R2) which are in Optional only because of obscure problems in very specific situations affecting only few users and Microsoft just wants to avoid the backlash associated with this sort of releases if they are anything other than Optional.
This patch is one of those roll-ups (cumulative updates) promised for October 2016 and this one is specific to the .NET Framework versions. We may see it upgraded to Recommended or Important at the next main Patch Tuesday for October or November.

Reply | Quote

I’m getting messed up myself :

Here on Windows 7 the Control Panel / Installed Programs states :
Microsoft .Net Framework 4.6.2
Installed 12/10/2015
Version 4.6.01590

Corroborated by the application ASoft .Net Version Detector v.16R2 which displays : 4.6.2

And you write that “[…]users on 4.6.1 will never have a problem, but I think they will eventually get 4.6.2[…]”

I’m doing my best but I admit being intrigued once in a while …

Reply | Quote

Microsoft is promoting .Net 4.6.2 with this statement:
“The Microsoft .NET Framework 4.6.2 is a highly compatible, in-place update to the Microsoft .NET Framework 4/4.5/4.5.1/4.5.2/4.6/4.6.1.”

.Net 4.6.2 can be installed using either the web installer here:

https://www.microsoft.com/en-us/download/details.aspx?id=53345

or with the offline installer package here:

https://www.microsoft.com/en-us/download/details.aspx?id=53344

I installed it on my Win 7 machine, and it appears to be working fine. It apparently already includes all of the KB upgrades, as I have not seen any of those in Windows Update.

Reply | Quote

It is interesting how you claim “that’s expected”, when everyone else is confused

Reply | Quote

abbodi86 and ch100, thank you for your reply!
Good to know I didn’t receive the wrong patch. And I will wait until it’s a recommended update.

Reply | Quote

I don’t know how you got 4.6.2 in 2015. I thought it was released more recently, but everything is possible. You may have installed an early beta/preview?

Reply | Quote

ch100, Simpson, abbodi86: O. K. I understand now. Also, as you suggested and is my usual procedure, I will wait to install this update until the dust settles. Thanks to you and all who replied.

Reply | Quote

Because i saw the update in MU catalog which reflects WU state
http://go.microsoft.com/fwlink/?LinkID=116494&updateid=23a8b5b2-7c45-47b1-a99d-a7149de3410a

it’s labeled KB3179930
More information url points to KB3179949
hitting download gives you both

Reply | Quote

@SamH: the .NET Framework 4.6.2 downloads are currently only available from Microsoft Download Center and won’t be posted on Windows Update until later on (maybe either next month or near the end of 2016).

Smart of you to install .NET 4.6.2 than to just rely on patching .NET from WU, like what I did on all my Win7 computers.

Reply | Quote

I may very well have installed it myself, independently of Windows Update, I’m not sure because I’ve just noticed that I have among by backups two .Net Frameworks installers,

1- Microsoft .Net Framework 4.6.1 with :
NDP461-KB3102436-x86-x64-AllOS-ENU.exe dated 12/10/2015

2- Microsoft .Net Framework 4.6.2 with :
NDP462-KB3151800-x86-x64-AllOS-ENU.exe dated 08/03/2016

Not sure because concerning .Net Framework I also keep a backup of the installers whether I’ve installed them myself or downloaded them after a Windows Update…

Anyway the article you mention above, https://blogs.msdn.microsoft.com/dotnet/2016/08/02/announcing-net-framework-4-6-2/ is dated August 2, 2016, no?

I don’t understand either how Windows my Control Panel / Installed Programs states :
Microsoft .Net Framework 4.6.2 as Installed on 12/10/2015 … ckecked again, 12/10/2015 confirmed.

Reply | Quote