Microsoft has released security bulletin MS08-069. To view the complete security bulletin, visit one of the following Microsoft Web sites:

• 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-069.mspx (http://www.microsoft.com/technet/security/bulletin/MS08-069.mspx)

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.

Additional information about this security update

• If you have multiple versions of Microsoft XML Core Services (MSXML) installed, you may have to apply multiple packages for this security update. Additionally, if you install a version of MSXML after you apply this security update, you may have to apply an additional package for this security update.For more information about the different MSXML versions that are available or that are included with various Microsoft products or software updates, click the following article number to view the article in the Microsoft Knowledge Base:
  269238  (/Feedback.aspx?kbNumber=269238/ ) List of Microsoft XML Parser (MSXML) versions
• Security update package 954459 for MSXML 6.0 is a complete installation package. You can use this package to install MSXML 6.0 on a computer that has no earlier versions of MSXML 6.0 installed. You can also use this package to update an existing installation of MSXML 6.0.
• Windows Update, Microsoft Update, and Microsoft Systems Management Server (SMS) 2003 Inventory Tool for Microsoft Updates offer security update package 954459 only if an earlier version of MSXML 6.0 is already installed on the computer.
• This security update is installed in the %SystemRoot% SYSTEM32 folder.
• When you remove security update 954459 for MSXML 6.0, MSXML 6.0 is completely removed from the computer.
• To apply this security update in quiet mode together with verbose logging and without restarting the computer, use a command-line command that resembles the following:
  • For x86-based computers:
    msxml6-KB954459-enu-x86.exe/q REBOOT=ReallySuppress/l*v c: KB954459.log
  • For IA-64-based computers:
    msxml6-KB954459-enu-ia64.exe/q REBOOT=ReallySuppress/l*v c: KB954459.log
  • For AMD64-based computers:
    msxml6-KB954459-enu-amd64.exe/q REBOOT=ReallySuppress/l*v c: KB954459.log

  A detailed log of the installation process will be located in the file that you specify in the command. In this example, the file is C: KB954459.log.

For more information about the latest service pack for Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base:

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 versions of Windows 2000

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 is signed with 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 original 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) are signed with 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

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

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

This article describes the 2007 Microsoft Office system issues that are fixed in the hotfix package that is dated August 26, 2008.

•	The issues that the hotfix package fixes.
•	The prerequisites for installing the hotfix package.
•	Whether you must restart the computer after you install the hotfix package.
•	Whether the hotfix package is replaced by any other hotfix packages.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

Back to the top

Issues that this hotfix package fixes

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

•	In Microsoft Office PowerPoint 2007, you save a presentation (.pptx) file that contains a radial or path gradient-filled shape as a PDF file. Then, when you open the PDF file, you find that the shape is not gradient filled. Note This problem may occur when a shadow is applied to the shape.
•	Consider the following scenario: • In a PowerPoint 2007 presentation, you insert two same-line Callout shapes. • You change the arrow settings of the line style for a Line Callout shape to the nondefault arrow settings. • You do not make any changes to the arrow settings for another line callout shape. • You save the presentation in the PowerPoint 97-2003 Presentation (.ppt) format. In this case, when you open the .ppt file in PowerPoint 2007 or in PowerPoint 2003, only the Callout shape that has the default arrow settings is displayed. The Callout shape that has nondefault arrow settings is not displayed.
•	Consider the following scenario: 1. In an instance of PowerPoint 2007, you create a new presentation (.pptx), and you add a drawing object in a slide. 2. In another instance of PowerPoint 2007, you open a PowerPoint 2003 presentation (.ppt) in which you have set the default formatting for drawing objects. 3. You copy and paste the slide that you created in step 1 to the PowerPoint 2003 presentation that you opened in step 2. In this scenario, you find that the drawing object that you add to the slide in step 1 uses the default formatting that was set in the PowerPoint 2003 presentation.
•	You create a chart in a Microsoft Office Excel 2007 workbook. Then, you copy and paste the chart to a slide in PowerPoint 2007. In this case, a new Excel 2007 instance starts unexpectedly.
•	In an Excel 2007 workbook, you insert a chart and then change the font color for legend entries. Then, you save the changes to the workbook. When you reopen the workbook in Excel 2007, the font color for the legend entries is reverted unexpectedly to the original color.
•	In an Excel 2007 workbook, you insert a chart, and you make the trendline and the equation that is displayed on the chart. When you copy and paste the chart into a Word document or into a PowerPoint presentation, the equation may be displayed incorrectly on the chart. Additionally, when you save and reopen the Excel 2007 workbook that contains the chart, you may find that the equation is also displayed incorrectly.

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 does not replace any other hotfixes.

Registry information

You do not have to make any changes to the registry to apply this hotfix.

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-kb956058-fullfile-x86-glb.exe	12.0.6327.5000	17,307,968	21-Aug-2008	05:10	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Oart.msp	Not Applicable	16,296,448	20-Aug-2008	15:03	Not Applicable
Oartconv.msp	Not Applicable	8,827,904	20-Aug-2008	15:03	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:

Contents of the Oart.msp file

File name	File version	File size	Date	Time	Platform
Oart.dll	12.0.6327.5000	14,187,032	19-Aug-2008	16:47	x86

Contents of the Oartconv.msp file

File name	File version	File size	Date	Time	Platform
Oartconv.dll	12.0.6327.5000	8,453,672	19-Aug-2008	16:47	x86

Additional notes

•	For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
•	For more information, click the following article number to view the article in the Microsoft Knowledge Base: 824684 (/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top

This article describes the 2007 Microsoft Office system issue that is fixed in the hotfix package that is dated December 16, 2008.

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issue that this hotfix package fixes

This hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:

After you upgrade from Microsoft Office 2003 to the 2007 Microsoft Office system, you may receive the following error message when you double-click an .xml file:

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

There are no prerequisites for installing 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 a previously released 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 issue that is listed in this article.The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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

Microsoft Windows Installer .msp file information

Xmleditverb.msp information

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

As part of an ongoing commitment to provide detection tools and deployment recommendations for security updates, Microsoft is delivering this detection and deployment guidance for all updates that are released during a Microsoft Security Response Center (MSRC) release cycle.

This guidance contains recommendations that are based on the kinds of scenarios that may exist in various Microsoft operating system environments. This guidance includes how to use tools such as the following tools:

•	Windows Update
•	Microsoft Update
•	Office Update
•	The Microsoft Baseline Security Analyzer (MBSA)
•	Windows Server Update Services (WSUS)
•	Microsoft System Center Configuration Manager
•	Microsoft Systems Management Server (SMS)
•	The Extended Security Update Inventory Tool

This article describes the detection and deployment guidance for the security release that is dated August 12, 2008.

Back to the top

Detection and deployment

Environments that detect and deploy security updates by using Windows Update, Microsoft Update, Office Update, and Mactopia

Security updates that were released on August 12, 2008 are available through the following Web sites. Any exceptions are described in each Web site section. The products that are supported by each Web site are also listed.

NoteNot every update is available on every Web site that is listed here.

Windows Update

The products that are supported by this Web site are as follows:

•	Microsoft Windows 2000
•	Windows XP
•	Windows Server 2003
•	Windows Vista
•	Windows Server 2008

Microsoft Update

The products that are supported by this Web site are as follows:

•	Microsoft Internet Security and Acceleration Server 2004
•	Microsoft Internet Security and Acceleration Server 2006
•	Microsoft Exchange 2000 Server
•	Microsoft Exchange Server 2003
•	Microsoft Exchange Server 2007
•	Microsoft Office 2002
•	Microsoft Office 2003
•	The 2007 Microsoft Office system
•	Windows 2000
•	Windows XP
•	Windows Server 2003
•	Windows Vista
•	Windows Server 2008
•	Microsoft SQL Server 2005
•	Microsoft Forefront Client Security
•	Microsoft Visual Studio 2005

General exceptions

•	Microsoft Update does not support SQL 7.0 or Microsoft Date Engine (MSDE) 1.0.
•	Microsoft Update does not support Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.
•	Microsoft Update does not support MSN Messenger or Windows Live Messenger.

Specific exceptions

•

955702 (MS08-050) – Microsoft Update only supports Windows Messenger 4.7 on Windows XP Service Pack 2 (SP2) and on Windows XP Service Pack 3 (SP3). No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

Office Update

The products that are supported by this Web site are as follows:

•	Office 2000
•	Office 2002
•	Office 2003
•	The 2007 Office system

General exceptions

•	Office Update does not support 2007 Office components when they are installed on computers that are running Windows Vista or Windows Server 2008. You must use Microsoft Update instead.
•	Office Update does not support any Macintosh products.

Mactopia

The products that are supported by this Web site are as follows:

•	Microsoft Office 2001 for Mac
•	Microsoft Office 2004 for Mac
•	Microsoft Office X for Mac
•	Microsoft Office 2008 for Mac

Environments that detect security updates by using Microsoft Baseline Security Analyzer (MBSA) version 2.1

You can detect security updates that were released on August 12, 2008 if you use MBSA version 2.1.

NoteMBSA version 2.1 is now released and fully supports security and vulnerability assessment scans on Windows Vista and on Windows Server 2008.

General exceptions

•	MBSA version 2.1 does not support SQL 7.0 or MSDE 1.0.
•	MBSA version 2.1 does not support any Office 2000 components.
•	MBSA version 2.1 does not support any Macintosh products.
•	MBSA version 2.1 does not support Microsoft Works 8 when using an offline scan. For more information, see the Offline and Online scans section, later in this section.
•	MBSA version 2.1 does not support MSN Messenger or Windows Live Messenger.
•	MBSA version 1.2.1 and 2.0.1 are no longer supported.

Specific exceptions

•	955702 (MS08-050) – MBSA only supports Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.
•	924090 (MS08-044) – MBSA only supports detection of Microsoft Works when doing an online scan. For more information, see the Offline and Online scans section, later in this section.

Offline and Online scans

•	Online scan This is when the system that is scanned by MBSA 2.1 has connectivity to Microsoft Update. This is shown in the completed scan report.
•	Offline scan This is when the system that is scanned by MBSA 2.1 is managed by WSUS or in an offline secure environment that forces the system to use the WSUSSCN2.CAB offline catalog.

Environments that detect and deploy security updates by using Windows Server Update Services (WSUS)

You can detect and deploy security updates that were released on August 12, 2008 if you use any of the following items:

•	WSUS 2.0 Service Pack 1 (SP1)
•	WSUS 3.0
•	WSUS 3.0 SP1

General exceptions

•	WSUS does not support SQL 7.0 or MSDE 1.0.
•	WSUS does not support Microsoft Works 8.
•	SUS 1.0 SP1 is no longer supported. It will not receive security updates.

Specific exceptions

•

955702 (MS08-050) – WSUS only supports Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

Environments that detect and deploy security updates by using SMS 2.0, SMS 2003, or SCCM 2007

You can detect and deploy all security updates that were released on August 12, 2008 if you use any of the following items:

•	Systems Management Server (SMS) 2.0 together with the SUS Feature Pack
•	Systems Management Server (SMS) 2003 together with the SUS Feature Pack
•	Systems Management Server (SMS) 2003 together with Inventory Tool for Microsoft Updates (ITMU)
•	System Center Configuration Manager (SCCM) 2007

General exceptions

•	Microsoft Systems Management Server 2003 SP3 includes support for, and is required for, Windows Vista and Windows Server 2008 manageability.
•	SMS 2003 together with ITMU and SCCM 2007 do not support the following products: • SQL 7.0 • MSDE 1.0 • Microsoft Works 8
•	SMS together with the SUS Feature Pack do not support the following products: • MSDE 1.0 • SQL 2005 • SQL 2008 • Exchange 2007 • Microsoft Works 8 • The 2007 Office system • Windows Internet Explorer 7 • Windows Vista • Windows Server 2008 • Any x64-based versions of Windows or of SQL • Any Itanium-based versions of Windows or of SQL
•	The SMS SUS Feature Pack, SMS ITMU, and SCCM do not support any Macintosh products.

Specific exceptions

•

955702 (MS08-050) – SMS SUSFP, SMS ITMU, and SCCM 2007 only support Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

NoteThe SMS SUS Feature Pack requires the Extended Security Update Inventory Tool to detect all the security updates.

To obtain the Extended Security Update Inventory Tool, visit the following Microsoft Web site:

Summary of detection and deployment guidance

The following table summarizes the detection and deployment guidance for each new security update.

NoteTo simplify this table, items that were listed under the general exceptions heading for each detection and deployment technology are not included.

For example, the SMS SUS Feature Pack column in this table may include a Yes. However, the security bulletin lists a Windows Vista component as affected. Previously, we would have stated in the table that the SMS SUS Feature Pack partly supported the deployment of the security update because the SMS SUS Feature Pack does not support Windows Vista components. Currently, we no longer account for that specific exception in the table because the exception is always listed as a general exception.

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.1	WSUS 2.0 and WSUS 3.0	SMS SUS Feature Pack	SMS Inventory Tool for Microsoft Updates	System Center Configuration Manager 2007
			Detect and deploy	Detect and deploy	Detect and deploy	Detect only	Detect and deploy	Detect and deploy	Detect and deploy	Detect and deploy
955617	MS08-041	Access	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
955048	MS08-042	Word	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
954066	MS08-043	Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
924090	MS08-044	Office Filters	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
953838	MS08-045	Internet Explorer	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
952954	MS08-046	Windows ICM	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
953733	MS08-047	IPsec	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
951066	MS08-048	Outlook Express/Windows Mail	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
950974	MS08-049	Event System	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
955702	MS08-050	Windows Messenger	Not applicable	Partly, see the Windows Update section	Partly, see the Microsoft Update section	Partly, see the MBSA section	Partly, see the WSUS section	Partly, see the SMS section	Partly, see the SMS Update section	Partly, see the SCCM section
949785	MS08-051	PowerPoint	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes

Rereleased security updates

There are no rereleases this month.

Back to the top

Frequently asked questions

What is Microsoft doing to provide guidance about how to deploy these updates?

We encourage system administrators to join the monthly technical Webcast to learn more about security updates. The Webcast for this security update airs on August 13, 2008 at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

What other information should I know about MBSA?

For more information about the programs that MBSA currently supports, visit the following Microsoft TechNet Web site:

Can I use SMS or System Center Configuration Manager to determine whether the updates are required?

Yes. SMS helps detect and deploy these security updates. SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with SUSFP use MBSA version 1.2.1 technology for detection. Therefore, SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack have limitations that resemble the limitations of MBSA version 1.2.1.

For more information about SMS, visit the following Microsoft Web site:

The SUS Feature Pack together with the Extended Security Update Inventory Tool is required to detect all the security updates on Microsoft Windows and on other affected Microsoft products.

For more information about the limitations of the SUS Feature Pack, click the following article number to view the article in the Microsoft Knowledge Base:

SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack also use the Microsoft Office Inventory Tool to detect the required security updates for Microsoft Office programs such as Microsoft Word.

SMS 2003 customers can also use ITMU to detect and deploy security updates. ITMU uses technology from Microsoft Updates. For more information about ITMU, visit the following Microsoft Web site:

System Center Configuration Manager 2007 uses WSUS 3.0 for detection and deployment of these security updates. Therefore, anything that is supported by WSUS 3.0 is also supported by System Center Configuration Manager 2007.

Back to the top

According to RFC 2045, MIME e-mail clients that do not have S/MIME capability can read clear signed messages. However, for Microsoft Exchange Server 2007 users, MIME e-mail clients cannot read the body of clear signed messages in Microsoft Office Outlook Web Access if the S/MIME control is not installed. The body of the e-mail message is blank.

This problem affects both Microsoft Office Outlook Web Access Premium and Microsoft Office Outlook Web Access Light. Windows Internet Explorer 7 and later versions of Internet Explorer are the only versions of Internet Explorer that support the S/MIME control.

Note This problem occurs only if the following conditions are true:

•	The e-mail messages are sent within a Microsoft Exchange Server organization.
•	The e-mail messages are sent from Microsoft Exchange 2000 Server or from Microsoft Exchange Server 2003 to Exchange Server 2007.
•	The e-mail messages are in an Exchange Server 2007 mailbox.

Back to the top

To work around this problem, use Microsoft Outlook or another e-mail client that supports S/MIME.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

When messages are sent in Microsoft Transport Neutral Encapsulation Format (MS-TNEF) format from Exchange 2000 Server or from Exchange Server 2003 to Exchange Server 2007, certain properties are not converted. The Outlook Web Access client has to have these properties to display the body of the e-mail message.

If you forward the e-mail message in Outlook or if you perform any other operation that promotes the clear signed content to the relevant MAPI properties of the clear signed message, the body of the e-mail message is visible in Outlook Web Access.

For more information about clear signed messages, visit the following Web sites:

For more information about S/MIME, visit the following Web site:

Back to the top

This article describes the Microsoft Office Word 2007 issues that are fixed in the hotfix package that is dated February 15, 2008.

•	The issues that the hotfix package fixes.
•	The prerequisites for installing the hotfix package.
•	Whether you must restart the computer after you install the hotfix package.
•	Whether the hotfix package is replaced by any other hotfix packages.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

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:

•	Consider the following scenario: • On an Office SharePoint site, you set a document library’s document template type to Microsoft Office Word 97-2003 document (.doc). • On a client computer that is running Office Word 2007, you create a new document from the document library. In this case, when you try to save the document in Office Word 2007, the default document type that appears in the Save as type box of the Save As dialog box is Word Document (*.docx). Additionally, if you do not notice that Word Document (*.docx) is wrong document type for the document library on the SharePoint site, and then click Save in the Save As dialog box, a dialog box states that states that you are saving the document in the wrong document type . If you click Cancel in this dialog box, you notice that the Save As dialog box reappears. However, the file name is changes to some random numbers together with .tmp file name extension. For example, the file name may appear as 6AF9E345.tmp.docx.
•	In Office Word 2007, you add a XML schema to the schema library. Then, when you open or close a document that has the XML schema applied, you may notice that a memory leak occurs in Performance Monitor.
•	In Office Word 2007, you insert an object that is from an Internet address. After that, when you try to change the source of the linked object to another Internet address, you receive the following error message: You cannot use an Internet address here. Enter a path that points to a location on your computer or on the network.
•	Office Word 2007 stops responding when you try to open WordPerfect 5.1 files.
•	You embed a Word document object in a 2007 Microsoft Office file. However, you cannot save a copy of the Word document object to a network location in the Word 2007 format (.docx).

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 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

To apply this hotfix package, you must have Word 2007 installed.

Restart information

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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-kb941468-fullfile-x86-glb.exe	12.0.6300.5000	15,670,968	28-Jan-2008	17:55	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,064,704	28-Jan-2008	18:15	Not Applicable
Wordconv.msp	Not Applicable	6,239,232	28-Jan-2008	18:15	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:

Contents of the Word.msp file

File name	File version	File size	Date	Time	Platform
Winword.exe	12.0.6300.5000	349,720	12-Dec-2007	15:54	x86
Wwlib.dll	12.0.6300.5000	17,485,848	12-Dec-2007	15:54	x86

Contents of the Wordconv.msp file

File name	File version	File size	Date	Time	Platform
Wrd12cnv.dll	12.0.6300.5000	4,272,664	12-Dec-2007	17:08	x86
Wrd12exe.exe	12.0.6300.5000	24,584	12-Dec-2007	17:08	x86

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

Back to the top

After a resource updates a task in Project Web Access and submits the update, the task update is submitted to a project manager other than the designated status manager.

To resolve this issue, apply hotfix 956060. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Consider the following scenario. You mount a Virtual Machine hard disk file (.vhd file) as a loopback device in Windows Server 2008. The .vhd file is now available as a virtual hard disk. In this scenario, users may access the virtual machine, and they can read from or write to the virtual hard disk.

Back to the top

This issue occurs if you mount a .vhd file as loopback device by using the Hyper-V Windows Management Instrumentation (WMI) APIs.

Back to the top

To enforce the security of the contents of a .vhd file that is mounted as a loopback device, use one of the following methods:

•	Configure NTFS file system permissions on files and folders in the mounted .vhd file.
•	Use a separate server to which virtual machine users do not have access.

Back to the top

For more information about Hyper-V, visit the following Microsoft Web site:

Back to the top

On a Windows Vista-based computer or on a Windows Server 2008-based client computer, you create a shortcut to a DFS link in the Favorite Links folder (%Userprofile% Links). However, when you try to click the shortcut in Windows Explorer, the contents of the DFS share do not appear.

Note This problem does not occur if the shortcut points to a DFS root folder or if the shortcut uses the UNC path for the target share.

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

To apply this hotfix, the computer must run one of the following:

•	Windows Vista
•	Windows Vista Service Pack 1
•	Windows Server 2008

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

•	The files that apply to a specific product milestone (RTM, SPn) can be identified by examining the file version numbers as shown in the following table: Version Product Milestone Service branch 6.0.6000 .20xxx Windows RTM LDR 6.0.6001.22xxx Windows Vista SP1 and Windows Server 2008 SP1 SP1 LDR
•	Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
•	The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important to maintaining the state of the updated component. The security catalog files, for which attributes not listed, are signed with a Microsoft digital signature.

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

File name	File version	File size	Date	Time	Platform
Shell32-ppdlic.xrm-ms	Not Applicable	3,150	25-Jul-2008	02:48	Not Applicable
Shell32.dll	6.0.6000.20882	11,320,320	25-Jul-2008	03:13	x86
Shell32.dll	6.0.6001.22229	11,581,952	25-Jul-2008	03:22	x86

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

File name	File version	File size	Date	Time	Platform
Shell32-ppdlic.xrm-ms	Not Applicable	3,150	25-Jul-2008	03:01	Not Applicable
Shell32.dll	6.0.6000.20882	12,788,736	25-Jul-2008	03:24	x64
Shell32.dll	6.0.6001.22229	12,899,328	25-Jul-2008	03:53	x64
Shell32.dll	6.0.6000.20882	11,320,320	25-Jul-2008	03:13	x86
Shell32.dll	6.0.6001.22229	11,581,952	25-Jul-2008	03:22	x86

Additional file information for Windows Server 2008 and Windows Vista

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

File name	Package_for_kb953537_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	19,139
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,367
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_client~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,715
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,421
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_sc~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,424
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,425
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_server~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,432
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,422
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,431
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	19,020
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,425
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_0c8d50707aa16033b3a64bd0220e5bf9_31bf3856ad364e35_6.0.6000.20882_none_cb304f2db0940c2d.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_11f01c3c0091e5d8d47f19e365b71f2a_31bf3856ad364e35_6.0.6000.20882_none_aa6561f3261feaa4.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_195c7f5f144e141af4e2293ffacd3b69_31bf3856ad364e35_6.0.6000.20882_none_fedd5434fd72c0c7.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_1a39b2269eec529c646151b3a4e874ec_31bf3856ad364e35_6.0.6000.20882_none_30709238f68c823d.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_24b6c295fbf637309c77e5b993c8df99_31bf3856ad364e35_6.0.6000.20882_none_d87b7d6122dbe2eb.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_280b405f3c1666dd258d69fbda8670d0_31bf3856ad364e35_6.0.6000.20882_none_518fd1521a3c627b.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_36c049e76ff263209fb3052ba4b9e7e8_31bf3856ad364e35_6.0.6000.20882_none_58bacf2d641e2ba1.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_38bbd75ee49d829d79ad5c4be14b0c23_31bf3856ad364e35_6.0.6000.20882_none_3928ba639cbd9a23.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_3f0f1d20e1db0484fce01e9a7a575e1c_31bf3856ad364e35_6.0.6000.20882_none_41e882f2ae8151c9.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_4505df0c3b76b17302b4bb0713e092b0_31bf3856ad364e35_6.0.6000.20882_none_43ce13c59f05fe8a.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_458acf96413aab1ad51d38337fbe6895_31bf3856ad364e35_6.0.6000.20882_none_e0a9a825a94e72fa.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_465bd0635faebe77e75c24978b267a59_31bf3856ad364e35_6.0.6000.20882_none_29c2c8087d493461.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_46853169a8455c91c71ffa0ee118e9e7_31bf3856ad364e35_6.0.6000.20882_none_c07b87a202cd1c7b.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_46f8c85ec82ceb603ffd886951f82a26_31bf3856ad364e35_6.0.6000.20882_none_1c0a54a24a97780a.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_489e1c68b765054efa21f22c3866dfd2_31bf3856ad364e35_6.0.6000.20882_none_c6713d7146e491fd.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_4cb8c73d564be7256f299ed37e66bee1_31bf3856ad364e35_6.0.6000.20882_none_14459f61c8704864.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_5aa9fe1ea5a40010e1571af571dd363c_31bf3856ad364e35_6.0.6000.20882_none_a247bf4310cda742.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_5acb3f49c956fb58b8ded84508425f48_31bf3856ad364e35_6.0.6000.20882_none_51de1d5d7ae6614b.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_6d71edc617d70dcb8747abb83be7e8cb_31bf3856ad364e35_6.0.6000.20882_none_25d3b9b7d3407deb.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_7682c3d1a0f2612e4dee3b44ec336a1b_31bf3856ad364e35_6.0.6001.22229_none_7ce88f51f54a97d1.manifest
File version	Not Applicable
File size	695
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_80e2335f26e51c085b99e5c2bc094a8a_31bf3856ad364e35_6.0.6000.20882_none_c731e3a7227bfc49.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_841f12beeeedf3823a682b313bed31ce_31bf3856ad364e35_6.0.6000.20882_none_c095bcd79dd0ac6c.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_8bbbeaca73e36a2418fadd0aa4475efe_31bf3856ad364e35_6.0.6000.20882_none_1ef756416ffc4254.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_8f8f6126ffadf3d771cad901eadf6ed2_31bf3856ad364e35_6.0.6000.20882_none_2c4988dc479089be.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_9458692ec5e23304c8d7bf1b179abace_31bf3856ad364e35_6.0.6000.20882_none_015507f62b7122ce.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_984f22c59a2e66f9d66ffbd9e02fba50_31bf3856ad364e35_6.0.6000.20882_none_3eaacec034d259dc.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_9e7ac22538a08fc505eee8c6dda2c160_31bf3856ad364e35_6.0.6000.20882_none_e9b5f1c9d8377d99.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_ba27e2bfe24d68beaf30898686e0204c_31bf3856ad364e35_6.0.6000.20882_none_938aa1490a163cdf.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_c7e8a8b6bd4afe992ba65f286c6fdb9b_31bf3856ad364e35_6.0.6000.20882_none_a82d31f25829f819.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_db8698b0da6fab8f0e2fc21744ee68a2_31bf3856ad364e35_6.0.6000.20882_none_cc05d2cf587dfd23.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_df5fee1cbb6a1f34f60333eb286815ee_31bf3856ad364e35_6.0.6000.20882_none_f4e53123a96c99e9.manifest
File version	Not Applicable
File size	708
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_e5abc8d436d5cb289344e9abdf4218d5_31bf3856ad364e35_6.0.6000.20882_none_bb999b5a6ffa7741.manifest
File version	Not Applicable
File size	695
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_eabcba71355f842bd4fe29642f7d7f1f_31bf3856ad364e35_6.0.6000.20882_none_740b0ed446aef107.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_eb9c61ba7edf25ac10f70187dc7647b6_31bf3856ad364e35_6.0.6000.20882_none_6d67eabe44d48fe2.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_ecf63702ff1aeb6776ad71a4e3b31325_31bf3856ad364e35_6.0.6000.20882_none_4bc5d32a58aa87a8.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_f61a979035e70cd23b362e4a92232f34_31bf3856ad364e35_6.0.6000.20882_none_ce8ffe572fe63934.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_f8f2f452a4c6078c9fc2f4136047d660_31bf3856ad364e35_6.0.6000.20882_none_d31d6d13b1c2d2ed.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_fd33c635b678d128c4a7e94e877066cf_31bf3856ad364e35_6.0.6000.20882_none_4937468c2f3823c7.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08

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

File name	Amd64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20882_none_c696a7a0e68f7d2b.manifest
File version	Not Applicable
File size	905,287
Date (UTC)	25-Jul-2008
Time (UTC)	03:38
File name	Amd64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6001.22229_none_c8c4c7d4e37f17d7.manifest
File version	Not Applicable
File size	906,231
Date (UTC)	25-Jul-2008
Time (UTC)	04:41
File name	Package_for_kb953537_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	19,570
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,375
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_client~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,725
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,429
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,432
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,433
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_server~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,440
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,430
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,439
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpe_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	19,453
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpe~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,433
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20882_none_d0eb51f31af03f26.manifest
File version	Not Applicable
File size	896,876
Date (UTC)	25-Jul-2008
Time (UTC)	03:22
File name	Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6001.22229_none_d319722717dfd9d2.manifest
File version	Not Applicable
File size	899,202
Date (UTC)	25-Jul-2008
Time (UTC)	03:34

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

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

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

Back to the top

On a Windows Vista-based or Windows Server 2008-based computer, you have a Serial Advanced Technology Attachment (SATA) device that supports the Native Command Queuing (NCQ) feature. However, you may experience poor performance when you access the SATA device.

This problem occurs if the computer uses the Microsoft AHCI driver (Msahci.sys). The SATA device supports queue depths of greater than 1 and less than 32. However, the Microsoft AHCI driver incorrectly sets the queue depth on the SATA device. In this case, NCQ is disabled for the SATA device.

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 on a 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 must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 (.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 32-bit versions of Windows Server 2008 and of Windows Vista

For all supported 64-bit versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

For more information about NCQ, visit the following Web site:

For more information about SSD, visit the following Web site:

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista

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