Version history of the CLR 2.0
[update 13/3/12 – added 5719]
[update Oct & Nov 2011 – various additions as I find them]
[update 23/9/11 added MS11-044 and MS11-028]
[update 31/5/11 added .5669]
[update 7/4/11 added a load of fixes that I didn’t have listed]
[update 29/12/9 added lots of post SP2 hotfixes, MS09-061 versions and added the note on dual-branch servicing]
[update 8/10/9 added Windows 7 versions and the post-3.5 SP1 app compat update]
[update 5/11/8 added .NET 3.5 SP1, various hotfixes and additional note about "what is the CLR"]
[update 20/11/7 added .NET 2.0 SP1]
[update 15/11/7 added 4 new recent fixes]
Following on from my post about ASP.NET 2.0 fixes, summarised below are the Common Language Runtime (CLR) 2.0 major releases and hotfixes, in version number order. Additional note (5/11/8): the CLR is not synonymous with the .NET Framework as a whole. The CLR is the core runtime engine, including the JIT compiler, metadata management, threadpool, garbage collector etc. The .NET Framework includes the CLR, the base class libraries (BCL), ASP.NET, WCF, WPF and lots more. The below list only relates to CLR fixes.
ASP.NET is a hungry consumer of the CLR services such as threadpool, garbage collection etc. Therefore many of the problems we see customers experience in production ASP.NET applications are the result of issues in the CLR - many of which we have already fixed. So it is always worth considering what patches you currently have installed when something weird happens.
Please read the caveats at the start of the ASP.NET 2.0 fixes post before proceeding.
Following .NET Framework 2.0 SP2, the capability for .NET Framework 2.0 fix packages to carry two different types of fix was introduced. This is referred to as dual branch servicing and is described in this article:
The first occasion I am aware of this capability actually being used is in the MS09-061 release. Therefore it is no longer the case that if the version of mscorwks.dll that you have on your system is higher than the one mentioned in a particular hotfix article that you automatically have the fix described in that article. It depends on what you had on your system prior to installing the dual-branch hotfix package. If you already had a hotfix version of those files installed you would get the LDR version. If you didn’t then you would get the GDR version.
Comments
Anonymous
September 06, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/09/06/version-history-of-the-clr-20/Anonymous
September 06, 2007
Thanks Aaron (of 'This Old Code'), you're welcome! As an escalation engineer in Microsoft's support organisation it's part of my role to provide technical detail to go into the hotfix articles. There are others involved in the publication process so I do not always have complete control over the final wording that appears but I certainly appreciate the need to make articles as useful as possible. Thanks for the feedback! DougAnonymous
September 06, 2007
Know your CLR 2.0 versionsAnonymous
September 16, 2007
Ca, ça peut être très pratique : Notes from a dark corner : Version history of the CLR 2.0 Une historiqueAnonymous
November 21, 2007
This is a number that is going to become very familiar to me over the coming months and probably years.Anonymous
November 21, 2007
This is a number that is going to become very familiar to me over the coming months and probably yearsAnonymous
December 14, 2007
Hi Doug We have received a report where our product was running in .Net 3.0 mode, but where .Net 3.5 had been installed. I can see that this changes the version of aspnet_wp.exe to .1433. The worker process died and left this clue in the event log. It is reproducible. How do we best address this quite fatal error? Best regards Jesper Jørgensen, Sitecore Faulting application aspnet_wp.exe, version 2.0.50727.1433, stamp 471ebf4c, faulting module kernel32.dll, version 5.1.2600.3119, stamp 46239c31, debug? 0, fault address 0x00012a5b. aspnet_wp.exe (PID: 1620) stoppede uventet.Yderligere oplysninger finder du under Hjælp og support påAnonymous
December 14, 2007
Hi Jesper One option is to raise an assisted support case with Microsoft support. We have a bunch of talented support engineers ready to assist troubleshoot such issues with you. If it turns out to be due to a Microsoft bug there is no charge. And maybe you already have a support contract with us or support incidents available through an MSDN subscription or through having Partner status? The other option is to DIY debug it. Grab a memory dump at process shutdown and then use the debugging tools to figure out what happened. My colleague Tess has a very details blog showing how to do this kind of debugging. See the first link under "Blog I recommend" above left. Regards DougAnonymous
June 29, 2008
Very useful list, thank you!. Just found one extra version that's not covered, see: http://support.microsoft.com/kb/923028Anonymous
June 10, 2009
Any plans to update this invaluable list? I'm trying to hunt down version 4903 at the moment. I've found 3521 in Win 7 Beta and 4918 in Win 7 RC 1.Anonymous
June 12, 2009
The comment has been removedAnonymous
October 05, 2009
An update would be most appreciated. I have Win7 RC1 with 4918, but am looking for 4927.Anonymous
October 07, 2009
4927 is the Windows 7 and Windows Server 2008 R2 version. I've just made a minor update. A major update is long overdue and I am working on it. Thanks DougAnonymous
December 28, 2009
Finally, managed a major update. Sorry for the long delay. Doug.Anonymous
March 16, 2010
The comment has been removedAnonymous
April 15, 2010
The comment has been removedAnonymous
April 15, 2010
The comment has been removedAnonymous
August 11, 2010
Version 2.0.50727.3615 = Security update KB983582Anonymous
August 15, 2010
Thanks Thomas. I've now added all the versions relating to MS10-060 (hopefully!)..DougAnonymous
May 27, 2011
The comment has been removedAnonymous
May 30, 2011
Thanks Andre - I've now added 5669Anonymous
September 21, 2011
The comment has been removedAnonymous
September 22, 2011
The comment has been removedAnonymous
September 27, 2011
The comment has been removedAnonymous
September 27, 2011
Thank you Andre, I've added that one.Anonymous
March 13, 2012
New hotfix: 2.0.50727.5719 = KB2669522 - FIX: Access violation when you use the ICryptoTransform.TransformFinalBlock API to perform a cryptographic operation in a .NET Framework 3.5-based applicationAnonymous
March 13, 2012
Thanks again Andre, 5719 addedAnonymous
April 05, 2012
great job and useful idea. pls 2.0.50727.5448 is missing?Anonymous
April 10, 2012
New updates: 2.0.50727.5723 = KB2688730 Hotfix Rollup 2688730 is available for the .NET Framework 2.0 SP2 on Windows 7 SP1 or on Windows Server 2008 R2 SP1 and KB2688027 Hotfix Rollup 2688027 is available for the .NET Framework 2.0 SP2 on Windows Vista SP2 or Windows Server 2008 SP2 and KB2688737 Hotfix Rollup 2688737 is available for the .NET Framework 2.0 SP2 on Windows XP SP3 or on Windows Server 2003 SP2Anonymous
June 18, 2012
Thanks Andre and alonesword. Will get these added. Currently trying to redesign the format similar to what I did for the CLR 4.0 fix list. Will try to publish soonAnonymous
August 14, 2012
New updates which update CLR to 2.0.50727.5733 (same update but 3 KBs for each platform) Hotfix Rollup 2733946 is available for the .NET Framework 2.0 SP2 on Windows Vista SP2 and on Windows Server 2008 SP2 support.microsoft.com/.../en-us Hotfix Rollup 2733947 is available for the .NET Framework 2.0 SP2 on Windows 7 SP1 and on Windows Server 2008 R2 SP1 support.microsoft.com/.../en-us Hotfix Rollup 2733948 is available for the .NET Framework 2.0 SP2 on Windows XP SP3 and on Windows Server 2003 SP2 support.microsoft.com/.../en-usAnonymous
February 17, 2013
New updates which update the CLr 2.0 to Version 2.0.50727.7017 Hotfix rollup 2803752 is available for the .NET Framework 2.0 SP2 in Windows 7 SP1 support.microsoft.com/.../en-us Hotfix rollup 2803751 is available for the .NET Framework 2.0 SP2 in Windows Server 2003 SP2 and Windows XP SP3 support.microsoft.com/.../en-us Hotfix rollup 2803756 is available for the .NET Framework 2.0 SP2 in Windows 8 and Windows Server 2012 support.microsoft.com/.../en-usAnonymous
February 17, 2013
New updates which update the CLr 2.0 to Version 2.0.50727.7017 Hotfix rollup 2803752 is available for the .NET Framework 2.0 SP2 in Windows 7 SP1 support.microsoft.com/.../en-us Hotfix rollup 2803751 is available for the .NET Framework 2.0 SP2 in Windows Server 2003 SP2 and Windows XP SP3 support.microsoft.com/.../en-us Hotfix rollup 2803756 is available for the .NET Framework 2.0 SP2 in Windows 8 and Windows Server 2012 support.microsoft.com/.../en-usAnonymous
February 17, 2013
Here is the missing Vista update of CLR 2.0 7017: Hotfix rollup 2803753 is available for the .NET Framework 2.0 SP2 in Windows Server 2008 SP2 and Windows Vista SP2 support.microsoft.com/.../en-usAnonymous
October 13, 2015
Thank you for compiling this list. I have bookmarked it and reference it occasionally when diagnosing customer issues. I noticed the hotfix in the KB article below is not included. I believe this version would be 2.0.50727.4253: support.microsoft.com/.../2497453Anonymous
October 28, 2015
The comment has been removed