Introduction
This article describes hotfix rollup 2829536 that is available for the Microsoft .NET Framework 3.5 Service Pack 1 (SP1). For more information about the issue that the hotfix resolves, see the "More information" section.This hotfix rollup is available for the following operating systems:
-
Windows 7
-
Windows Server 2008 R2
More Information
Hotfix Information
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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
Prerequisites
To apply this hotfix, you must have the .NET Framework 3.5 SP1 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.
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x86-based versions of Windows Server 2008 R2 and Windows 7
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:40 |
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:40 |
For all supported x64-based versions of Windows Server 2008 R2 and Windows 7
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:40 |
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:40 |
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:40 |
For all supported IA64-based versions of Windows Server 2008 R2 and Windows 7
|
File name |
File version |
File size |
Date |
Time |
|---|---|---|---|---|
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:39 |
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:40 |
|
system.core.dll |
3.5.30729.7030 |
667,648 |
21-Mar-2013 |
07:40 |
Issues that this hotfix rollup resolvesWhen you call some methods of the System.Diagnostics.Eventing.Reader.EventRecord class, such as FormatDescription method, in an application, the methods may return a NULL value. Note This issue may occur only when an exact locale or region is not installed on your computer.
