What time functions are updated?

The following time functions are updated by this update:

• SystemTimeToTzSpecificLocalTime() Converts a time in Coordinated Universal Time (UTC) to a specified time zone’s corresponding local time.
• TzSpecificTimeToSystemTime() Converts a local time to a time in Coordinated Universal Time (UTC).

Note The functions that are listed here use a TIME_ZONE_INFORMATION structure that specifies the START DATE and the END DATE for daylight saving time (DST). By default, the current DST rules are used when no such structure is provided.

Back to the top

When to use these functions in an application

Most date and time stamps that are created and displayed in Windows and in many applications are stored as UTC. Then, they are rendered in local time by using system APIs. Examples of these include Windows file time stamps, Outlook sent and received dates, and event logging time stamps.

Not all built-in, Windows-based applications use these newly updated APIs. However, they are available to all applications, including third-party applications. These functions are useful in many scenarios, such as a user auditing scenario in which the ability to use DST rules for previous years on a current Windows service pack is important.

Generally, if an application requires historically accurate time stamps, these functions should be used.

Back to the top

How to use these functions in an application

For information about syntax, parameters, return value, and examples on how to use these functions in an application, please visit the following Microsoft Developer Network (MSDN) Web sites:

SystemTimeToTzSpecificLocalTime Function

TzSpecificLocalTimeToSystemTime Function

Note This article supersedes article 944340, which describes an earlier version of these APIs. This update improves the performance of the functions, and enables historically accurate time-stamp lookup functionality that was introduced in 944340.

This update applies to the following Windows operating systems:

• Windows XP Service Pack 3 (SP3)
• Windows Server 2003 Service Pack 2 (SP2)
• Windows Vista Service Pack 1 (SP1)
• Windows Server 2008

Back to the top

Hotfix information for Windows XP

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 this specific problem.

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, submit a request to 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, you must have Windows XP SP3 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

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

Hotfix replacement information

This hotfix replaces the following hotfix:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

File information

The English 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 XP with Service Pack 3, x86-based versions

Back to the top

Hotfix information for Windows Server 2003

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, you must have the following installed:

• Windows Server 2003 SP2

  For more information, click the following article number to view the article in the Microsoft Knowledge Base:

  889100  (/Feedback.aspx?kbNumber=889100/ ) How to obtain the latest service pack for Windows Server 2003
• The 944340 hotfix

  For more information, click the following article number to view the article in the Microsoft Knowledge Base:

  944340  (/Feedback.aspx?kbNumber=944340/ ) The time stamps are incorrect after you apply update 928388 and then change the time settings to a year that is earlier than 2007 in Windows XP and in Windows Server 2003

Restart requirement

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

Hotfix replacement information

This hotfix replaces the following hotfix:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

File information

The English 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 Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Back to the top

Hotfix information for Windows Vista and for Windows Server 2008

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 on Windows Vista-based computer, you must have Windows Vista SP1 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English 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 and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

Back to the top

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported IA-64-based versions of Windows Server 2008

Back to the top

Back to the top

Back to the top

To resolve this issue, you have to check the Windows Vista registry for a specific registry subkey. If that subkey is present, you have to delete the InputPersonalization registry subkey, and then you must restart Windows Vista.

Note When you delete the InputPersonalization subkey, this forces the Handwriting recognition personalization tool to re-create the InputPersonalization registry subkey. When the InputPersonalization subkey is re-created, the Search feature is reactivated.

To do this, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2.	Locate and then click the following subkey in the registry: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Search Gathering Manager Applications Windows PluginManagers 3
3.	If the subkey in step 2 is present, locate and then click the following subkey in the registry: HKEY_LOCAL_MACHINE SOFTWARE Microsoft InputPersonalization
4.	On the Edit menu, click Delete, and then click Yes.
5.	Exit Registry Editor.
6.	Restart Windows Vista.

Back to the top

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous 2007 Office suites fix release. We recommend that you consider applying the most recent fix release that contains the hotfix that you need.

Back to the top

How to obtain the August 2008 cumulative update packages

A set of supported cumulative update packages are now available from Microsoft. However, each package is intended to correct only the applications that are listed in this article. Apply the packages only to systems that are experiencing these specific problems. If you are not severely affected by any of these problems, we recommend that you wait for the next 2007 Office suites service pack that contains the hotfixes in these cumulative update packages.

Note If additional issues occur or 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 a specific cumulative update package. To create a separate service request, visit the following Microsoft Web site:

Back to the top

Packages that are included in the August 2008 cumulative update

A link to a Microsoft Knowledge Base article that discusses each hotfix will be released as the article becomes available. To obtain a specific hotfix, please contact support and ask for the hotfix by referencing the Knowledge Base article number.

For more information about the 2007 Office suite bugs, click the following article numbers to view the articles in the Microsoft Knowledge Base.

Hotfix package name	Knowledge Base article number	Product
Access.msp	956054 (/Feedback.aspx?kbNumber=956054/) Description of the Access 2007 hotfix package (Access.msp): August 26, 2008	Access
Ace.msp	956838 (/Feedback.aspx?kbNumber=956838/) Description of the Access 2007 hotfix package (Ace.msp): August 26, 2008	Access
Excel.msp, Oart.msp	956798 (/Feedback.aspx?kbNumber=956798/) Description of the Excel 2007 hotfix package (Excel.msp, Oart.msp): August 26, 2008	Excel
Excel.msp, Xlconv.msp	956836 (/Feedback.aspx?kbNumber=956836/) Description of the Excel 2007 hotfix package (Excel.msp, Xlconv.msp): August 26, 2008	Excel Converter
Excel.msp, Xlconv.msp, Graph.msp	956511 (/Feedback.aspx?kbNumber=956511/) Description of the Excel 2007 hotfix package (Excel.msp, Xlconv.msp, Graph.msp): August 26, 2008	Excel Converter
Excel-xx-xx.msp (Localized – All Languages) Not Global	956510 (/Feedback.aspx?kbNumber=956510/) Description of the Excel 2007 hotfix package (Excel-xx-xx.msp): August 26, 2008	Excel Localized
Ifswfe.msp	956315 (/Feedback.aspx?kbNumber=956315/) Description of the Forms Server 2007 hotfix package (Ifswfe.msp): August 26, 2008	Forms Server
Ipeditor.msp;infopath.msp	956314 (/Feedback.aspx?kbNumber=956314/) Description of the InfoPath 2007 hotfix package (Ipeditor.msp, Infopath.msp): August 26, 2008	InfoPath
Coreserver.msp	956056	SharePoint Server
Gfonts.msp	956514 (/Feedback.aspx?kbNumber=956514/) Description of the 2007 Office hotfix package (Gfonts.msp): August 26, 2008	Fonts
Ime32.msp	956793 (/Feedback.aspx?kbNumber=956793/) Description of the Input Method Editor (Japanese) 2007 hotfix package (Ime32.msp): August 26, 2008	English Assist
Msdaipp.msp	956790 (/Feedback.aspx?kbNumber=956790/) Description of the 2007 Office system hotfix package (Msdaipp.msp): August 26, 2008	Internet Publishing Provider
Mso.msp	956506 (/Feedback.aspx?kbNumber=956506/) Description of the 2007 Office system hotfix package (Mso.msp): August 26, 2008	Office Core
Graph.msp, Excel.msp, Xlconv.msp, Xlview.msp	956796 (/Feedback.aspx?kbNumber=956796/) Description of the 2007 Office system hotfix package (Graph.msp, Excel.msp, Xlconv.msp, Xlview,msp): August 26, 2008	Excel Converter, Excel Viewer
Oart.msp; OartConv.msp	956058 (/Feedback.aspx?kbNumber=956058/) Description of the 2007 Office hotfix package (Oart.msp, OartConv.msp): August 26, 2008	Office Art
Outlook.msp	956059	Outlook
PowerPoint.msp	956316 (/Feedback.aspx?kbNumber=956316/) Description of the PowerPoint 2007 hotfix package (PowerPoint.msp): August 26, 2008	PowerPoint
RichEd20.msp	956801 (/Feedback.aspx?kbNumber=956801/) Description of the PowerPoint 2007 hotfix package (RichEd20.msp): August 26, 2008	Rich Edit
Project.msp	956060 (/Feedback.aspx?kbNumber=956060/) Description of the Project 2007 hotfix package (Project.msp): August 26, 2008	Project
Pjsrvapp.msp, Pjsrvwfe.msp	956061	Project Server
Visio.msp	956063 (/Feedback.aspx?kbNumber=956063/) Description of the Visio 2007 hotfix package (Visio.msp): August 26, 2008	Visio
Visio.msp (ru-ru) Localized	956837	Visio Localized (Russian)
Visio.msp, Vviewer.msp	956791 (/Feedback.aspx?kbNumber=956791/) Description of the Office Visio 2007 hotfix package (Visio.msp, Vviewer.msp): August 26, 2008	Visio Viewer
Word.msp	956064	Word
Word.msp, Wordconv.msp	956795 (/Feedback.aspx?kbNumber=956795/) Description of the Word 2007 hotfix package (Word.msp, Wordconv.msp): August 26, 2008	Word Converter
Sts.msp	956057	Windows SharePoint Services
Wssmui.msp {All languages}	957109 (/Feedback.aspx?kbNumber=957109/) Description of the Windows SharePoint Services 3.0 hotfix package (Wssmui.msp): August 26, 2008	Windows SharePoint Services

Back to the top

Prerequisites

Prerequisites are listed in the KB articles for the individual packages.

Back to the top

This problem is caused by a bug in the GetVolumeNameForVolumeMountPoint Win32 API function on the products listed in the Applies to section of this article.  It occurs only for volumes that have been assigned multiple unique volume names (GUIDs).

The problem has been corrected in the following products:

• Windows Server 2008  — All versions
• Windows Vista Service Pack 1

 

Back to the top

Applications that must run on the affected products can work around this bug in one of two ways.  The first is to open the volume with the CreateFile Win32 function and then calling the DeviceIoControl function to issue the IOCTL_MOUNTMGR_QUERY_POINTS command. 

The second way is by calling GetVolumeNameForVolumeMountPoint twice.  In the first call, pass the target volume name as documented (usually as a the drive letter in the format X: ) in the lpszVolumeMountPoint parameter.  This call will return one of the assigned unique volume names in the lpszVolumeName parameter.  In the second call, pass the volume name returned by the first call in the lpszVolumeMountPoint parameter.  This will cause GetVolumeNameForVolumeMountPoint to return the expected volume name.

The sample below to see how you might call GetVolumeNameForVolumeMountPoint() twice to get the expected results. 

#include <windows.h>
#include <stdio.h>
#include <tchar.h>

int _tmain(int argc, TCHAR* argv[])
{

    TCHAR szGUID1 [MAX_PATH];
    TCHAR szGUID2 [MAX_PATH];

    if (argc != 2)
    {
        wprintf(L%s <x: > n n, argv[0]);
        return 0;
    }

    _tprintf(TEXT(Calling GetVolumeNameForVolumeMountPoint for %s n), argv[1]);

    // On the first call to GetVolumeNameForVolumeMountPoint
    // pass in whatever you would normally pass in
    if (GetVolumeNameForVolumeMountPoint(argv[1], szGUID1, MAX_PATH))
    {
        _tprintf(TEXT( GUID1: %s n n), szGUID1);
    }

    // On the second call, pass in the Volume Name received from the first
    // call to GetVolumeNameForVolumeMountPoint
    if (GetVolumeNameForVolumeMountPoint(szGUID1, szGUID2, MAX_PATH))
    {
        _tprintf(TEXT( GUID2: %s n n), szGUID2);
    }
    return 0;
}

CreateFile, DeviceIoControl, and IOCTL_MOUNTMGR_QUERY_POINTS are documented in the MSDN Library on http://msdn.microsoft.com (http://msdn.microsoft.com) .

Back to the top

A volume can be multiple unique volume names (and thus multiple GUIDs) when it is used by multiple running installations of Windows.  This could happen in the following scenarios and in similar scenarios where multiple installations of Windows have accessed the volume:

• Dual booting two or more copies of Windows which access the drive.
• Using a volume on a shared disk in a cluster where multiple nodes have accessed the volume.
• Moving the disk which hosts the volume from one computer to another.
• In a SAN environment where the volume was assigned to multiple instances of Windows.

In these situations, each running instance of Windows will assign its own GUID to the volume.  Furthermore, each instance will enumerate all of the volume names and mount points assigned to the volume and thus will see multiple GUIDs.  However, not all GUIDs may be used by the specific instance of Windows that is currently running.  This is why the volume name returned by GetVolumeNameForVolumeMountPoint may be incorrect.

The MOUNTVOL.EXE tool always returns the correct volume name.

 

Back to the top

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Note If the application does not capture the exception that is returned by CDao on the insertion or the update, the database will not have the updates that you intended to make.

Back to the top

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

The Microsoft .NET Framework 2.0 Configuration tool only applies to 32-bit assemblies (i.e. assemblies compiled with the Target CPU set to x86). This is also true for the mscorcfg.msc MMC snap-in located in the Program Files Microsoft.NET SDK v2.0 64 bit bin folder.

This behavior is by design.

Back to the top

Run Caspol.exe for the 64-bit version of the .NET Framework 2.0 to configure security policy for 64-bit applications.

1. Open a 64-bit .NET framework SDK command prompt or the Visual Studio x64 Command prompt.
2. Run caspol.exe to make the policy changes.

You can verify changes to the security policies saving them out to a text file and comparing. To save the policies to a text file, run the following command using both the 32-bit and 64-bit versions of Caspol.exe

Caspol –all –l > c: policy.txt

Back to the top

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

1. Install the hotfix package that was released on August 26, 2008.For more information about the hotfix package, click the following article number to view the article in the Microsoft Knowledge Base:
   956506  (/Feedback.aspx?kbNumber=956506/ ) Description of the 2007 Office system hotfix package (Mso.msp): August 26, 2008
2. Set the FailOnCRLServerOffline registry entry. To do this, follow these steps:
   1. Start Registry Editor.
      • In Windows Vista, click Start
        Collapse this imageExpand this image

        

        , type regedit in the Start Search box, and then press ENTER.

        Collapse this imageExpand this image

        

        If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

      • In Windows XP, click Start, click Run, type regedit in the Open box, and then click OK.
   2. Locate and then right-click the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Common Signatures
   3. On the Edit menu, point to New, and then click DWORD Value.
   4. Type FailOnCRLServerOffline, and then press ENTER.
   5. Right-click FailOnCRLServerOffline, and then click Modify.
   6. In the Value data box, type 1, and then click OK.
   7. On the File menu, click Exit to exit Registry Editor.

Back to the top

In this scenario, the IME Conversion Mode is unexpectedly changed to half-shape mode.

Note This issue occurs only the first time that you switch the focus. If the application continues running, the IME status is maintained as expected.

Back to the top

Back to the top

Hotfix information

A supported hotfix is now 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 this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Vista service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English 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, x86-based versions

Windows Vista, x64-based versions

Windows Vista, IA-64-based versions

Back to the top

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Back to the top

When you run a full-screen application, such as a game, the Windows Sidebar may flash or appear on top of the application or game briefly.

Back to the top

Full screen applications or games which do not create a full-screen window may cause the Windows Sidebar to unexpectedly receive an indication that the mouse is over the Windows Sidebar. When this happens the Windows Sidebar will try an animation to fade in, which is normal behavior. However, an issue will underlying technologies (layered windows) will cause the Sidebar to flash into view despite the application or game being topmost.

Back to the top

The Windows Sidebar can be closed before you run the application or game, or can be set to be Sidebar is always on top of other windows . Or, the code for the application or game can be modified to create a full-screen window, rather than a topmost window the size of the current screen.

To close the Windows Sidebar, right-click Windows Sidebar, and then click Close Windows Sidebar.

To set the Sidebar is always on top of other windows option, follow these steps:

1. Right-click Windows Sidebar, and then click Properties.

2. Click to select the Sidebar is always on top of other windows check box, and then click OK.

Back to the top

Repro Steps

==========

To reproduce this issue, follow these steps:

1.       Make sure Windows Sidebar is not set to Sidebar is always on top of other windows.

2.        Start application which uses Direct 3D.

3.       Move mouse around, typically toward upper-right of the screen. Sidebar should flash and appear for some time.

Back to the top

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Note If the application does not capture the exception that is returned by CDao on the insertion or the update, the database will not have the updates that you intended to make.

Back to the top

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Back to the top

Back to the top

The Debug Diagnostics 1.1 tool is available as a stand-alone tool. To obtain the Debug Diagnostics 1.1 tool, visit the following Microsoft Web site:

Note The Debug Diagnostics 1.0 tool is available as part of the IIS Diagnostics Toolkit 1.0 or as a stand-alone tool.

Back to the top

Back to the top

Components of the Debug Diagnostics 1.1 tool

The Debugging Service

The Debugging Service (Dbghost.exe) performs the following actions:

•	Attaches the host to and detaches the host from running processes
•	Collects performance monitor data
•	Contacts a server and uses the HttpStatusCode enumeration to determine the status of the server. This operation is also known as an HTTP ping.
•	Monitors memory leaks in running processes
•	Collects debugging session state information
•	Shows the state of each defined rule

The Debugger Host

The Debugger Host (Dbghost.exe) hosts the Windows Symbolic Debugger Engine (Dbgeng.dll). The Debugger Host attaches processes to the Windows Symbolic Debugger Engine and generates memory dumps. The Debugger Host also hosts the primary module that is used to analyze memory dumps.

Note The Debugger Host is not dependent on the Debug Diagnostic service (Dbgsvc.exe).

The user interfaces

The user interfaces (Debugdiag.exe and Debugdiaganalysisonly.exe) in the Debug Diagnostics 1.1 tool are interfaces that are used to analyze memory dumps, automate creating control scripts, and display the status of running processes. These processes include services.

The Debug Diagnostics 1.1 tool includes three views:

•	Rules Uses a wizard to create control scripts for the debugger host
•	Advanced analysis Runs the selected analysis script on one or more memory dump files
•	Processes Displays the status of running processes and scripts

Back to the top

How to use the Debug Diagnostics 1.1 tool

Before you start the Debug Diagnostics 1.1 tool, you must identity the kind of issue that you are experiencing. For example, determine whether the application stops responding, crashes, performs slowly, or leaks memory. After you know the kind of issue, you can configure the Debug Diagnostics 1.1 tool to gather the correct data. Then, you can use the data to determine and resolve the cause of the problem.

Debug a process crash

Typically, a process crash indicates that an unhandled exception in a process or code that is running in a process has terminated the process. To debug a process crash, create a crash rule on the process. You can attach the Debug Diagnostics 1.1 tool to a specific process. The Debug Diagnostics 1.1 tool monitors the process for any exception or custom breakpoint that causes the process to terminate unexpectedly. When a crash occurs, a memory dump file is created in the folder that is specified in the rule.

For more information about how to create a crash rule, click the following article number to view the article in the Microsoft Knowledge Base:

Debug a process that stops responding or a slow performance issue

Use one of the following methods.

Method 1: Create a hang rule

The hang monitoring feature is designed to troubleshoot IIS process performance issues. For example, you can create a hang rule to troubleshoot an issue in which pages in a Web application take longer than expected to load or do not load at all.

When you create a hang rule and then specify a process and URL to monitor, you must also specify a ping interval and a response time-out value. The Debug Diagnostics 1.1 tool sends a request to the server at configured intervals. If the server does not respond before the configured time-out, a memory dump file is generated for the specified process.

For more information about how to create a hang rule, click the following article number to view the article in the Microsoft Knowledge Base:

Method 2: Manually create a memory dump file for the process

When the process stops responding or performs slowly, you can manually create a memory dump file. To manually create a memory dump file for a process, right-click the process in the Processes view, and then click Create Full Userdump.

Debug memory or handle usage

Use one of the following methods.

Method 1: Create a leak rule

When you create a leak rule against a process, the Leaktrack.dll file is injected into the process to track memory usage and handle usage over time. When you configure a memory leak rule or a handle leak rule, you can configure the Debug Diagnostics 1.1 tool to generate the memory dump file that is based on time or memory usage.

Method 2: Manually create a memory dump file

To do this, right-click the process in the Processes view, and then click Monitor For Leaks. When the process grows to a problem size, right-click the process, and then click Create Full Userdump.

For more information about how to create a memory and handle leak rule, click the following article number to view the article in the Microsoft Knowledge Base:

Analyze memory dump files

The Debug Diagnostics 1.1 tool can analyze a memory dump file and generate a report file that includes the analysis. Additionally, the report file includes recommendations to resolve the problems that are identified.

The Debug Diagnostics 1.1 tool uses analysis scripts to analyze the process dump file. The following analysis scripts are used most frequently:

•	Crash/hang analyzers The crash/hang script analyzes exception information in the dump file if a crash is detected. The crash/hang script also analyzes the dump file for issues that are known to cause a hang condition. This script includes IIS, Microsoft Data Access Components, COM+, and Windows Socket information that is related to the process.
•	Memory pressure analyzers The memory pressure analysis script analyzes the memory usage of a process and displays the data that is gathered by the Leaktrack.dll file.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

For example, a Windows Server 2008-based domain controller randomly becomes unresponsive to LDAP requests. After this issue occurs, you have to restart the server.

Back to the top

A thread owns a critical section and calls the closesock function. However, the closesock function never returns. Therefore, other threads cannot access the critical section and stop responding.

Back to the top

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 this specific problem. 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have Windows Server 2008 or Windows Vista SP1 installed on the computer.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English 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 Server 2008 and Windows Vista note

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

For all supported x64-based versions of Windows Server 2008 and Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported Itaniuim-based versions of Windows Server 2008

Back to the top

Back to the top

Issues that this hotfix package fixes

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	In Microsoft Office Word 2007, when you use a Microsoft Visual Basic for Applications (VBA) macro to communicate with an application by using a COM interface, the macro takes a long time to finish. When you run the same macro in Microsoft Office Word 2003, the macro runs much faster.
•	Consider the following scenario: • In Word 2007, a document that is in the portrait orientation has frames that contain vertical text. • Or, in Word 2007, a document that is in the landscape orientation has frames that contain horizontal text. • You print this document to a regular printer or to a Microsoft XPS Document Writer printer. In this scenario, the text may be missing or truncated. This issue also occurs when you save the document in the Microsoft XPS format or in the PDF format.
•	Consider the following scenario. In Word 2007, you enable the AutoSave feature. You open a document that is located in a share folder. You edit a text box in the document. While you edit the text box, Word 2007 starts to save the AutoRecover information automatically. In this scenario, Word 2007 may close unexpectedly.
•	In Word 2007, when you try to open a Word document that is created by an earlier version of Word, Word 2007 stops responding. However, the document can be opened correctly in Word 2002 and in Word 2003.

Back to the top

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 this specific problem. 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

There are no prerequisites for installing this hotfix.

Restart information

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

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.
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.Download information

File name	File version	File size	Date	Time	Platform
Office-kb952701-fullfile-x86-glb.exe	12.0.6300.5000	15,875,864	09-May-2008	21:25	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,251,584	10-May-2008	00:58	Not Applicable
Wordconv.msp	Not Applicable	6,216,192	10-May-2008	00:58	Not Applicable

After the hotfix is installed, the Global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Word.msp

Wordconv.msp

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Back to the top

When you run a full-screen application, such as a game, the Windows Sidebar may flash or appear on top of the application or game briefly.

Back to the top

Full screen applications or games which do not create a full-screen window may cause the Windows Sidebar to unexpectedly receive an indication that the mouse is over the Windows Sidebar. When this happens the Windows Sidebar will try an animation to fade in, which is normal behavior. However, an issue will underlying technologies (layered windows) will cause the Sidebar to flash into view despite the application or game being topmost.

Back to the top

The Windows Sidebar can be closed before you run the application or game, or can be set to be Sidebar is always on top of other windows . Or, the code for the application or game can be modified to create a full-screen window, rather than a topmost window the size of the current screen.

To close the Windows Sidebar, right-click Windows Sidebar, and then click Close Windows Sidebar.

To set the Sidebar is always on top of other windows option, follow these steps:

1. Right-click Windows Sidebar, and then click Properties.

2. Click to select the Sidebar is always on top of other windows check box, and then click OK.

Back to the top

Repro Steps

==========

To reproduce this issue, follow these steps:

1.       Make sure Windows Sidebar is not set to Sidebar is always on top of other windows.

2.        Start application which uses Direct 3D.

3.       Move mouse around, typically toward upper-right of the screen. Sidebar should flash and appear for some time.

Back to the top

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

For example, you create a customization file to install Microsoft Office OneNote 2007 and to generate a custom OneNote shortcut in the following location:

After you use this customization file, you notice that the OneNote shortcut is not generated in the following location as expected:

Instead, you notice that the shortcut is generated in the following location:

Back to the top

Installations of the 2007 Office system are per-computer. Therefore, the shortcuts are put in the CommonAppDataFolder folder instead of in the AppDataFolder folder.

Back to the top

After all per-user files and all registry entries are added by using the OCT, the shortcuts are copied to a user’s profile the next time that the user runs a 2007 Office application.

If you want the shortcuts to be copied to the profile before the user starts a 2007 Office application, you can add a registry entry that will run a one-time start of a 2007 Office application during the logon process.

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.

To run a one-time start of a 2007 Office application during the logon process, use the Add registry entries section of the OCT to add a registry entry that resembles the following registry entry:

Back to the top

Back to the top

Note For more information about how to troubleshoot program compatibility, see the Additional information section.

If you have a software program that is not Windows Vista-compatible, you still may be able to get it to run on Windows Vista by using the individual program’s Compatibility tab or by using any of the troubleshooting methods that are referenced in this article.

Back to the top

Applications that have earned the Certified for Windows Vista logo

The Certified for Windows Vista logo is a compatibility designation for applications and devices that have passed a rigorous testing program on computers that are running Windows Vista. The technical requirements for this designation target four core areas: reliability, security, compatibility with Windows Vista and future operating systems, and installation and removal.

To view the list of applications that have earned the Certified for Windows Vista logo, visit the following Microsoft Web site:

Back to the top

Applications that have earned the Works with Windows Vista logo

The Works with Windows Vista logo is a compatibility designation that is designed to encourage Windows Vista compatibility for the current generation of Windows-based applications. To receive this designation, software companies test their applications to make sure that the applications meet the program’s guidelines.

To view the list of applications that have earned the Works with Windows Vista logo, visit the following Microsoft Web site:

Back to the top

Windows Vista Upgrade Advisor

The Windows Vista Upgrade Advisor will help you determine whether your Windows XP-based computer can run Windows Vista. You can also use the Upgrade Advisor to determine whether your Windows Vista-based computer is ready for an upgrade to a more powerful edition of Windows Vista.

For more information about how to download and to install the Windows Vista Upgrade Advisor, visit the following Microsoft Web site:

Back to the top

Windows Marketplace Web site

To find additional Windows-compatible programs online, visit the Windows Marketplace Web site. Windows Marketplace is a Web site that contains links to thousands of different software and hardware products that work with Windows, from productivity programs and games to digital cameras and portable media players. For more information about Windows Marketplace, visit the following Microsoft Web site:

Back to the top

Additional information

For more information about how to find Windows-compatible programs, visit the following Microsoft Web site:

Most programs that are written for Windows XP also work in this version of Windows. But some older programs might run poorly or might not run at all. If a program that is written for an earlier version of Windows does not run correctly, use the Program Compatibility Wizard to change the compatibility settings for the program. To change settings for a program manually, use the individual program’s Compatibility tab. For more information about how to use an individual program’s Compatibility tab, visit the following Microsoft Web site:

For more information about Windows Vista Application Compatibility, visit the following Microsoft Web site:

For more information about how to troubleshoot program compatibility, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Note If you still have program-incompatibility problems, you might want to ask someone for help or contact support. For information about how to contact support, visit the following Microsoft Web site:

Back to the top

Microsoft Application Compatibility Toolkit 5.0

The Microsoft Application Compatibility Toolkit (ACT) 5.0 is a life-cycle management tool that assists in identifying and managing your overall application portfolio, reducing the cost and time involved in resolving application compatibility issues, and helping you quickly deploy Windows Vista and Windows Updates.

For more information about how to download and to install the Microsoft Application Compatibility Toolkit 5.0, visit the following Microsoft Web site:

For more information about how to troubleshoot program compatibility, click the following article numbers to view the articles in the Microsoft Knowledge Base:

If you are trying to troubleshoot a software program that is not Windows Vista-compatible, there are troubleshooting resources that are available to you. If you have a software program that is not Windows Vista-compatible, you still may be able to get it to run on Windows Vista by using the individual program’s Compatibility tab.

Back to the top

Back to the top

You can configure the PstDisableGrow registry entry to prevent Microsoft Office Outlook 2007 from creating new items in a .pst file. To do this, follow these steps:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate and then click the following registry subkey: HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook PST
3.	On the Edit menu, point to New, and then click DWORD Value.
4.	Type PstDisableGrow, and then press ENTER.
5.	Right-click PstDisableGrow, and then click Modify.
6.	In the Value data box, type 1, and then click OK.
7.	Exit Registry Editor.

After you complete this procedure, you may want to use MAPI applications to create new items in a .pst file when the PstDisableGrow registry entry is configured. To do this, apply the 953925 hotfix package .

• Home users:
  http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx (http://www.microsoft.com/protect/computer/updates/bulletins/200811.mspx)

  Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now:

  http://update.microsoft.com/microsoftupdate (http://update.microsoft.com/microsoftupdate/)
• IT professionals:
  http://www.microsoft.com/technet/security/bulletin/MS08-068.mspx (http://www.microsoft.com/technet/security/bulletin/MS08-068.mspx)

Back to the top

How to obtain help and support for this security update

For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for support issues with security updates, visit the Microsoft International Support Web site:

North American customers can also obtain instant access to unlimited no-charge e-mail support or to unlimited individual chat support by visiting the following Microsoft Web site:

For enterprise customers, support for security updates is available through your usual support contacts.

Back to the top

Known issues with this security update

Symptoms

After you apply this security update, applications such as Microsoft SQL Server or Internet Information Services (IIS) may fail when they make local NTLM authentication requests.

Cause

This problem occurs because of the way that NT LAN Manager (NTLM) treats different naming conventions as remote entities instead of as local entities. A local authentication failure might occur when the client calculates and caches the correct response to the NTLM challenge that is sent by the server in local lsass memory before the response is sent back to the server. When the server code for NTLM finds the received response in the local lsass cache, the code does not honor the authentication request and treats it as a replay attack. This behavior leads to a local authentication failure.

Resolution

To resolve this problem, you must disable reflection protection so that the affected systems can be authenticated. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

How to disable NTLM reflection protection

ImportantThis section, method, or task contains steps that tell you how to change the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To disable NTLM reflection protection, you must modify a registry key on the client computer. To do this, follow these steps on the client computer:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following subkey in the registry:
   HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Lsa
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type DisableLoopbackCheck for the name of the DWORD, and then press ENTER.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Exit Registry Editor, and then restart the computer.

Note You must restart the computer for this change to take effect.

The effect of disabling NTLM reflection protection

Because the NTLM reflection protection is part of the fix for this SMB vulnerability, disabling NTLM reflection protection on an affected system by setting DisableLoopbackCheck to 1 returns the system to a vulnerable state. Therefore, we strongly recommend that you use the BackConnectionHostNames registry key if needed.

How to re-enable NTLM reflection protection

To re-enable NTLM reflection protection, you must modify a registry entry on the client computer. To do this, follow these steps on the client computer:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following subkey in the registry:
   HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Lsa
3. Right-click DisableLoopbackCheck, and then click Modify.
4. In the Value data box, type 0, and then click OK.
5. Exit Registry Editor, and then restart the computer.

Note You must restart the computer for this change to take effect.

How to disable NTLM reflection protection for a particular SPN

You can disable NTLM reflection protection for a particular Service Principal Name (SPN) that is causing the corresponding authentication to break.To do this, follow these steps on the client computer:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following subkey in the registry:
   HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Lsa MSV1_0
3. On the Edit menu, point to New, and then click Multi-String Value.
4. Type BackConnectionHostNames for the name of the Multi-String Value, and then press ENTER.

   Note If the BackConnectionHostNames registry entry exists as a REG_DWORD, you must delete the BackConnectionHostNames registry entry.

5. Right-click BackConnectionHostNames, and then click Modify.
6. In the Value data box, type the CNAME or the DNS alias that is used for the local shares on the computer, and then click OK.

   Note You must type each host name on a separate line.

7. Exit Registry Editor, and then restart the computer.

Note You must restart the computer for this change to take effect.

The effect of disabling NTLM reflection protection for a particular SPN

Because NTLM reflection protection is part of the fix for this SMB vulnerability, disabling NTLM reflection protection on an affected system will return the system to a vulnerable state for the particular SPN for which the reflection protection was disabled.

How to re-enable NTLM reflection protection for a particular SPN

To do this, follow these steps on the client computer:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following subkey in the registry:
   HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Lsa MSV1_0
3. Right-click BackConnectionHostNames, and then click Modify.
4. In the Value data box, delete the CNAME or the DNS alias that is used for the local shares on the computer, and then click OK.

   Note You must type each host name on a separate line.

5. Exit Registry Editor, and then restart the computer.

Note You must restart the computer for this change to take effect.

Back to the top

File information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.

For all supported editions of Microsoft Windows 2000 Service Pack 4

Windows XP and Windows Server 2003 file information notes

• The files that apply to a specific milestone (RTM, SPn) and service branch (QFE, GDR) are noted in the SP requirement and Service branch columns.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
• In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that has a Microsoft digital signature.

For all supported x86-based versions of Windows XP

For all supported x64-based versions of Windows Server 2003 and of Windows XP Professional x64 edition

For all supported x86-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000. xxxxxx version number.
• GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) have a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

Back to the top

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista