Hotfix rollup 3057756 for the .NET Framework 4.0 on Windows 7 SP1, Windows Server 2003 SP2, Windows Server 2008 R2 SP1, Windows Server 2008 SP2, and Windows Vista SP2

Applies to: Windows 7 Service Pack 1Microsoft Windows Server 2003 Service Pack 2Windows Server 2008 Service Pack 2 More

This article describes the hotfix rollup 3057756 that is available for the Microsoft .NET Framework 4.0. For more information about the issues that the hotfix rollup resolves, see the "Issues that this hotfix rollup resolves" section.

Resolution


A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

More Information


Prerequisites

To apply this hotfix, you must have the .NET Framework 4.0 installed.

Restart requirement

You have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.

Hotfix replacement information

This hotfix package does not replace a previously released hotfix package.


Issues that this hotfix rollup resolves

After October 26, 2014, when you use applications on systems that have the September 2014 Russian time zone update KB2998527  installed and use the Microsoft .NET Framework, the applications that use the TimeZoneInfo class may make time calculations incorrectly. For more information, see Update 2998527 causes incorrect code lookups on past dates by using TimeZoneInfo in the .NET Framework .