Hotfix rollup 2783767 is available for the .NET Framework 4


This article describes hotfix rollup 2783767 that is available for the .NET Framework 4. This hotfix rollup is available to fix several issues in the Microsoft .NET Framework 4. For more information about the issues that the hotfix resolves, see the "More information" section.

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: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.


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

Restart requirement

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

Hotfix replacement information

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

Issues that this hotfix rollup resolves

Common language runtime (CLR) issue

When you are using some non-English operating systems, the PerformanceCounterCategory.GetCategories method cannot return a list of performance counter categories. Additionally, a .NET Framework application returns no values when you run code that resembles the following to enumerate performance counter categories:
PerformanceCounterCategory[] categories;
categories = PerformanceCounterCategory.GetCategories();
Console.WriteLine(categories.Length + " categories are registered on this computer");
After you apply the hotfix, you must add the following LocalizedPerfCounter configuration key to the application configuration file for your .NET Framework application:
<add key="LocalizedPerfCounter" value="true" />

ASP.NET issue

Assume that you have a computer that has Internet Explorer 10 standard mode enabled. When you click the Image Control button in an UpdatePanel control on a webpage, you receive the following JavaScript error message:
SCRIPT5022: Sys.WebForms.PageRequestManagerServerErrorException: Input string was not in a correct format.

Windows Presentation Foundation (WPF) issue

Poor printing performance occurs when you use a.NET Framework 4.5-based WPF service to print to a Graphic Device Interface (GDI) printer on an operating system. This issue occurs if the following conditions are true:
  • The operating system that hosts the service uses a non-English locale.
  • The operating system has one of the following products installed:
    • WPF version 4.0
    • WPF version 4.5
    • WPF version 3.5 and the hotfix that is described in the following Microsoft Knowledge Base article (or an upgrade hotfix that includes this hotfix):
      980294 Characters in the Barcode font are printed in the Wingdings font in an XPS document that is created by using the .NET Framework 3.0
  • You print a document that has many blocks of text.
This issue occurs because a lookup operation occurs every time that the printing process calls a block of text to find the GDI font that is used to display the text. The resource usage of the lookup operation is increased by applying the hotfix that is described in Microsoft Knowledge Base (KB) article 980294, WPF version 4.0, and WPF version 4.5. Additionally, the resource usage of the lookup operation dominates the overall resource usage of the printing process. This hotfix resolves a known issue in the logic that caches the lookup operation results. After you apply the hotfix, the resource usage of the lookup operation occurs once per GDI font instead of occurring once per block of text. 

SQL Server issue

When you use the SQLBulkCopy class to transfer data that contains non-ASCII characters in Microsoft SQL Server 2008, the non-ASCII characters might be lost. For example, you use the SQLBulkCopy class to transfer the string data Ă to a table. After it is transferred, the string data is A instead of Ă.

Note This issue was fixed in a hotfix of the .NET Framework 2.0 that is described in the following Microsoft Knowledge Base article:
2635219 FIX: Non-ASCII data might be lost when you use the SQLBulkCopy class to transfer Non-ASCII data in SQL Server 2008


Id. de artículo: 2783767 - Última revisión: 18 mar. 2013 - Revisión: 1

Microsoft .NET Framework 4.0