Back to the top

Known issues

Back to the top

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Back to the top

Back to the top

Back to the top

Detection and deployment

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

Security updates that were released on May 8, 2007 are available through the following Web sites. Any exceptions are in the following list. The products that are supported by each Web site are also listed.

•	Microsoft Windows Update http://update.microsoft.com/windowsupdate (http://update.microsoft.com/windowsupdate) • Windows 2000, Windows XP, Windows Server 2003
•	Microsoft Update http://update.microsoft.com/microsoftupdate (http://update.microsoft.com/microsoftupdate) • Windows 2000, Windows XP, and Windows Server 2003 • Microsoft Office XP and Office 2003 • Microsoft Exchange 2000 and Exchange 2003 • Internet Security and Acceleration Server 2004 • Microsoft SQL Server 2005 • Security update 934233 (security bulletin MS07-023) Microsoft Update does not support the Excel 2000 part of this security update. • Security update 934232 (security bulletin MS07-024) Microsoft Update does not support the Word 2000 part of this security update. • Security update 934873 (security bulletin MS07-025) Microsoft Update does not support the Office 2000 part of this security update.
•	Office Update http://officeupdate.microsoft.com (http://officeupdate.microsoft.com) • Office 2000, Office XP, and Office 2003
•	Mactopia http://www.microsoft.com/mac (http://www.microsoft.com/mac) • Office 2001 for Mac • Office X for Mac • Office 2004 for Mac

Note Not every update is available on every Web site that is listed.

Environments that detect security updates by using MBSA version 1.2.1 or MBSA version 2.0.1

Microsoft Baseline Security Analyzer (MBSA) version 1.2.1 contains an integrated version of the Office Detection Tool (ODT). If you use MBSA 1.2.1 or MBSA version 2.0.1 to detect security updates, you can detect all the security updates that were released on May 8, 2007. Any exceptions are in the following list.

Note The ODT part of MBSA 1.2.1 is limited to local scans only.

Note MBSA 1.2.1 does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

Note MBSA 2.0.1 is not supported on Windows Vista. However, MBSA 2.0.1 supports remote scans of computers that are running Windows Vista. 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:

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

If you use SUS, WSUS 2.0, or WSUS 3.0 to detect and to deploy security updates, you can detect most security updates that were released on May 8, 2007. Any exceptions are in the following list.
Note SUS 1.0 SP1 does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

•	Security update 934233 (security bulletin MS07-023) SUS does not support any part of this security update. WSUS does not support the Excel 2000 part of this security update.
•	Security update 934232 (security bulletin MS07-024) SUS does not support any part of this security update. WSUS does not support the Word 2000 part of this security update.
•	Security update 934873 (security bulletin MS07-025) SUS does not support any part of this security update. WSUS does not support the Office 2000 part of this security update.
•	Security update 931906 (security bulletin MS07-028) SUS does not support any part of this security update.

Environments that detect and that deploy security updates by using SMS 2.0 together with the Security Update Inventory Tool (SUIT) or SMS 2003 together with the Inventory Tool for Microsoft Updates (ITMU)

If you use Microsoft Systems Management Server (SMS) 2.0 together with SUIT, SMS 2003 together with SUIT, or SMS 2003 together with ITMU to detect and to deploy security updates, you can detect and deploy all security updates that were released on May 8, 2007. Any exceptions are in the following list.
Note SMS together with SUIT does not support Windows Vista, any Windows x64 editions, or Windows Itanium-based systems.

•	Security update 934233 (security bulletin MS07-023) SMS ITMU does not support the Excel 2000 part of this security update.
•	Security update 934232 (security bulletin MS07-024) SMS ITMU does not support the Word 2000 part of this security update.
•	Security update 934873 (security bulletin MS07-025) SMS ITMU does not support the Office 2000 part of this security update.
•	Security update 931832 (security bulletin MS07-026) SMS SUIT does not support the Exchange 2007 part of this security update.
•	Security update 931906 (security bulletin MS07-028) SMS SUIT supports this update when you use the Extended Security Update Inventory Tool (ESUIT).

To obtain ESUIT, visit the following Microsoft Web site:

Back to the top

Summary of detection and deployment guidance

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

Security update

Bulletin

Component

Office Update

Windows Update

Microsoft Update

MBSA 1.2 and the Office Detection Tool

MBSA 2.0.1

SUS

WSUS 2.0 and WSUS 3.0

Enterprise Scan Tool

SMS Security Update Inventory Tool

SMS Inventory Tool for Microsoft Updates

Detect and deploy

Detect and deploy

Detect and deploy

Detect only

Detect only

Detect and deploy

Detect and deploy

Detect only

Detect and deploy

Detect and deploy

934233

MS07-023

Excel

Yes

Not applicable

Partially, see the MU section

Yes

Partially, see the MBSA section

Not applicable

Partially, see the WSUS section

Not applicable

Yes

Partially, see the SMS section

934232

MS07-024

Word

Yes

Not applicable

Partially, see the MU section

Yes

Partially, see the MBSA section

Not applicable

Partially, see the WSUS section

Not applicable

Yes

Partially, see the SMS section

934873

MS07-025

Office

Yes

Not applicable

Partially, see the MU section

Yes

Partially, see the MBSA section

Not applicable

Partially, see the WSUS section

Not applicable

Yes

Partially, see the SMS section

931832

MS07-026

Exchange

Not applicable

Not applicable

Yes

Partially, see the MBSA section

Yes

Not applicable

Yes

Not applicable

Partially, see the SMS section

Yes

931768

MS07-027

Internet Explorer

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

931906

MS07-028

CAPICOM

Not applicable

Not applicable

Yes

No

Yes

Not applicable

Yes

Yes

Yes, with ESUIT

Yes

935966

MS07-029

DNS

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

Back to the top

Rereleased security updates

There are no rereleases this month.

Back to the top

Frequently asked questions

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

A1: Microsoft encourages system administrators to join the monthly technical webcast to learn more about security updates. The webcast for this security update airs on May 9, 2007 at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

Q2: Is the Enterprise Scan Tool (EST) cumulative for SMS like ESUIT is cumulative for SMS?

A2: No, the EST is not cumulative. There are no plans to make the EST cumulative.

Q3: Can I use MBSA to determine whether these updates are required?

A3: Yes, you can use MBSA 1.2.1 and MBSA 2.0.1 to fully detect the need for the following security updates that were released on May 8, 2007, except where noted.

Microsoft Knowledge Base article number	Bulletin ID	Component	Detection note
934233	MS07-023	Excel	See the MBSA section
934232	MS07-024	Word	See the MBSA section
934873	MS07-025	Office	See the MBSA section
931832	MS07-026	Exchange	See the MBSA section
931906	MS07-028	CAPICOM	See the MBSA section

For more information about the programs that MBSA currently does not detect, click the following article numbers to view the articles in the Microsoft Knowledge Base:

You may have installed a program that is listed in the Affected software section of a security bulletin that is mentioned in the related article. In this case, you may have to manually determine whether you must install the required security update.. For more information about MBSA, visit the following Microsoft Web site:

Q4: Which security updates require that I use the EST together with MBSA 1.2.1 to determine which systems on my network are vulnerable?

A4: The following security update requires that you use the EST together with MBSA to determine which systems on the network are vulnerable.

Microsoft Knowledge Base article number	Bulletin ID	Component
931906	MS07-028	CAPICOM

Q5: Can I use SMS to determine whether the updates are required?

A5: Yes, SMS helps detect and deploy these security updates. SMS 2.0 and SMS 2003 together with SUIT use MBSA 1.2.1 technology for detection. Therefore, SMS 2.0 and SMS 2003 together with SUIT have limitations that resemble the limitations of MBSA 1.2.1. For more information about SMS, visit the following Microsoft Web site:

SUIT together with ESUIT are required for detection of all the security updates on Microsoft Windows and on other affected Microsoft products. For more information about the limitations of SUIT, click the following article numbers to view the articles in the Microsoft Knowledge Base:

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

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

Back to the top

After upgrading a Windows Server 2008 Standard system with the Hyper-v role installed to Windows Server 2008 Enterprise Edition or Windows Server 2008 Datacenter edition you may encounter some of the following issues

 

·         Hyper-V does not appear as installed role

·         Hyper-V Manager will not display any configured virtual machines

·         Any previous virtual machine configuration files stored in C: ProgramData Microsoft Windows Hyper-v Virtual Machine are missing

·         Hyper-V Image Management service does not start or is missing

·         Hyper-V Networking Management Service does not start or is missing

·         Hyper-V Virtual Machine Management service does not start or is missing

Back to the top

Hyper-V role is not migrated when upgrading from one version of Windows Server 2008 to another version.

Back to the top

To prevent this issue from occurring, follow these steps:

 

1.       In Hyper-V manager Export all virtual machines.

2.       Using Server Manager remove the Hyper-V role.

3.       Run upgrade. 

 For more information about the update package see the following knowledge base article:

950050      Description of the update for the release version of the Hyper-V technology for Windows Server 2008

/950050 (http://support.microsoft.com/default.aspx?scid=kb;en-us;950050)

4.       Reinstall the Hyper-V update.

5.       In Server Manager add the Hyper-V role.

6.       Import your virtual machines.

 

To resolve this issue after doing an upgrade, follow these steps:

1.       Using Server Manager remove the Hyper-V role.

2.       Reinstall the Hyper-V update.

 For more information about the update package see the following knowledge base article:

950050      Description of the update for the release version of the Hyper-V technology for Windows Server 2008

/950050 (http://support.microsoft.com/default.aspx?scid=kb;en-us;950050)

 

3.       In Server Manager add the Hyper-V role.

4.       Recreate the virtual machines using the existing VHD files.

 

 

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

The iSCSI boot specific Setup code is not cross-platform aware.

When using a NIC-based iSCSI boot solution and cross-platform media, installation will fail in the WinPE phase of Setup.
When using an HBA-based iSCSI boot solution and cross-platform media, failure of the installation may occur after Setup has completed.

Back to the top

You must use the same architecture for WinPE as the target deployment architecture when deploying to an iSCSI boot disk.

For example, if you are installing x64 architecture Windows, you must use x64 architecture WinPE (such as x64 architecture-only installation media).

Cross-platform media, such as cross-platform media available on MSDN, or cross-platform media created using the OEM Preinstallation Kit (OPK), will fail in this iSCSI boot scenario.

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

Back to the top

If these conditions are true, the logon account contains two at signs. For example, you must type sample@bar@domain_name.com to log on to the computer.

During S4U Kerberos authentication, the UPN name is parsed from left to right until the first at sign is found. The at sign acts as a delimiter between the Active Directory directory service logon name and the domain name. When a logon name contains the at sign, only the part of the Active Directory logon name that is to the left of the at sign is used during authentication.

Back to the top

Back to the top

Back to the top

For more information about logon methods and authentication methods for Microsoft Windows XP Professional, visit the following Microsoft Web site:

For more information about how to troubleshoot logon problems in Microsoft Windows 2000 Professional, visit the following Microsoft Web site:

Back to the top

This guidance contains recommendations that are based on the types 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 March 11, 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 March 11, 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.

Note Not 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 Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.

Specific exceptionsMicrosoft Update does not support the part of security update 933103 that involves the following products:

•	Microsoft Visual Studio 2002
•	Microsoft Visual Studio 2003
•	Microsoft BizTalk Server 2000
•	Microsoft BizTalk Server 2002
•	Microsoft Commerce Server 2000
•	Microsoft Internet Security and Acceleration (ISA) Server 2000

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

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

You can detect security updates that were released on March 11, 2008 if you use MBSA version 2.0.1.

General Exceptions

•	MBSA version 2.0.1 does not support any Office 2000 components.
•	MBSA version 2.0.1 does not support any Macintosh products.
•	MBSA version 2.0.1 is not supported on Windows Vista. However, MBSA version 2.0.1 supports remote scans of computers that are running Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 931943 (/Feedback.aspx?kbNumber=931943/)Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista
•	MBSA version 1.2.1 is no longer supported. It will not detect security updates that were released after October 2007.

Specific exceptionsMBSA version 2.0.1 does not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

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 March 11, 2008 if you use any of the following items:

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

General Exceptions

•	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Office 2000 components.
•	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Macintosh products.
•	SUS 1.0 Service Pack 1 (SP1) is no longer supported. It will not receive security updates.

Specific exceptionsWSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

Environments that detect and deploy security updates by using SMS 2.0, SMS 2003, or System Center Configuration Manager 2007

You can detect and deploy all security updates that were released on March 11, 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 2007

General Exceptions

•	SMS ITMU and System Center Configuration Manager do not support any Office 2000 components.
•	SMS together with the SUS Feature Pack does not support the following products: • The 2007 Office system • Windows Internet Explorer 7 • Windows Vista • Windows Server 2008 • Any x64-based versions of Windows • Any Itanium-based versions of Windows
•	The SMS SUS Feature Pack, SMS ITMU, and System Center Configuration Manager do not support any Macintosh products.

Specific exceptionsWSUS 2.0, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

Note The 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.

Note To simplify this table, items that were listed under the General Exceptions heading for each detection and deployment technology are not included.

For example, the Microsoft Update column in this table may include a Yes. However, the security bulletin lists an Office 2000 component as affected. Previously, we would have stated in the table that Microsoft Update partially supported deployment of the security update. However, no Office 2000 components are supported by Microsoft Update. Therefore, we no longer account for that product in the table because it is always listed as a general exception.

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.0.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
949029	MS08-014	Microsoft Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949031	MS08-015	Microsoft Outlook	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949030	MS08-016	Office	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
933103	MS08-017	Microsoft Office Web Components	Partially. See Office Update section.	Not applicable	Partially. See Microsoft Update section.	Partially. See MBSA section.	Partially. See WSUS section.	Yes	Partially. See SMS section.	Partially. See System Center Configuration Manager section.

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 Thursday, March 13, 2008 12: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 does not detect, click the following article number to view the article in the Microsoft Knowledge Base:

If you installed a program that is listed in the Affected software section of a security bulletin, you may have to manually determine whether you must install the required security update. For more information about MBSA, visit the following Microsoft 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 informationabout 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 to 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

When you start a restored Virtual Machine (VM) that was backed up using Volume Shadow Copy Service (VSS) the VM generates the following message:

 

Event ID 6008, The previous system shutdown at time on <date> was unexpected

Back to the top

When the system is restored the Hyper-V VSS writer turns off and deletes the currently running VM. The backup application then places the files (configuration file, snapshot files, VHD files, etc) in the restore locations. Finally, the writer registers the restored configuration with Hyper-V and attaches the necessary VHD files. The writer does not interact with the OS in the VM at all in the entire restore phase.

Back to the top

Due to the Guest OS being backed up while it was in the running state and the VM being restored in the off line state the value in bootstat.dat indicates an unexpected shutdown.

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 Windows Media Player and WindowsMedia Center do not appear in Windows Mixer unless they are running.

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

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

• When you install this security update on a computer that is running Windows Vista or Windows Server 2008, you may have to restart the computer two times to complete the installation. This issue may occur if you install an XML Core Services 4.0–based update together with an update that contains inbox drivers. For example, the following updates contain inbox drivers:
  956697  (/Feedback.aspx?kbNumber=956697/ ) Windows Server 2008 Hyper-V VSS writer is not used during a backup job because of corrupted or invalid virtual machine configuration files
  938371  (/Feedback.aspx?kbNumber=938371/ ) A software update is available for the Windows Vista installation components

  This issue occurs because Microsoft Windows Installer (MSI)-based installations will not continue while inbox drivers are updating. This is because inbox drivers set the impactful transaction flag and the reboot required flag at the servicing stack level for Windows Vista and Windows Server 2008. Therefore, the update for XML Core Services 4.0 will fail during installation if an update that contains an inbox driver is applied first. After the inbox driver has installed, and then the computer is restarted, the installation of security update for XML Core Services 4.0 will succeed. However, an additional restart is required to complete the installation.

  To avoid this issue, install the security update for XML Core Services 4.0 before you install the update that contains inbox drivers.

• This security update may repeatedly appear in the update list on Microsoft Update or on Windows Update if one of the system files is corrupted or if it has not been updated correctly.For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  941729  (/Feedback.aspx?kbNumber=941729/ ) Security updates for Microsoft XML Core Services 4.0 Service Pack 2 may repeatedly appear in the update list on Microsoft Update or on Windows Update
• After you install security update 954430, certain application compatibility issues and reliability issues may occur in Microsoft XML Core Services 4.0 SP2 on a Windows Vista-based computer. To resolve these issues, install the update that is described in Microsoft Knowledge Base article 941833.
  For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
  941833  (/Feedback.aspx?kbNumber=941833/ ) An update is available that improves the compatibility and the reliability of Microsoft XML Core Services 4.0 Service Pack 2 on a Windows Vista-based computer

  An update is available that improves the compatibility and the reliability of Microsoft XML Core Service 4.0 Service Pack 2 on a Windows Vista-based computer

• The following security updates do not support the complete removal of MSXML 4.0:
  • Security update 954430 for Microsoft XML Core Services (MSXML) 4.0
  • Security update 936181 for Microsoft XML Core Services (MSXML) 4.0
  • Security update 936181 for MSXML 4.0 Service Pack 1 (SP1)
  • Security update 936181 for MSXML 4.0 Service Pack 2 (SP2)

  This situation occurs because this version of MSXML is installed in side-by-side mode. To work around this issue, follow these steps:

  1. Remove security update 954430 by using the Add or Remove Programs item in Control Panel.
  2. Delete the Msxml4.dll file from the %SystemRoot% System32 folder.
  3. Repair the previous installation of MSXML 4.0 by using the Add or Remove Programs item in Control Panel.

  The earlier versions of the Msxml4.dll file and of the Msxml4r.dll file are restored to the side-by-side folder and to the %SystemRoot% System32 folder.

• You may receive the following error message when you install security update 954430 from Windows Update:
  Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.

  When this error occurs, you may also notice information that resembles the following in the log file:

  Error 1911. Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.
  MSI (s) (20:18) [17:52:31:612]: Product: MSXML 4.0 SP2 (KB954430) — Error 1911. Could not register type library for file c: Windows system32 msxml4.dll. Contact your support personnel.
  === Logging stopped: 11/10/2006 17:53:07 ===
  MSI (c) (34:20) [17:53:07:252]: Note: 1: 1708
  MSI (c) (34:20) [17:53:07:260]: Product: MSXML 4.0 SP2 (KB954430) — Installation failed.
  MSI (c) (34:20) [17:53:07:267]: Windows Installer installed the product. Product Name: MSXML 4.0 SP2 (KB954430). Product Version: 4.20.9839.0. Product Language: 1033. Installation success or error status: 1603.
  MSI (c) (34:20) [17:53:07:313]: Grabbed execution mutex.
  MSI (c) (34:20) [17:53:07:319]: Cleaning up uninstalled install packages, if any existMSI (c) (34:20) [17:53:07:331]: MainEngineThread is returning 1603
  === Verbose logging stopped: 11/10/2006 17:53:07 ===

  To work around this problem, manually install the security update from the Microsoft Download Center, and then click Ignore when the error message is displayed. To confirm that the installation was successful, verify that the version of the Msxml4.dll file in the %SystemRoot% System32 folder is 4.20.9870.0.

Back to the top

File information

The English (United States) version of this security update 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.

Back to the top

• You use the Microsoft URL Rewrite Module for Internet Information Services (IIS) 7.0 to rewrite a URL and to run a child request.
• You use a relative reference in image paths, in a SiteMap node, or in the <form action=/> tag.

In this scenario, the paths for the image, the SiteMap node, and the <form action=/> tag are also rewritten in the same manner as the URL.

For example, consider the following scenario:

• You have an Article.aspx file and an Image.gif file in the C: wwwroot folder. These files are configured to be available through http://localhost.
• You configure the URL Rewrite rule for URLs like http://localhost/1/AAA to be rewritten as http://localhost/article.aspx?id=1&title=AAA.
• You display the Image.gif file on the Article.aspx Web page by using <asp:Image runat=server ImageUrl=Image.gif />.

When you run the request for http://localhost/1/AAA, the URL is rewritten as http://localhost/article.aspx?id=1&title=AAA. Additionally, the path for the image is rendered as http://localhost/1/AAA/Image.gif. This path is incorrect, and you cannot see the image on the page.

Back to the top

Download information

The following files are available for download from the MicrosoftDownload Center:

Collapse this imageExpand this image

Download the Microsoft URL Rewrite Module for IIS 7.0 (x86) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=836778ea-b2f2-4907-b2dc-a152ec0a4bc4&amp;amp;displaylang=en)

Collapse this imageExpand this image

Download the Microsoft URL Rewrite Module for IIS 7.0 (x64) package now. (http://www.microsoft.com/downloads/details.aspx?familyid=6C15B777-8D9E-4D99-B359-A98E2C0880F7&amp;amp;displaylang=en)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Back to the top

Hotfix information

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

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the Microsoft .NET Framework 2.0 installed to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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

Back to the top