On August 7, 2014, Microsoft announced that support will end for .NET Framework 4, 4.5, and 4.5.1 on January 12, 2016 (.NET Framework Lifecycle). Customers and developers need to have completed the in-place update to .NET Framework 4.5.2 by January 12, 2016 to continue receiving technical support and security updates. Support for .NET Framework 4.5.2, as well as all other .NET Framework versions such as 3.5 SP1, will continue for the duration of the operating system support lifecycle.
All machines running versions of .NET less than 4, 4.5, and 4.5.1 must be upgraded to 4.5.2 at a minimum.
There are a very small number of changes in .NET 4.5.2 that are not fully compatible with earlier .NET versions. Microsoft includes these changes in the interests of security, in order to comply with industry wide standards, and to correct previous incompatibility within .NET. Additionally, there are a small number of changes included in .NET 4.5.2 that will only be enabled if you choose to recompile an application against .NET 4.5.2.
More information about application compatibility across the various versions in the .NET 4.x family can be found here.
Support for .NET 4.5.2 follows the support lifecycle policy of the parent operating system. It is supported as a Windows component on the latest required operating system update for Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows 8.1 Update, Windows Server 2012, and Windows Server 2012 R2.
Install a Supported Framework Version
The following links can be used to download and install a supported version:
- .NET Framework 4.6.1 (Web Installer; Offline Installer)
- .NET Framework 4.6 (Web Installer; Offline Installer)
- .NET Framework 4.5.2 (Web Installer; Offline Installer)
These versions of the .NET Framework run side-by-side with the .NET Framework 3.5 SP1 and earlier versions, but perform an in-place update for the .NET Framework 4, .NET Framework 4.5 and .NET Framework 4.5.1.
In addition to downloading from Microsoft, packages are available for deployment within MECM and IEM.
Please upgrade to one of the supported version as soon as possible.
