Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, your computer must be running one of the following Windows operating systems:
- Windows Vista Service Pack 2 (SP2)
- Windows Server 2008 Service Pack 2 (SP2)
- Windows 7
- Windows Server 2008 R2
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791
How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849
How to obtain the latest service pack for Windows Server 2008
Installation instructions
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. By default, this hotfix is not automatically enabled after you apply it. You must manually enable this hotfix at the system level or at the process level. After you enable this hotfix, the exception will be escalated to the Windows kernel to be processed.
When you enable this hotfix at the system level, all the processes that are running in the system are affected. When you enable this hotfix at the process level, only that specific process is affected. The hotfix setting at the process level supersedes the hotfix setting at the system level.
To enable this hotfix at the system level, follow these steps:
- In Registry Editor, locate the following registry subkey:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
- Create a registry entry of the DWORD value.
- Name the new registry entry DisableUserModeCallbackFilter.
- Set the value of the DisableUserModeCallbackFilter registry entry to 1.
To enable this hotfix at the process level, follow these steps:
- In Registry Editor, locate the following registry subkey:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
or HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
. - Create a registry subkey.
- Name the new registry subkey with the name of the process for which you want to enable the hotfix. For example, if you want to enable this hotfix on the Notepad.exe process, you name the new registry subkey "Notepad.exe."
- Under the new registry subkey, create a registry entry of the DWORD value.
- Name the new registry entry DisableUserModeCallbackFilter.
- Set the value of the DisableUserModeCallbackFilter registry entry to 1.
This hotfix also includes new functions that are exported by Kernel32.DLL. The applications can call these new functions to enable the hotfix at runtime. These new functions and flags are defined as the following:
BOOL
WINAPI
SetProcessUserModeExceptionPolicy(
__in DWORD dwFlags
);
BOOL
WINAPI
GetProcessUserModeExceptionPolicy(
__out LPDWORD lpFlags
);
#define PROCESS_CALLBACK_FILTER_ENABLED 0x1
By default, a new process is created by using the PROCESS_CALLBACK_FILTER_ENABLED flag set. The hotfix is enabled for a process by clearing the flag:
DWORD dwFlags;
If (GetProcessUserModeExceptionPolicy(&dwFlags)) {
SetProcessUserModeExceptionPolicy(dwFlags & ~PROCESS_CALLBACK_FILTER_ENABLED);
}
The Registry key is only intended for development scenarios. Independent software vendors (ISV) should not change the Image File Execution Options (IFEO) keys in their installers.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same package. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR), can be identified by examining the file version numbers as shown in the following table.
|
Version | Product | SR_Level | Service branch |
|---|
|
6.0.600
2
.
22xxx | Windows Vista and Windows Server 2008 | SP2 | LDR |
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
| File name | File version | File size | Date | Time | Platform | Service branch |
|---|
| Kernel32.dll | 6.0.6002.22267 | 1,218,560 | 12-Nov-2009 | 17:42 | x64 | Not Applicable |
| Ntdll.dll | 6.0.6002.22267 | 1,582,800 | 12-Nov-2009 | 17:48 | x64 | Not Applicable |
| Kernel32.dll | 6.0.6002.22267 | 858,624 | 12-Nov-2009 | 17:41 | x86 | WOW |
| Ntdll.dll | 6.0.6002.22267 | 1,165,592 | 12-Nov-2009 | 17:44 | x86 | WOW |
For all supported IA-64-based versions of Windows Server 2008
| File name | File version | File size | Date | Time | Platform | Service branch |
|---|
| Kernel32.dll | 6.0.6002.22267 | 2,185,216 | 15-Nov-2009 | 19:11 | Not Applicable | Not Applicable |
| Ntdll.dll | 6.0.6002.22267 | 2,564,168 | 15-Nov-2009 | 19:17 | IA-64 | Not Applicable |
| Kernel32.dll | 6.0.6002.22267 | 858,624 | 12-Nov-2009 | 17:41 | x86 | WOW |
| Ntdll.dll | 6.0.6002.22267 | 1,165,592 | 12-Nov-2009 | 17:44 | x86 | WOW |
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same package. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
| File name | File version | File size | Date | Time | Platform | Service branch |
|---|
| Kernel32.dll | 6.1.7600.20573 | 1,162,752 | 12-Nov-2009 | 20:02 | x64 | Not Applicable |
| Ntdll.dll | 6.1.7600.20573 | 1,737,320 | 12-Nov-2009 | 20:09 | x64 | Not Applicable |
| Kernel32.dll | 6.1.7600.20573 | 837,120 | 12-Nov-2009 | 19:55 | x86 | WOW |
| Ntdll.dll | 6.1.7600.20573 | 1,290,248 | 12-Nov-2009 | 19:58 | x86 | WOW |
For all supported IA-64-based versions of Windows Server 2008 R2
| File name | File version | File size | Date | Time | Platform | Service branch |
|---|
| Kernel32.dll | 6.1.7600.20573 | 2,137,088 | 12-Nov-2009 | 06:16 | IA-64 | Not Applicable |
| Ntdll.dll | 6.1.7600.20573 | 2,783,936 | 12-Nov-2009 | 17:35 | IA-64 | Not Applicable |
| Kernel32.dll | 6.1.7600.20573 | 837,120 | 12-Nov-2009 | 19:55 | x86 | WOW |
| Ntdll.dll | 6.1.7600.20573 | 1,290,248 | 12-Nov-2009 | 19:58 | x86 | WOW |