Hotfix rollup 3031988 for the .NET Framework 3.5 on Windows 8 and Windows Server 2012

Applies to: .NET Framework 3.5 Service Pack 1Windows 8Windows 8 Enterprise

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


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


To apply this hotfix, you must have the .NET Framework 3.5 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

Issue 1

Assume that your locale is not set to a Lithuanian locale. When you run a .NET Framework 2.0 SP2, 3.5 SP1, 4.0 or 4.5-based application to obtain the New Lithuanian Euro symbol, the symbol does not display.

Issue 2

Assume that you have applied Update 2998527  on your computer. When you run an application that uses the .NET Framework to calculate time by using the TimeZoneInfo class, you may receive incorrect code lookups on past dates.

For more information about this issue, see KB 3012229: Update 2998527 causes incorrect code lookups on past dates by using TimeZoneInfo in the .NET Framework.