Consider the following scenario. You have an Apple iPod that is connected to a Windows Vista-based computer through a USB connection. Then, you disconnect the iPod from the computer. In this scenario, the data on the iPod may become corrupted.

This problem may occur if you use one of the following methods to disconnect the iPod:

•	You use the Safely Remove Hardware feature in the notification area to disconnect the iPod. Then, you disconnect the USB cable.
•	You use the Eject command in Windows Explorer to disconnect the iPod. Then, you disconnect the USB cable.

Back to the top

To resolve this problem, install update 936824. To install this update, visit the following Microsoft Web site:

Back to the top

Update information

The following files are available for download from the Microsoft Download Center:

Download the Download the update for Windows Vista 32-bit version (KB936824) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=6A9FC712-F518-44AB-A11F-B6AA22525DEC)
Download the update for Windows Vista 64-bit version (KB936824) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=A7A9FD92-7521-4A6F-BDD2-790EE2612D66)
Release Date: May 8, 2007

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.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update replaces update 933824.

File information

The English version of this 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.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb936824_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,735	30-Apr-2007	20:43	Not applicable
Package_1_for_kb936824~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	2,440	30-Apr-2007	20:41	Not applicable
Package_2_for_kb936824_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,983	30-Apr-2007	20:43	Not applicable
Package_2_for_kb936824~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	2,720	30-Apr-2007	20:41	Not applicable
Update-bf.mum	Not applicable	1,862	30-Apr-2007	20:43	Not applicable
Update.mum	Not applicable	1,897	30-Apr-2007	20:41	Not applicable
Usbstor.sys	6.0.6000.20588	55,296	28-Apr-2007	02:31	x86
X86_3062b910f8361f96560d8463846fbca1_31bf3856ad364e35_6.0.6000.20588_none_4e137d9609394891.manifest	Not applicable	699	30-Apr-2007	20:41	Not applicable
X86_f2dd01f2032c5b6566762661bf24827f_31bf3856ad364e35_6.0.6000.16478_none_e38721a2fccac79f.manifest	Not applicable	699	30-Apr-2007	20:41	Not applicable
X86_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.16478_none_04e03d3efd49bd96.manifest	Not applicable	1,308	28-Apr-2007	04:01	Not applicable
X86_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.20588_none_055f0a1e166f7951.manifest	Not applicable	1,308	28-Apr-2007	03:33	Not applicable
X86_usbstor.inf_31bf3856ad364e35_6.0.6000.16478_none_465c5f209ade1e53.manifest	Not applicable	1,482	30-Apr-2007	20:43	Not applicable
X86_usbstor.inf_31bf3856ad364e35_6.0.6000.20588_none_46db2bffb403da0e.manifest	Not applicable	1,482	30-Apr-2007	20:43	Not applicable
Usbstor.sys	6.0.6000.16478	55,296	28-Apr-2007	02:39	x86

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_97c033069d26f2fd361f80da50c07f32_31bf3856ad364e35_6.0.6000.20588_none_333d5b5494183685.manifest	Not applicable	703	30-Apr-2007	20:41	Not applicable
Amd64_ce91649dffd237d9476d3dd44be082c9_31bf3856ad364e35_6.0.6000.16478_none_2b5db0e1045caa2a.manifest	Not applicable	703	30-Apr-2007	20:41	Not applicable
Amd64_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.16478_none_60fed8c2b5a72ecc.manifest	Not applicable	1,310	28-Apr-2007	05:08	Not applicable
Amd64_microsoft-windows-ipod-fix-01_31bf3856ad364e35_6.0.6000.20588_none_617da5a1ceccea87.manifest	Not applicable	1,310	28-Apr-2007	04:44	Not applicable
Amd64_usbstor.inf_31bf3856ad364e35_6.0.6000.16478_none_a27afaa4533b8f89.manifest	Not applicable	1,484	30-Apr-2007	20:47	Not applicable
Amd64_usbstor.inf_31bf3856ad364e35_6.0.6000.20588_none_a2f9c7836c614b44.manifest	Not applicable	1,484	30-Apr-2007	20:47	Not applicable
Package_1_for_kb936824_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,745	30-Apr-2007	20:43	Not applicable
Package_1_for_kb936824~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	2,454	30-Apr-2007	20:41	Not applicable
Package_2_for_kb936824_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,995	30-Apr-2007	20:43	Not applicable
Package_2_for_kb936824~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	2,736	30-Apr-2007	20:41	Not applicable
Update-bf.mum	Not applicable	1,862	30-Apr-2007	20:43	Not applicable
Update.mum	Not applicable	1,897	30-Apr-2007	20:41	Not applicable
Usbstor.sys	6.0.6000.16478	66,048	28-Apr-2007	03:20	x64
Usbstor.sys	6.0.6000.20588	66,048	28-Apr-2007	02:58	x64

Back to the top

If the data on the iPod is corrupted, select the iPod in the Apple iTunes user interface. Then, on the Summary tab, click Restore to restore the iPod to working condition.

Apple recommends that you always use iTunes to disconnect or to eject an iPod. To eject an iPod in iTunes, click Eject iPod on the Controls menu. Then, disconnect the USB cable.

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 about this problem, visit the following Apple Web site:

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
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

Consider the following scenario. On a Windows-based computer that is running Windows Internet Explorer 7, you install the MS07-045 cumulative security update (KB937143) for Internet Explorer. Then, you use Internet Explorer 7 to browse certain Web sites. In this scenario, you may receive an error page that contains the following error message:

This issue occurs if a Web site that you browse is an Active Server Pages (ASP) page that calls a .NET-managed component.

Note This .NET-managed component uses .NET interop functionality.

Back to the top

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

Back to the top

Hotfix information for Windows XP

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

To apply this hotfix, you must have Windows XP Service Pack 2 (SP2) installed.

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.

File name	File version	File size	Date	Time	Platform
Urlmon.dll	7.0.6000.20733	1,162,752	07-Dec-2007	05:53	x86

Back to the top

Hotfix information for Windows Server 2003

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

To apply this hotfix, you must have Windows Server 2003 Service Pack 2 installed.

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.

File name	File version	File size	Date	Time	Platform
Urlmon.dll	7.0.6000.20733	1,162,752	06-Dec-2007	19:32	x86

Back to the top

Hotfix information for Windows Vista

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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

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

File name	File version	File size	Date	Time	Platform
Update.mum	Not Applicable	2,031	05-Dec-2007	12:47	Not Applicable
X86_395ee482d2c34d4bc21bf30dc6c83930_31bf3856ad364e35_6.0.6000.20733_none_6a8300a61a7b767b.manifest	Not Applicable	724	05-Dec-2007	12:47	Not Applicable
X86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_6.0.6000.20733_none_b369071af2d69a04.manifest	Not Applicable	283,492	05-Dec-2007	12:47	Not Applicable
Urlmon.dll	7.0.6000.20733	1,162,752	05-Dec-2007	04:09	x86

After you apply this hotfix, follow these steps to enable the changes that the hotfix makes:

1.	Click Start, click Run, type regedit , and then click OK.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Internet Explorer MAIN FeatureControl FEATURE_IGNORE_ZONES_INITIALIZATION_FAILURE_KB945701
3.	Right-click FEATURE_IGNORE_ZONES_INITIALIZATION_FAILURE_KB945701, point to New, and then click DWORD Value.
4.	Type w3wp.exe to name the new registry entry, and then press ENTER.
5.	Right-click w3wp.exe, and then click Modify.
6.	In the Value data box, type 1, and then click OK.
7.	Exit Registry Editor.

Note You must apply this hotfix on the Web server that is running Internet Information Services (IIS).

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

This article describes step-by-step instructions for how to disable certain Microsoft Internet Protocol version 6 (IPv6) components in Windows Vista. To disable IPv6 components, you must be logged on to the Windows Vista computer as a member of the Administrators group, or your user account must be granted permissions to edit the Windows registry.

Back to the top

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

To disable certain IPv6 components in Windows Vista, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list.
2.	In the User Account Control dialog box, click Continue.
3.	In Registry Editor, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Tcpip6 Parameters
4.	Double-click DisabledComponents to modify the DisabledComponents entry. Note If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps: a. In the Edit menu, point to New, and then click DWORD (32-bit) Value. b. Type DisabledComponents, and then press ENTER. c. Double-click DisabledComponents.
5.	Type any one of the following values to configure the IPv6 protocol, and then click OK: a. Type 0 to enable all IPv6 components. Note The value 0 is the default setting. b. Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface. This value also configures Windows Vista to use Internet Protocol version 4 (IPv4) instead of IPv6 in prefix policies. c. Type 0×20 to use IPv4 instead of IPv6 in prefix policies. d. Type 0×10 to disable native IPv6 interfaces. e. Type 0×01 to disable all tunnel IPv6 interfaces. f. Type 0×11 to disable all IPv6 interfaces except for the IPv6 loopback interface.

Note You must restart your computer for these changes to take affect.

Note Administrators must create an ADMX file in order to expose the settings in step 5 in a Group Policy setting.

Back to the top

For more information about how to manage Group Policy settings by using ADMX files, visit the following Microsoft TechNet Web site:

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

Back to the top

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

You create a shortcut (an .lnk file) to point to an executable file. However, on a computer that has Internet Explorer 7 installed, when you try to use Internet Explorer 7 to open the .lnk file, Internet Explorer 7 cannot load the target executable file.

Note This problem does not occur in Internet Explorer 6.

Back to the top

Windows XP

Service Pack information

To resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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, you must have Windows XP Service Pack 2 installed on the computer.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To enable this hotfix, follow these steps.

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

1.	Click Start, click Run, type regedit, and then press ENTER.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Internet Explorer Main FeatureControl
3.	On the Edit menu, point to New, and then click Key.
4.	Type the following key name, and then press ENTER: FEATURE_SHELLEXEC_FAVCENTER_KB952729
5.	On the Edit menu, point to New, and then click DWORD Value.
6.	Type iexplore.exe, and then press ENTER.
7.	On the Edit menu, click Modify.
8.	Type 1, and then click OK.
9.	Exit Registry Editor.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows XP with SP2, x86-based versions

File name	File version	File size	Date	Time	Platform
Ieframe.dll	7.0.6000.20833	6,068,224	15-May-2008	16:02	x86

Back to the top

Windows Server 2003

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, you must have Windows Server 2003 Service Pack 2 installed on the computer.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To enable this hotfix, follow these steps.

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

1.	Click Start, click Run, type regedit, and then press ENTER.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Internet Explorer Main FeatureControl
3.	On the Edit menu, point to New, and then click Key.
4.	Type the following key name, and then press ENTER: FEATURE_SHELLEXEC_FAVCENTER_KB952729
5.	On the Edit menu, point to New, and then click DWORD Value.
6.	Type iexplore.exe, and then press ENTER.
7.	On the Edit menu, click Modify.
8.	Type 1, and then click OK.
9.	Exit Registry Editor.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003 with SP2, x86-based versions

File name	File version	File size	Date	Time	Platform
Ieframe.dll	7.0.6000.20833	6,068,224	16-May-2008	10:52	x86

Back to the top

Windows Vista

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, you must have Windows Vista or Windows Vista Service Pack 1 installed on the computer.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To enable this hotfix, follow these steps.

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

1.	Click Start, type regedit in the Start Search box, and then press ENTER.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Internet Explorer Main FeatureControl
3.	On the Edit menu, point to New, and then click Key.
4.	Type the following key name, and then press ENTER: FEATURE_SHELLEXEC_FAVCENTER_KB952729
5.	On the Edit menu, point to New, and then click DWORD Value.
6.	Type iexplore.exe, and then press ENTER.
7.	On the Edit menu, click Modify.
8.	Type 1, and then click OK.
9.	Exit Registry Editor.

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

File name	File version	File size	Date	Time	Platform
Package_1_for_kb952729~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,780	13-May-2008	23:39	Not Applicable
Package_2_for_kb952729~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,719	13-May-2008	23:39	Not Applicable
Package_for_kb952729_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	13-May-2008	23:39	Not Applicable
Package_for_kb952729_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,430	13-May-2008	23:39	Not Applicable
Package_for_kb952729_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,363	13-May-2008	23:39	Not Applicable
Package_for_kb952729_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	13-May-2008	23:39	Not Applicable
Update.mum	Not Applicable	1,858	13-May-2008	23:39	Not Applicable
X86_ccf826bbdf755827196b148a3122a252_31bf3856ad364e35_6.0.6000.20833_none_5fb33f1c184a43f5.manifest	Not Applicable	695	13-May-2008	23:39	Not Applicable
X86_microsoft-windows-ieframe_31bf3856ad364e35_6.0.6000.20833_none_63285dc4ca2bb521.manifest	Not Applicable	748,166	13-May-2008	03:50	Not Applicable
Ieframe.dll	7.0.6000.20833	6,068,224	13-May-2008	03:15	x86
Ieui.dll	7.0.6000.20833	180,736	13-May-2008	03:15	x86

Windows Vista with SP1, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb952729~31bf3856ad364e35~x86~~6.0.2.0.mum	Not Applicable	1,942	14-May-2008	05:25	Not Applicable
Package_2_for_kb952729~31bf3856ad364e35~x86~~6.0.2.0.mum	Not Applicable	1,780	14-May-2008	05:25	Not Applicable
Package_for_kb952729_client_1~31bf3856ad364e35~x86~~6.0.2.0.mum	Not Applicable	1,367	14-May-2008	05:25	Not Applicable
Package_for_kb952729_client~31bf3856ad364e35~x86~~6.0.2.0.mum	Not Applicable	1,430	14-May-2008	05:25	Not Applicable
Package_for_kb952729_server_0~31bf3856ad364e35~x86~~6.0.2.0.mum	Not Applicable	1,425	14-May-2008	05:25	Not Applicable
Package_for_kb952729_server~31bf3856ad364e35~x86~~6.0.2.0.mum	Not Applicable	1,430	14-May-2008	05:25	Not Applicable
Update.mum	Not Applicable	2,082	14-May-2008	05:25	Not Applicable
X86_c943ae3653d07f3099f42999f9065214_31bf3856ad364e35_6.0.6001.22177_none_f8c001c6c02bce21.manifest	Not Applicable	695	14-May-2008	05:25	Not Applicable
X86_microsoft-windows-ieframe_31bf3856ad364e35_6.0.6001.22177_none_64e75bfcc76f1e0b.manifest	Not Applicable	748,166	13-May-2008	04:16	Not Applicable
Ieframe.dll	7.0.6001.22177	6,069,760	13-May-2008	03:14	x86
Ieui.dll	7.0.6001.22177	180,736	13-May-2008	03:14	x86

Back to the top

To work around this issue, convert the .lnk file to a .url file.

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:

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

When you try to open a file or a folder on an external Sony Ultra Portable universal serial bus (USB) drive (model VGP-UHDP04) that is connected to a Windows Vista-based computer, you cannot access the file or the folder. Additionally, Windows Explorer stops responding. This problem occurs after you wake the Windows Vista-based computer from hibernation.

Back to the top

This issue occurs because the USB port on the Windows Vista-based computer cannot detect the device speed of the USB drive.

Back to the top

To work around this issue, use one of the following methods.

Back to the top

Method 1

Disconnect the USB drive before you put the Windows Vista-based computer in hibernation.

Back to the top

Method 2

Disable hibernation on the Windows Vista-based computer. To do this, follow these steps:

1.	Click Start, and then click Control Panel.
2.	In Control Panel, double-click System and Maintenance, and then click Power Options.
3.	Under Preferred plans, select the plan that you want to change, and then click Change Plan Settings.
4.	On the Edit Plan Settings page, click Change advanced power settings.
5.	In the Advanced Settings dialog box, expand Sleep, and then expand Hibernate.
6.	Click the menu next to Setting (Minutes), click Never, and then click OK.
7.	On the Edit Plan Settings page, click Save changes.

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

Consider the following scenario. You use Windows Internet Explorer to visit a Microsoft Office SharePoint Portal Server site. When you select Explorer View on the site, a WebDAV PROPFIND request is sent. However, an extra forward slash mark (/) is appended to the query path in the WebDAV PROPFIND request.

Because of this behavior, the request may be blocked by some firewalls, or it may be routed to the wrong server. In this scenario, you cannot access the correct resource.

This problem may occur in the following Microsoft Windows operating systems:

•	Windows XP
•	Windows Vista
•	Windows Server 2008

Back to the top

Hotfix information for Windows XP

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows XP Service Pack 2 (SP2) or Windows XP Service Pack 3 (SP3) installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows XP with Service Pack 2, x86-based versions

File name	File version	File size	Date	Time	Platform
Mrxdav.sys	5.1.2600.3365	179,712	03-May-2008	10:30	x86

Windows XP with Service Pack 3, x86-based versions

File name	File version	File size	Date	Time	Platform
Mrxdav.sys	5.1.2600.5594	179,712	03-May-2008	12:04	x86

Back to the top

Hotfix information for Windows Vista and for Windows Server 2008

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing 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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista or Windows Server 2008, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb945015~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,777	01-May-2008	23:54	Not Applicable
Package_2_for_kb945015~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,163	01-May-2008	23:54	Not Applicable
Package_3_for_kb945015~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,228	01-May-2008	23:54	Not Applicable
Package_4_for_kb945015~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,228	01-May-2008	23:54	Not Applicable
Package_for_kb945015_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,408	01-May-2008	23:54	Not Applicable
Package_for_kb945015_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,641	01-May-2008	23:54	Not Applicable
Package_for_kb945015_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,712	01-May-2008	23:54	Not Applicable
Package_for_kb945015_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,408	01-May-2008	23:54	Not Applicable
Package_for_kb945015_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	01-May-2008	23:54	Not Applicable
Update.mum	Not Applicable	2,050	01-May-2008	23:54	Not Applicable
X86_8b6bbf650365b3f6405082de5a9e0a7b_31bf3856ad364e35_6.0.6001.22170_none_6773a664df1a2ee0.manifest	Not Applicable	1,412	01-May-2008	23:54	Not Applicable
X86_8d0a289ff6536d1d2f1c6b04a298c5f7_31bf3856ad364e35_6.0.6001.22170_none_5da8ab231f33eeea.manifest	Not Applicable	709	01-May-2008	23:54	Not Applicable
X86_c3992e9833fa67e9bf11d23102ef1b38_31bf3856ad364e35_6.0.6001.22170_none_d6b7a0e7dd737e23.manifest	Not Applicable	1,059	01-May-2008	23:54	Not Applicable
X86_dc003fa167f5e5782f3910cabd2aaf8c_31bf3856ad364e35_6.0.6000.20826_none_00a63860366d48fe.manifest	Not Applicable	1,412	01-May-2008	23:54	Not Applicable
X86_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.0.6000.20826_none_92612b2e6e411670.manifest	Not Applicable	5,069	01-May-2008	03:35	Not Applicable
X86_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.0.6001.22170_none_940b56966b959de5.manifest	Not Applicable	5,069	01-May-2008	03:57	Not Applicable
X86_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.0.6000.20826_none_133ea726e1bd8086.manifest	Not Applicable	13,639	01-May-2008	03:32	Not Applicable
X86_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.0.6001.22170_none_14e8d28edf1207fb.manifest	Not Applicable	13,642	01-May-2008	03:55	Not Applicable
X86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.0.6000.20826_none_53b98babcfb37f6d.manifest	Not Applicable	6,904	01-May-2008	03:36	Not Applicable
X86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.0.6001.22170_none_5563b713cd0806e2.manifest	Not Applicable	6,904	01-May-2008	03:59	Not Applicable
Davclnt.dll	6.0.6000.20826	54,272	01-May-2008	03:16	x86
Davclnt.dll	6.0.6001.22170	54,272	01-May-2008	03:22	x86
Mrxdav.sys	6.0.6000.20826	113,152	01-May-2008	00:48	x86
Mrxdav.sys	6.0.6001.22170	113,152	01-May-2008	00:54	x86
Webclnt.dll	6.0.6000.20826	196,608	01-May-2008	03:20	Not Applicable
Webclnt.dll	6.0.6001.22170	197,120	01-May-2008	03:28	Not Applicable

Windows Vista or Windows Server 2008, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_02d4aa7f877fca746224d0e6224f5dd9_31bf3856ad364e35_6.0.6000.20826_none_cdcce6f0a82c5600.manifest	Not Applicable	2,126	01-May-2008	23:54	Not Applicable
Amd64_5a92aae043892b97816a3ad911023ddd_31bf3856ad364e35_6.0.6001.22170_none_a583e2fb99aec674.manifest	Not Applicable	2,126	01-May-2008	23:54	Not Applicable
Amd64_777c92d38b1a368cb98b9c59592c2d27_31bf3856ad364e35_6.0.6001.22170_none_e6c75e7b7c6a86b1.manifest	Not Applicable	2,478	01-May-2008	23:54	Not Applicable
Amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.0.6000.20826_none_ee7fc6b2269e87a6.manifest	Not Applicable	5,087	01-May-2008	03:49	Not Applicable
Amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.0.6001.22170_none_f029f21a23f30f1b.manifest	Not Applicable	5,087	01-May-2008	04:17	Not Applicable
Amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.0.6000.20826_none_6f5d42aa9a1af1bc.manifest	Not Applicable	13,903	01-May-2008	03:47	Not Applicable
Amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.0.6001.22170_none_71076e12976f7931.manifest	Not Applicable	13,906	01-May-2008	04:14	Not Applicable
Amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.0.6000.20826_none_afd8272f8810f0a3.manifest	Not Applicable	6,934	01-May-2008	03:51	Not Applicable
Amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.0.6001.22170_none_b182529785657818.manifest	Not Applicable	6,934	01-May-2008	04:20	Not Applicable
Package_1_for_kb945015~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,860	01-May-2008	23:54	Not Applicable
Package_2_for_kb945015~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,922	01-May-2008	23:54	Not Applicable
Package_3_for_kb945015~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,696	01-May-2008	23:54	Not Applicable
Package_for_kb945015_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,416	01-May-2008	23:54	Not Applicable
Package_for_kb945015_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	01-May-2008	23:54	Not Applicable
Package_for_kb945015_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,721	01-May-2008	23:54	Not Applicable
Package_for_kb945015_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,416	01-May-2008	23:54	Not Applicable
Package_for_kb945015_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,438	01-May-2008	23:54	Not Applicable
Update.mum	Not Applicable	2,064	01-May-2008	23:54	Not Applicable
Wow64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.0.6001.22170_none_7b5c1864cbd03b2c.manifest	Not Applicable	8,609	01-May-2008	03:45	Not Applicable
Davclnt.dll	6.0.6000.20826	72,704	01-May-2008	03:26	x64
Davclnt.dll	6.0.6001.22170	72,704	01-May-2008	03:48	x64
Mrxdav.sys	6.0.6000.20826	137,216	01-May-2008	01:00	x64
Mrxdav.sys	6.0.6001.22170	137,216	01-May-2008	01:21	x64
Webclnt.dll	6.0.6000.20826	214,016	01-May-2008	03:29	x64
Webclnt.dll	6.0.6001.22170	214,528	01-May-2008	03:53	x64
Mrxdav.sys	6.0.6001.22170	113,152	01-May-2008	00:54	x86

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 about the PROPFIND method, visit the following Web site:

Back to the top

Back to the top

This article describes the detection and deployment guidance for the security release that is dated May 8, 2007.

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:

•	Security update 934233 (security bulletin MS07-023) MBSA 2.0.1 does not support the Excel 2000 part of this security update.
•	Security update 934232 (security bulletin MS07-024) MBSA 2.0.1 does not support the Word 2000 part of this security update.
•	Security update 934873 (security bulletin MS07-025) MBSA 2.0.1 does not support the Office 2000 part of this security update.
•	Security update 931832 (security bulletin MS07-026) MBSA 1.2.1 does not support the Exchange 2007 part of this security update.
•	Security update 931906 (security bulletin MS07-028) MBSA 1.2.1 does not support any part of this security update. The May 8, 2007 Enterprise Scan Tool will detect the need for this update.

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

When you view files and folders by using Windows Explorer, the Windows Explorer menu bar is not displayed.

Note The Windows Explorer menu bar includes the File menu, the Edit menu, the View menu, the Tools menu, and the Help menu.

Back to the top

By default, the menu bar is hidden in Windows Explorer.

Back to the top

To resolve this issue, use one of the following methods:

Back to the top

Method 1: Press the ALT key

To display the menu bar in Windows Explorer, press the ALT key. Pressing the ALT key again hides the menu bar.

Back to the top

Method 2: Set the menu bar to always appear

1.	Click Start, type explorer in the Start Search box, and then click Windows Explorer in the Programs list.
2.	Click Organize, click to select the Layout check box, and then click Menu Bar.

Back to the top

Consider the following scenario:

•	You connect more than one monitor on a Windows Vista-based or Windows Server 2008-based computer.
•	On a secondary monitor, you put a Windows Explorer window into full-screen mode by pressing the F11 key.

In this scenario, when you move the pointer to the top of the screen, the Windows Explorer navigation bar does not appear.

Notes

•	The navigation bar appears if the Windows Explorer window is maximized instead of in full-screen mode.
•	The navigation bar appears if you switch out of full-screen mode by pressing the F11 key.

Back to the top

Hotfix information

Windows Vista

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

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

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix, the computer must be running Windows Vista.

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.

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, 32-bit versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,776	14-Mar-2008	18:15	Not Applicable
Package_2_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,943	14-Mar-2008	18:15	Not Applicable
Package_3_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,781	14-Mar-2008	18:15	Not Applicable
Package_4_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,781	14-Mar-2008	18:15	Not Applicable
Package_5_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,776	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,713	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,430	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,420	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,424	14-Mar-2008	18:15	Not Applicable
Update.mum	Not Applicable	3,075	14-Mar-2008	18:15	Not Applicable
X86_197be20b0b8a90fa0bfeac29dad28e7e_31bf3856ad364e35_6.0.6000.20792_none_53ca3fb08b320046.manifest	Not Applicable	696	14-Mar-2008	18:15	Not Applicable
X86_a287a3acb005ea2c722bec5d78d96df2_31bf3856ad364e35_6.0.6001.22136_none_511bef340d65eb96.manifest	Not Applicable	696	14-Mar-2008	18:15	Not Applicable
X86_microsoft-windows-browseui_31bf3856ad364e35_6.0.6000.20792_none_2f26f12002940a1c.manifest	Not Applicable	48,516	14-Mar-2008	03:45	Not Applicable
X86_microsoft-windows-browseui_31bf3856ad364e35_6.0.6001.22136_none_31521075ff8658c3.manifest	Not Applicable	48,522	14-Mar-2008	03:57	Not Applicable
Browseui.dll	6.0.6000.20792	1,321,984	14-Mar-2008	03:19	x86
Browseui.dll	6.0.6001.22136	1,324,032	14-Mar-2008	03:18	x86

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_2f2a9ba93575b70a45a18c640770fa32_31bf3856ad364e35_6.0.6000.20792_none_7d06c49a121d01bf.manifest	Not Applicable	700	14-Mar-2008	18:15	Not Applicable
Amd64_9603cd5f92b2772cdc8a705f3e44ee95_31bf3856ad364e35_6.0.6000.20792_none_190a42971c6f30a7.manifest	Not Applicable	1,040	14-Mar-2008	18:15	Not Applicable
Amd64_e38fb56b4049e17d173e6dd67bc83ff0_31bf3856ad364e35_6.0.6001.22136_none_e8b81c2c1db1ac88.manifest	Not Applicable	1,040	14-Mar-2008	18:15	Not Applicable
Amd64_f38ebedbf27d291f496e41b4f4907fe9_31bf3856ad364e35_6.0.6001.22136_none_fbb39c5bd5a6b903.manifest	Not Applicable	700	14-Mar-2008	18:15	Not Applicable
Amd64_microsoft-windows-browseui_31bf3856ad364e35_6.0.6000.20792_none_8b458ca3baf17b52.manifest	Not Applicable	48,886	14-Mar-2008	04:04	Not Applicable
Amd64_microsoft-windows-browseui_31bf3856ad364e35_6.0.6001.22136_none_8d70abf9b7e3c9f9.manifest	Not Applicable	48,892	14-Mar-2008	04:26	Not Applicable
Package_1_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,786	14-Mar-2008	18:15	Not Applicable
Package_2_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,169	14-Mar-2008	18:15	Not Applicable
Package_3_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,005	14-Mar-2008	18:15	Not Applicable
Package_4_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,005	14-Mar-2008	18:15	Not Applicable
Package_5_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,786	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,723	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,438	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,428	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,432	14-Mar-2008	18:15	Not Applicable
Update.mum	Not Applicable	3,097	14-Mar-2008	18:15	Not Applicable
Browseui.dll	6.0.6000.20792	1,671,680	14-Mar-2008	03:33	x64
Browseui.dll	6.0.6001.22136	1,653,760	14-Mar-2008	03:47	x64

Windows Vista, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Ia64_04949d1d639a35fde44cb28b34f3378e_31bf3856ad364e35_6.0.6001.22136_none_2769eff6dded8627.manifest	Not Applicable	1,038	14-Mar-2008	18:15	Not Applicable
Ia64_4edf8af1b4ee483d2ee4bc73002e4986_31bf3856ad364e35_6.0.6001.22136_none_cb42ab447649d82d.manifest	Not Applicable	698	14-Mar-2008	18:15	Not Applicable
Ia64_microsoft-windows-browseui_31bf3856ad364e35_6.0.6001.22136_none_3153b46bff8461bf.manifest	Not Applicable	48,548	14-Mar-2008	04:09	Not Applicable
Package_1_for_kb949843~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,781	14-Mar-2008	18:15	Not Applicable
Package_2_for_kb949843~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,000	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,429	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,434	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,433	14-Mar-2008	18:15	Not Applicable
Update.mum	Not Applicable	1,923	14-Mar-2008	18:15	Not Applicable
Browseui.dll	6.0.6001.22136	3,175,936	14-Mar-2008	03:33	IA-64

Windows Server 2008

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2008 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, the computer must be running 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.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, 32-bit versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,776	14-Mar-2008	18:15	Not Applicable
Package_2_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,943	14-Mar-2008	18:15	Not Applicable
Package_3_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,781	14-Mar-2008	18:15	Not Applicable
Package_4_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,781	14-Mar-2008	18:15	Not Applicable
Package_5_for_kb949843~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,776	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,713	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,430	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,420	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,424	14-Mar-2008	18:15	Not Applicable
Update.mum	Not Applicable	3,075	14-Mar-2008	18:15	Not Applicable
X86_197be20b0b8a90fa0bfeac29dad28e7e_31bf3856ad364e35_6.0.6000.20792_none_53ca3fb08b320046.manifest	Not Applicable	696	14-Mar-2008	18:15	Not Applicable
X86_a287a3acb005ea2c722bec5d78d96df2_31bf3856ad364e35_6.0.6001.22136_none_511bef340d65eb96.manifest	Not Applicable	696	14-Mar-2008	18:15	Not Applicable
X86_microsoft-windows-browseui_31bf3856ad364e35_6.0.6000.20792_none_2f26f12002940a1c.manifest	Not Applicable	48,516	14-Mar-2008	03:45	Not Applicable
X86_microsoft-windows-browseui_31bf3856ad364e35_6.0.6001.22136_none_31521075ff8658c3.manifest	Not Applicable	48,522	14-Mar-2008	03:57	Not Applicable
Browseui.dll	6.0.6000.20792	1,321,984	14-Mar-2008	03:19	x86
Browseui.dll	6.0.6001.22136	1,324,032	14-Mar-2008	03:18	x86

Windows Server 2008, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_2f2a9ba93575b70a45a18c640770fa32_31bf3856ad364e35_6.0.6000.20792_none_7d06c49a121d01bf.manifest	Not Applicable	700	14-Mar-2008	18:15	Not Applicable
Amd64_9603cd5f92b2772cdc8a705f3e44ee95_31bf3856ad364e35_6.0.6000.20792_none_190a42971c6f30a7.manifest	Not Applicable	1,040	14-Mar-2008	18:15	Not Applicable
Amd64_e38fb56b4049e17d173e6dd67bc83ff0_31bf3856ad364e35_6.0.6001.22136_none_e8b81c2c1db1ac88.manifest	Not Applicable	1,040	14-Mar-2008	18:15	Not Applicable
Amd64_f38ebedbf27d291f496e41b4f4907fe9_31bf3856ad364e35_6.0.6001.22136_none_fbb39c5bd5a6b903.manifest	Not Applicable	700	14-Mar-2008	18:15	Not Applicable
Amd64_microsoft-windows-browseui_31bf3856ad364e35_6.0.6000.20792_none_8b458ca3baf17b52.manifest	Not Applicable	48,886	14-Mar-2008	04:04	Not Applicable
Amd64_microsoft-windows-browseui_31bf3856ad364e35_6.0.6001.22136_none_8d70abf9b7e3c9f9.manifest	Not Applicable	48,892	14-Mar-2008	04:26	Not Applicable
Package_1_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,786	14-Mar-2008	18:15	Not Applicable
Package_2_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,169	14-Mar-2008	18:15	Not Applicable
Package_3_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,005	14-Mar-2008	18:15	Not Applicable
Package_4_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,005	14-Mar-2008	18:15	Not Applicable
Package_5_for_kb949843~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,786	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,723	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,438	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,428	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpe~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,432	14-Mar-2008	18:15	Not Applicable
Update.mum	Not Applicable	3,097	14-Mar-2008	18:15	Not Applicable
Browseui.dll	6.0.6000.20792	1,671,680	14-Mar-2008	03:33	x64
Browseui.dll	6.0.6001.22136	1,653,760	14-Mar-2008	03:47	x64

Windows Server 2008, Itanium-based versions

File name	File version	File size	Date	Time	Platform
Ia64_04949d1d639a35fde44cb28b34f3378e_31bf3856ad364e35_6.0.6001.22136_none_2769eff6dded8627.manifest	Not Applicable	1,038	14-Mar-2008	18:15	Not Applicable
Ia64_4edf8af1b4ee483d2ee4bc73002e4986_31bf3856ad364e35_6.0.6001.22136_none_cb42ab447649d82d.manifest	Not Applicable	698	14-Mar-2008	18:15	Not Applicable
Ia64_microsoft-windows-browseui_31bf3856ad364e35_6.0.6001.22136_none_3153b46bff8461bf.manifest	Not Applicable	48,548	14-Mar-2008	04:09	Not Applicable
Package_1_for_kb949843~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,781	14-Mar-2008	18:15	Not Applicable
Package_2_for_kb949843~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,000	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,429	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,434	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	14-Mar-2008	18:15	Not Applicable
Package_for_kb949843_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,433	14-Mar-2008	18:15	Not Applicable
Update.mum	Not Applicable	1,923	14-Mar-2008	18:15	Not Applicable
Browseui.dll	6.0.6001.22136	3,175,936	14-Mar-2008	03:33	IA-64

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:

Back to the top

When a user visits a Web site that you own, and the user downloads a file by using Windows Internet Explorer 7, the user may find that certain characters in the file name are converted to underscore characters (_) after they download the file.

This problem occurs when any of the following characters are in the file name.

Character	Name
<	Left angle bracket
>	Right angle bracket
	Backslash
	Quotation mark
/	Slash mark
:	Colon
|	Vertical bar
?	Question mark
*	Asterisk
	Space

Back to the top

This problem occurs because the Wininet.dll file resolves certain file stream issues when users download files by using Internet Explorer 7.

Back to the top

To resolve this problem, do not use Content-Disposition: Attachment; filename= HTTP header.

Back to the top

If a file name in this header contains a certain special characters, the cache code calls the CreateFileA() method on that name. If you use the NTFS file system, an alternative stream is created. Then, the WinInet.dll file writes only to the alternative stream.

When a cache entry is committed, the file name is included in the cache entry. Because the CreateFileA() method on the named stream works, the WinInet.dll file does not generate an error. Instead, it uses a random name. Therefore, when the cache entry is retrieved, and the caller tries to open the file, the open operation fails because WinInet.dll file tries to open the FileName file. Instead, the WinInet.dll file must open the FileName:$DATA file.

Therefore, you cannot cache or download content when the Content-Disposition file name token contains a file name that uses one of the special characters that are listed in the Symptoms section. The new version of the WinInet.dll file resolves this problem by checking for these characters and replacing them with an underscore character.

Back to the top

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

When calling a web service from a .net client you may see a delay.

From Internet Explorer, it may take a couple of seconds for the request to complete but when calling the same web method from a .net client it takes an extra 20 seconds.

Proxy auto detection delay

Use one of the following methods:

 

Method 1:  Turn off “Automatically Detect Settings” in Internet Explorer

 

Method 2:  Modify machine.config or app.config to disable .Net framework from using the autoproxy feature.

<configuration>

<system.net>

<defaultProxy >

<!– Disable Autoproxy–>

<proxy autoDetect=false/>

</defaultProxy>

</system.net>

</configuration>

The following article does an excellent job of explaining how proxy support works in .net framework:

 

Take the Burden Off Users with Automatic Configuration in .NET

http://msdn.microsoft.com/en-us/magazine/cc300743.aspx (http://msdn.microsoft.com/en-us/magazine/cc300743.aspx)

 

Here is a snippet from the section titled Proxy Support in the .NET Framework 2.0 which explains the reason for the delay when the Autoproxy protocol is implemented:

Automatic proxy configuration is now fully supported. The .NET Framework 2.0 reads the complete settings from the registry, including the automatic configuration flags and any explicitly provided script location. Automatic detection happens by first using the DHCPINFORM message and then using the DNS resolution techniques already described. Once the script location is identified, the script is

downloaded, compiled into an in-memory assembly, and then executed in a sandbox app domain where minimal permissions are granted.

 

In fact, no code access security (CAS) permissions are granted to the script other than the execution permission. Minimal permissions mean that rogue scripts can’t do anything significant other than call the few functions exposed to the script. For a detailed sample of how to host and run your own scripts in a sandbox app domain, see the sidebar, Hosting the Proxy Script.

 

Failover is also built in. If auto-detection fails and if you have entered an explicit script location, then that script is downloaded and run. If both fail and if you have a static proxy, then the static proxy is used as a fallback. If all fail, a direct connection to the target URL is attempted.

 

So, all of the above happens when the registry key is examined and the value indicates “Automatically detect settings”. The reason for the delay is the time it takes to do all of the above before trying

the direct connection.

 

If you have to use a specific proxy server, specify it in code or config file through <defaultProxy> setting, which is documented in MSDN:

<defaultProxy> Element (Network Settings)

http://msdn.microsoft.com/en-us/library/kd3cf2ex(VS.80).aspx (http://msdn.microsoft.com/en-us/library/kd3cf2ex(VS.80).aspx)

 

For additional information, see the following:

 

·         307220 HOW TO: Configure an XML Web Service Client by Using the .NET Framework to Work with a Proxy Server    /307220 (http://support.microsoft.com/default.aspx?scid=kb;en-us;307220)

 

·         330221 PRB: Common Proxy Server and Firewall Issues with MapPoint Web Services /330221 (http://support.microsoft.com/default.aspx?scid=kb;en-us;330221)

 

·         Take the Burden Off Users with Automatic Configuration in .NET http://msdn.microsoft.com/en-us/magazine/cc300743.aspx (http://msdn.microsoft.com/en-us/magazine/cc300743.aspx)

 

 

How to change the machine.config to disable the default proxy settings

Here is an example how you can change the machine.config to disable using the default settings for the proxy, and instead specify your own proxy settings:

<defaultProxy>

<proxy

usesystemdefault = false

proxyaddress=<http://proxyserver:port>

bypassonlocal=true

/>

<bypasslist>

<add address=100.100.100.100 />

</bypasslist>

</defaultProxy>

 

You can, alternatively, set the proxy name and bypass list in code on the Proxy property on the web service object:

WebProxy Class

http://msdn.microsoft.com/en-us/library/system.net.webproxy(VS.80).aspx (http://msdn.microsoft.com/en-us/library/system.net.webproxy(VS.80).aspx)

 

 

 

 

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

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.

In Windows Vista, a gadget that you downloaded from the Internet may appear to be installed correctly. However, the gadget does not appear in the Windows Sidebar as expected.

Back to the top

This issue occurs if the gadget does not support a language that is in the list of preferred languages for the current user.

Back to the top

This behavior is by design.

Back to the top

If a language for the gadget is not installed, the gadget does not appear in the Windows Sidebar. Typically, this issue occurs when the Japanese, French, or German version of Windows Vista is installed.

To help resolve this issue, ask the gadget developer to supply the language for the gadget.

Note You may be able to resolve this issue by installing a language pack that includes a language that matches the language in the gadget. For more information about how to install more languages, see Windows Help and Support.

Back to the top

On a Windows Vista or Windows Server 2008-based computer, you have a folder that contains many layers of subfolders. Each subfolder contains only one subfolder. When you try to expand the parent folder in the Windows Explorer navigation pane, Windows Explorer expands the folder to the last level of the subfolders as long as each subfolder contains only one subfolder. This problem may cause Windows Explorer to crash if there are many layers of subfolders.

If you have a subfolder that contains two or more subfolders, Windows Explorer stops expanding the folders when it reaches the folder that contains the two subfolders. For example, you have the following folder tree:

• C: temp
  • C: temp 1
    • C: temp 1 2
      • C: temp 1 2 3
        • C: temp 1 2 3 4
          • C: temp 1 2 3 4 4a
          • C: temp 1 2 3 4 4b

When you click the triangular icon to expand the C: temp folder, Windows Explorer expands all the way to the C: temp 1 2 3 4 folder. Windows Explorer does not expand the subfolders inside the C: temp 1 2 3 4 folder because that folder has two subfolders, 4a and 4b.

Note This problem does not occur in Windows operating systems that are earlier than Windows Vista.

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:

There are no prerequisites for Windows Server 2008-based computers.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

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

After you install this hotfix, you have to make the following changes to the registry to set the value of the DoNotExpandSingletons registry entry to 1:

1. Click Start, type regedit in the Start search box, and then press ENTER.
   If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.
2. Locate and then expand the following registry subkey:
   HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Explorer Advanced
3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
4. Type DoNotExpandSingletons, and then press ENTER.
5. Right-click DoNotExpandSingletons, and then click Modify.
6. In the Edit DWORD (32-bit) Value box, type 1 in the Value data box, and then click OK.
7. Exit Registry Editor.
8. Restart the computer.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

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

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

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

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

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

Additional file information for Windows Server 2008 and Windows Vista

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

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

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

On a Windows Vista-based computer, you cannot use keyboard shortcuts to select more than one item in Windows Explorer. For example, you cannot use the CTRL+A keyboard shortcut to select all the items in a Windows Explorer window. Also, you cannot select multiple items in a Windows Explorer window by holding the SHIFT key or the CTRL key while you click the items.

Back to the top

This problem occurs because certain applications add a key to the registry. The key prevents you from selecting multiple items in Windows Explorer.

Back to the top

To resolve this issue, use the Reset Folders command. To use the Reset Folders command, follow these steps:

1.	In the Windows Explorer window where this issue occurs, click Organize, and then click Folder and Search Options.
2.	On the View tab, click Reset Folders.

Note You may have to repeat these steps if you experience this problem again. The applications that cause this problem may insert the key into the registry whenever they run.

Back to the top

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