Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Hotfix rollup 2937671 is available for the .NET Framework 3.5.1 on Windows 8.1 or Windows Server 2012 R2

View products that this article applies to.


This article describes hotfix rollup 2937671 for the Microsoft .NET Framework 3.5.1 This hotfix rollup fixes several issues in the .NET Framework 3.5.1. For more information about the issue that the hotfix rollup resolves, see the "More Information" section.

This hotfix rollup is available for the following operating systems:
  • Windows 8.1
  • Windows Server 2012 R2

↑ Back to the top

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 .NET Framework 3.5.1 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 exit all .NET Framework-based applications before you apply this hotfix.

Hotfix replacement information

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

File information
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 the .NET Framework 3.5.1 in Windows 8.1 and Windows Server 2012 R2

File nameFile versionFile sizeDateTime,24815-Nov-201317:21,67215-Nov-201317:27,57615-Nov-201317:25,76815-Nov-201317:32,20815-Nov-201317:24,76815-Nov-201317:36,57615-Nov-201317:25,86415-Nov-201317:28,05615-Nov-201317:21,86415-Nov-201319:41,76815-Nov-201318:07,15215-Nov-201317:59,76815-Nov-201319:42,48015-Nov-201317:47,76815-Nov-201317:57,67215-Nov-201317:27,67215-Nov-201317:31,67215-Nov-201317:32,82415-Nov-201317:36,57615-Nov-201317:30,67215-Nov-201317:29,28815-Nov-201317:31,38415-Nov-201317:30,062,65611-Mar-201422:08,23215-Nov-201317:21,98415-Nov-201317:27,60015-Nov-201317:25,17615-Nov-201317:32,53615-Nov-201317:24,98415-Nov-201317:36,69615-Nov-201317:25,08015-Nov-201317:29,46415-Nov-201317:21,17615-Nov-201319:41,98415-Nov-201318:07,94415-Nov-201317:59,08015-Nov-201319:42,40815-Nov-201317:47,46415-Nov-201317:57,98415-Nov-201317:27,79215-Nov-201317:31,88815-Nov-201317:32,67215-Nov-201317:36,60015-Nov-201317:30,79215-Nov-201317:29,83215-Nov-201317:31,02415-Nov-201317:30,025,79211-Mar-201422:08

For all supported x64-based versions of the .NET Framework 3.5.1 in Windows 8.1 and Windows Server 2012 R2

File nameFile versionFile sizeDateTime,062,65611-Mar-201422:08,025,79211-Mar-201422:08,24815-Nov-201317:35,67215-Nov-201318:35,57615-Nov-201317:47,76815-Nov-201318:57,20815-Nov-201317:47,76815-Nov-201318:41,57615-Nov-201317:42,86415-Nov-201318:35,05615-Nov-201318:32,86415-Nov-201317:46,76815-Nov-201317:52,15215-Nov-201317:59,76815-Nov-201317:53,48015-Nov-201317:47,76815-Nov-201317:43,67215-Nov-201318:34,67215-Nov-201318:42,67215-Nov-201318:35,82415-Nov-201318:40,57615-Nov-201318:53,67215-Nov-201318:48,28815-Nov-201318:58,38415-Nov-201318:57,062,65611-Mar-201422:08,23215-Nov-201317:35,98415-Nov-201318:35,60015-Nov-201317:47,17615-Nov-201318:57,53615-Nov-201317:47,98415-Nov-201318:41,69615-Nov-201317:42,08015-Nov-201318:35,46415-Nov-201318:32,17615-Nov-201317:46,98415-Nov-201317:52,94415-Nov-201317:59,08015-Nov-201317:53,40815-Nov-201317:47,46415-Nov-201317:43,98415-Nov-201318:34,79215-Nov-201318:42,88815-Nov-201318:35,67215-Nov-201318:40,60015-Nov-201318:53,79215-Nov-201318:48,83215-Nov-201318:58,02415-Nov-201318:57,025,79211-Mar-201422:08

↑ Back to the top

Issue that this hotfix rollup resolves

Issue 1

When you have a Windows Forms application that is running on a 64-bit operating system, the CheckedListBox or ComboBox control may not paint its items, and the control looks empty. This issue occurs because the control does not receive a WM_DRAWITEM message from its parent window. This issue occurs when the following conditions are true:
  • The owner-drawn control such as CheckedListBox has a negative window handle value.
  • The owner-drawn control's window handle is created in the constructor for the control’s parent form.
Negative window handles are created on the checked version of the 64-bit operating system, or when the handle is re-created many times on a retail build of the 64-bit operating system, such as when the application is running for a long time.

Usually, the control’s window is not created in the control's constructor. Therefore, the handle is also not created until after the parent form constructor is invoked. The second condition happens only when creation of the window handle is forced in the parent form constructor. One of the ways to force this creation is to change certain properties of the control, such as the BorderStyle property. When the child control’s handle is created before the parent's handle, the child control is temporarily parented to another window, and is re-parented later when the parent window is created. After the control is re-parented, the WM_DRAWITEM message is not routed correctly.

This hotfix fixes the message routing from the parent form to the owner-drawn control.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbexpertiseadvanced, kbfix, kbhotfixserver, kb

↑ Back to the top

Article Info
Article ID : 2937671
Revision : 1
Created on : 1/7/2017
Published on : 4/14/2014
Exists online : False
Views : 275