Hotfix rollup 3035803 (Web Installer) for the .NET Framework 4.5, 4.5.1, and 4.5.2 on Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012, and Windows Server 2012 R2

This article describes hotfix rollup 3035803 that is available for the Microsoft .NET Framework 4.5.2, the .NET Framework 4.5.1, and the .NET Framework 4.5. For more information about the issues that the hotfix rollup resolves, see the "Issues that this hotfix rollup resolves" section.

The web installer is a small package (less than one megabyte) that automatically determines and downloads only the components that are applicable for a particular platform.
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.5.2, the .NET Framework 4.5.1, or the .NET Framework 4.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.

Detecting the installed hotfix

To detect the successful installation of hotfix rollup 3035803 for the .NET Framework 4.5 and later versions, check the release keyword to determine the installed version. To be forward-compatible, you can check for a value that is greater than or equal to the value that is listed in this table.

Hotfix Rollup VersionValue of the Release DWORD
Hotfix rollup 3035803 for the .NET Framework 4.5 and later versions379970

For more information about how to check installed versions of the .NET Framework, see the following MSDN article:


Issues that this hotfix rollup resolves

Issue 1

Assume that you have a 32-bit Windows Presentation Foundation (WPF) application on a 64-bit operating system. When the application repeatedly calls the PrintQueue.GetPrintCapabilities method (or other related printing methods, such as PrintQueue.Dispose), a memory leak occurs in a separate process that is running dllhost.exe.

Note This issue usually occurs when you enclose the PrintQueue object in the following "using" block:
using (var printQueue = new PrintQueue(printServer, printerName)){ ... use printQueue ... }

Issue 2

When you enable the UI virtualization for a list control such as ListBox, DataGrid, ListView, or TreeView in a WPF application, you encounter the following issues:
  • NullReferenceException or ArgumentException
  • Scrolling to an unexpected location
  • Infinite loop, or hanging
  • StackOverflow exception
  • Failure when you scroll to the last page
Cause

Frequently, these issues occur when a VirtualizingStackPanel class discovers that one or more of its children has changed height, at some time other than during the first measure request from its parent. For convenience, we refer to this situation as a "bottom-up height change". This situation includes the following examples:
  • Expand or collapse a hierarchical child (TreeViewItem or GroupItem)
  • Recycle a child when the new data yields a different height than the old data (when VirtualizingMode="Recycling" is set)
  • Use a UserControl whose content depends on data outside the control
  • Run handlers declared by the application for layout-related events such as Loaded or LayoutUpdated
  • Data binding to data outside the child (for example use AncestorType or ElementName in the binding)
The VirtualizingStackPanel class cannot always handle this situation correctly, this may cause the issues previously described.

Notes
  • The logic has now been improved to fix the issues arising from "bottom-up height changes".
  • The "bottom-up height change" situation is responsible for most of the scrolling and measurement issues that have reported to Microsoft, but not for them all. The same issues can occur for other reasons that are not addressed by this fix.
Issue 3

Assume that you have applied the January update. In this situation, performance degradations and instability occurs on the systems that rely on Background Garbage Collection. This issue occurs because the Garbage Collector was updated to make the "memory write watch" (MEM_WRITE_WATCH) feature required rather than optional. This update re-enables the MEM_WRITE_WATCH feature as optional.

Issue 4

Assume that you have an IIS hosted WCF service is running on the .NET Framework 4.5.1 or 4.5.2. The service is set to require a client certificate in the IIS settings. However, the binding’s HttpsTransportBindingElement.RequireClientCertificate is false.

In this situation, WCF does not honor the IIS setting, and will not correctly validate the client certificate. It is possible to work around this issue by using a custom binding and setting the HttpsTransportBindingElement.RequireClientCertificate property to true.

Issue 5

Assume that you have a WCF service that is using transport security. The service has a binding with SecurityBindingElement.SecurityHeaderLayout that is set to a value other than the default of Strict.

In this situation, WCF ignores this property, so WCF clients could not communicate with the service even when using a correct layout. In order for WCF to honor this correctly, you have to add the following line to appSettings in your configuration file:
<appSettings><add key="wcf:useConfiguredTransportSecurityHeaderLayout" value="true" /></appSettings>

Properties

Article ID: 3035803 - Last Review: 01/25/2016 07:03:00 - Revision: 2.0

Microsoft .NET Framework 4.5.2, Microsoft .NET Framework 4.5.1, Microsoft .NET Framework 4.5

  • kbfix kbsurveynew kbexpertiseadvanced kbqfe KB3035803
Feedback