FIX: The deactivated event is not triggered in a .NET Framework 3.0-based WPF application after you move the focus from a Windows Forms control that is included in the WPF application to another application

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. You have a Microsoft .NET Framework 3.0-based Windows Presentation Foundation (WPF) application that contains a Windows Forms control and a WPF control.The focus is in the Windows Forms control in the WPF application. Then, you move the focus to another application. In this scenario, the deactivated event is not triggered in the WPF application. Additionally, if you have code in the deactivated event, the code is not executed.

Note This problem does not occur if the focus is in the WPF control before you move the focus.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 3.0 service pack that contains this hotfix.

To resolve this problem immediately, 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 Web site: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.


You must have Windows Vista Service Pack 1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.
Windows Vista with Service Pack 1, x86-based versions
File nameFile versionFile sizeDateTime
Msil_windowsformsintegration_31bf3856ad364e35_6.0.6001.22184_none_29160d3fe7b7cd54.manifestNot applicable4,45821-May-200804:00
Package_1_for_kb952605~31bf3856ad364e35~x86~~ applicable2,50722-May-200800:34
Package_2_for_kb952605~31bf3856ad364e35~x86~~ applicable2,34522-May-200800:34
Package_for_kb952605_client_1~31bf3856ad364e35~x86~~ applicable1,36722-May-200800:34
Package_for_kb952605_client~31bf3856ad364e35~x86~~ applicable1,43022-May-200800:34
Package_for_kb952605_server_0~31bf3856ad364e35~x86~~ applicable1,40222-May-200800:34
Package_for_kb952605_server~31bf3856ad364e35~x86~~ applicable1,43022-May-200800:34
X86_258880172cc47b3d75eaecb5326f9f9b_31bf3856ad364e35_6.0.6001.22184_none_3d28f8185f7474ec.manifestNot applicable65422-May-200800:34
X86_99a08a5f04e08fbb0859a9bdd4772a4a_31bf3856ad364e35_6.0.6001.22184_none_4d588772865b5545.manifestNot applicable65722-May-200800:34
X86_wpf-windowsformsintegration_31bf3856ad364e35_6.0.6001.22184_none_fa532df6952af639.manifestNot applicable4,02521-May-200803:58
Windows Vista with Service Pack 1, x64-based versions
File nameFile versionFile sizeDateTime
Amd64_258880172cc47b3d75eaecb5326f9f9b_31bf3856ad364e35_6.0.6001.22184_none_9947939c17d1e622.manifestNot applicable65622-May-200800:34
Amd64_d7266ab289213d0c53135d11c5d0f068_31bf3856ad364e35_6.0.6001.22184_none_0c03e1e4e37f81b4.manifestNot applicable98222-May-200800:34
Amd64_wpf-windowsformsintegration_31bf3856ad364e35_6.0.6001.22184_none_5671c97a4d88676f.manifestNot applicable4,83521-May-200804:38
Msil_windowsformsintegration_31bf3856ad364e35_6.0.6001.22184_none_29160d3fe7b7cd54.manifestNot applicable4,45821-May-200804:00
Package_1_for_kb952605~31bf3856ad364e35~amd64~~ applicable2,71622-May-200800:34
Package_2_for_kb952605~31bf3856ad364e35~amd64~~ applicable2,55222-May-200800:34
Package_for_kb952605_client_1~31bf3856ad364e35~amd64~~ applicable1,37522-May-200800:34
Package_for_kb952605_client~31bf3856ad364e35~amd64~~ applicable1,43822-May-200800:34
Package_for_kb952605_server_0~31bf3856ad364e35~amd64~~ applicable1,41022-May-200800:34
Package_for_kb952605_server~31bf3856ad364e35~amd64~~ applicable1,43822-May-200800:34
X86_wpf-windowsformsintegration_31bf3856ad364e35_6.0.6001.22184_none_fa532df6952af639.manifestNot applicable4,02521-May-200803:58
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 952605 - Last Review: 11/02/2013 17:40:00 - Revision: 3.0

Microsoft .NET Framework 3.0

  • kbnosurvey kbarchive kbexpertiseadvanced kbfix kbqfe KB952605