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

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

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

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

How to obtain help and support for this security update

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

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

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

Additional information about this security update

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

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

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

File information

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

For all supported versions of Windows 2000

Windows XP and Windows Server 2003 file information notes

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

For all supported x86-based versions of Windows XP

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

For all supported x86-based versions of Windows Server 2003

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

Windows Vista and Windows Server 2008 file information notes

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

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

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

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

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

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

Additional file information for Windows Server 2008 and for Windows Vista

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

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

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

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

This article describes the Microsoft IPsec Diagnostic Tool that is available for use in the following Windows operating systems:

•	Windows Server 2008
•	Windows Vista
•	Windows Server 2003
•	Windows XP

You can use the Microsoft IPsec Diagnostic Tool to check for common network problems on the host computer. When problems are found, the tool suggests appropriate repair commands. The tool also collects IPsec policy information on the computer, and it parses the IPsec logs to determine the reasons for network failures. Additionally, you can use this tool for collecting traces of VPN connections and for collecting information about NAT clients, about Windows Firewall configuration, about Group Policy updates, about Wireless events, and about System events.

This diagnostic report that is generated by this tool is derived from the system logs that are collected by the tool during its analysis phase. Therefore, this report is conclusive. The information in these logs is sufficient to diagnose any network-related issues. For assisted support, you may have to share the logs with network administrators or with Microsoft Support. For more assistance, see the Help feature that is included with the tool.

To download the Microsoft IPsec Diagnostic Tool, visit the following Microsoft Download Center Web site:
The following file is available for download from the Microsoft Download Center:
Download the Microsoft IPSec Diagnostic Tool – 1.0.msi package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=1d4c292c-7998-42e4-8786-789c7b457881&DisplayLang=en)Release Date: January 30, 2008

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.

In a C++ Microsoft Jet DAO MFC (CDao) application, insertions and updates may not work on a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008. Additionally, you may receive the following error message:

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

Back to the top

This problem occurs when all the following conditions are true:

•	The application is written in Microsoft Visual C++ and uses the CDao classes to access a Microsoft Jet database data source.
•	The Use Multi-Byte Character Set value is set for the Character Set project option.
•	The data that the application is inserting or updating was retrieved from a fixed-length defined Text column.
•	The source Text column contains data that is the maximum length that the column allows. For example, a Text(10) column contains a value of 1234567890.
•	Successive insertions or updates occur from the original variable that is returned from the CDaoRecordset object.
•	The target table column is one of the following columns: • The same column from which the original data was retrieved • Another fixed-length column that is defined as a Text column of the same size

Back to the top

To resolve this problem, apply the hotfix that is described in Microsoft Knowledge Base article 943509.

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

Back to the top

If you cannot apply the hotfix that is described Microsoft Knowledge Base article 943509, use one of the following methods to work around this problem:

•	Update the application. To do this, copy the retrieved data from the original Visual C++ variable to a new variable. Then, insert or update the data from the new variable.
•	Update the database design. To do this, use one of the following methods: • Modify the column widths to one character larger than any expected data. • Redefine the width as a non-fixed length.

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

On a Windows Vista-based computer, the Microsoft ISATAP adapter appears with a yellow exclamation mark (!) next to it in Device Manager. Additionally, when you open the properties dialog box for the device, you receive an error message that resembles the following:

Back to the top

You can safely ignore this error message. This error message does not indicate a problem with the adapter. The adapter will continue to work correctly.

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

The Microsoft ISATAP device Inter Site Automatic Tunneling Address Protocol is used to help enterprises transition to an IPv6 infrastructure. The ISATAP adapter encapsulates IPv6 packets by using an IPv4 header. This functionality enables the client to transport IPv6 traffic over an IPv4 infrastructure. This approach lets organizations slowly migrate to an IPv6 infrastructure without having to spend excessive time and financial resources to convert to the new infrastructure.

Back to the top

When you run a Microsoft .NET Framework 2.0-based application, you receive a System.InvalidOperationException exception. This problem occurs if the following conditions are true:

•	You have installed security update MS 07-040 on the computer.
•	The .NET Framework 2.0-based application contains several enum types.
•	The enum types contain the XmlType attribute.
•	You set the AnonymousType field to True in the XmlType attribute.

If you have not installed security update MS 07-040 on the computer, you do not receive the exception.

If you change the AnonymousType field to False, you do not receive the exception even if you have installed security update MS 07-040.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next 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 the .NET Framework 2.0 SP1 installed.

Restart requirement

You have to 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) 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 tool in Control Panel.

File name	File version	File size	Date	Time	Platform
System.xml.dll	2.0.50727.1822	2,052,096	27-Mar-2008	03:36	x86

Back to the top

When this issue occurs, the call stack that is generated resembles the following:

System.InvalidOperationException was unhandledMessage=Unable to generate a temporary class (result=1). r nerror CS0266: Cannot implicitly convert type 'ConsoleApplication2.Color1?' to 'ConsoleApplication2.Color2?'. An explicit conversion exists (are you missing a cast?) r nSource=System.XmlStackTrace:at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)at System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)at ConsoleApplication2.Program.Main(String[] args) in C: Users daroth Documents Visual Studio 2008 Projects DevDivBugs162210 ConsoleApplication2 Program.cs:line 48at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)at System.Threading.ThreadHelper.ThreadStart()InnerException: 

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

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

Back to the top

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

Back to the top

Microsoft has released security bulletin MS07-017. The security bulletin contains all the relevant information about the security update. This information includes file manifest information and deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites:

•	Home users: http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx (http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx)
•	IT professionals: http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx (http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx)

Back to the top

Known issues

•

Microsoft is aware of an issue that affects a limited number of printer drivers. When you try to print by using one of these drivers, you may experience the following symptoms: • Your computer automatically restarts. • After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error.A log of this error has been created. Please tell Microsoft about this problem.We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you click the link at the bottom of the message box, you see error signature information that resembles the following: BCCode : 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) OSVer : 5_1_2600 SP : 0_0 Product : 256_1 • You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer… Technical information: *** Stop 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) UNEXPECTED_KERNEL_MODE_TRAP For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 935843 (/Feedback.aspx?kbNumber=935843/) Stop 0×0000007F error when you print from Windows XP or Windows 2000 with GDI security update 925902 installed

•

After you install this security update on a computer that is running Windows XP with Service Pack 2, certain third-party applications may not start. Additionally, you receive an error message that resembles the following: application_executable_name – Illegal System DLL Relocation The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL C: Windows System32 Hhctrl.ocx occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL. For more information about this issue, and to see a list of third-party programs that Microsoft has confirmed are affected by this problem, click the following article number to view the article in the Microsoft Knowledge Base: 935448 (/Feedback.aspx?kbNumber=935448/) Certain programs may not start, and you receive an error message on a computer that is running Windows XP Service Pack 2: Illegal System DLL Relocation If you receive a similar message when you use other programs, install update 935448. If we confirm that other programs are affected by this problem, we will update Microsoft Knowledge Base article 935448 with more information.

Back to the top

The revision number and the review dates for this article may reflect minor editorial revisions or structural revisions to this content. The major technical revisions to this content are listed in this table.

Date	Revisions
April 17, 2007	Updated the Known issues section to include information about a Stop error that you may receive after you install this security update. Added this table.

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:

•	A 64-bit application that is created by using the Microsoft .NET Framework 2.0 calls some COM APIs.
•	The COM APIs have multiple instances of the same method.
•	The method uses the lcid attribute.
•	You use one of the following to call the COM APIs: • The managed COM interop • Platform Invoke (P/Invoke) code

In this scenario, incorrect methods are called.

For example, consider the following scenario:

•	You have a 64-bit application that uses a 64-bit version of common language runtime (CLR).
•	The application has two managed P/Invoke functions that have the same signature. The signature points to a single native method.
•	The two P/Invoke functions rely on the LCIDConversionAttribute class for localization support.
•	You run the application.

In this scenario, you may receive an error message that resembles the following:

Back to the top

Hotfix information

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

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

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

Prerequisites

You must have one of the following installed to apply this hotfix:

•	Windows Vista Service Pack 1
•	The .NET Framework 2.0 Service Pack 1

Restart requirement

You do not have to 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.

The .NET Framework 2.0, 32-bit versions, on a computer that is not running Windows Vista

File name	File version	File size	Date	Time	Platform
Cordacwks.dll	2.0.50727.1812	822,280	29-Jan-2008	10:48	x86
Mscorlib.dll	2.0.50727.1812	4,345,856	29-Jan-2008	10:48	x86
Mscorwks.dll	2.0.50727.1812	5,852,672	29-Jan-2008	10:48	x86

The .NET Framework 2.0, Itanium-based versions, on a computer that is not running Windows Vista

File name	File version	File size	Date	Time	Platform
Cordacwks.dll	2.0.50727.1812	822,280	29-Jan-2008	10:48	x86
Cordacwks.dll	2.0.50727.1812	2,769,416	29-Jan-2008	02:26	IA-64
Mscorlib.dll	2.0.50727.1812	4,345,856	29-Jan-2008	10:48	x86
Mscorlib.dll	2.0.50727.1812	3,997,696	29-Jan-2008	02:26	IA-64
Mscorwks.dll	2.0.50727.1812	5,852,672	29-Jan-2008	10:48	x86
Mscorwks.dll	2.0.50727.1812	21,686,272	29-Jan-2008	02:26	IA-64

The .NET Framework 2.0, 64-bit versions, on a computer that is not running Windows Vista

File name	File version	File size	Date	Time	Platform
Cordacwks.dll	2.0.50727.1810	1,652,744	14-Jan-2008	23:36	x64
Cordacwks.dll	2.0.50727.1812	822,280	29-Jan-2008	10:48	x86
Mscorlib.dll	2.0.50727.1810	4,345,856	14-Jan-2008	23:36	x64
Mscorlib.dll	2.0.50727.1812	4,345,856	29-Jan-2008	10:48	x86
Mscorwks.dll	2.0.50727.1810	10,547,200	14-Jan-2008	23:36	x64
Mscorwks.dll	2.0.50727.1812	5,852,672	29-Jan-2008	10:48	x86

The .NET Framework 2.0 on a computer that is running a 32-bit version of Windows Vista with Service Pack 1

File name	File version	File size	Date	Time	Platform
Mscorlib.dll	2.0.50727.1826	4,345,856	06-May-2008	22:18	x86
Mscordacwks.dll	2.0.50727.1826	822,280	06-May-2008	22:18	x86
Mscorwks.dll	2.0.50727.1826	5,852,672	01-May-2008	23:34	x86

The .NET Framework 2.0 on a computer that is running a 64-bit version of Windows Vista with Service Pack 1

File name	File version	File size	Date	Time	Platform
Mscorlib.dll	2.0.50727.1826	4,345,856	05-May-2008	22:13	x64
Mscordacwks.dll	2.0.50727.1826	1,652,744	05-May-2008	22:13	x64
Mscorwks.dll	2.0.50727.1826	10,543,104	01-May-2008	23:36	x64
Mscorlib.dll	2.0.50727.1826	4,345,856	06-May-2008	22:18	x86
Mscordacwks.dll	2.0.50727.1826	822,280	06-May-2008	22:18	x86
Mscorwks.dll	2.0.50727.1826	5,852,672	01-May-2008	23:34	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 P/Invoke, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about the lcid attribute, visit the following MSDN Web site:

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

Back to the top

Back to the top

This article discusses the support boundaries that PSS provides for Windows PE 2.0 and describes methods for network booting Windows PE 2.0. This article specifically addresses the Pre-Boot Execution Environment (PXE) network boot technology. It does not encompass other network boot technologies that perform block-level I/O over a network connection, such as the Internet small computer system interface (iSCSI) boot technology.

Back to the top

A network booting client performs the following tasks:

•	Obtains an IP address
•	Discovers a valid network boot server
•	Downloads and executes a network boot application

The code execution in the network boot application leads to a full download and to a boot of Windows PE.

Hardware support for network boot operations

The ability to network boot comes from code that is embedded into the ROM of the network adapter or of the motherboard of the computer. This code contains logic that controls, among other things, network boot device initialization, User Datagram Protocol (UDP) transport support, and Trivial File Transfer Protocol (TFTP) support. For a certain class of PCI network interface cards (NICs), you may boot a device that uses software that emulates the function of an onboard PXE ROM in order to enable the device to boot. This external software usually takes the form of a network boot floppy disk.

Hardware PXE ROM issues

PSS support for hardware-related PXE ROM issues is limited to a commercially reasonable effort. If PSS determines that the issue is related to the hardware PXE ROM, you must obtain support directly from the vendor of the computer or from the hardware manufacturer.

Software PXE ROM issues

Microsoft provides software PXE ROM emulation in the form of a Remote Installation Service (RIS) boot floppy disk. This can be used to boot supported network adapters. PSS provides full support for this utility. Additionally, implementations of a software PXE ROM are available from other software vendors. If PSS determines that the issue is related to a non-Microsoft PXE ROM implementation, you must obtain support directly from the software vendor.

Methods to direct a booting PXE client to the correct network boot file

The following methods may be used to direct a booting PXE client to download and execute the correct network boot file:

•	The client may contact the network boot server directly to obtain the correct network boot file.
•	The client may receive the correct network boot file information from a Dynamic Host Configuration Protocol (DHCP) server.

IP Helper table updates

The PXE network boot method uses DHCP packets for communication. The DHCP packets serve a dual purpose. They are intended to help the client in obtaining an IP address lease from a DHCP server and to locate a valid network boot server. If the booting client, the DHCP server, and the network boot server are all located on the same network segment, usually no additional configuration is necessary. The DHCP broadcasts from the client reach both the DHCP server and the network boot server.

However, if either the DHCP server or the network boot server are on a different network segment than the client, or if they are on the same network segment but the network is controlled by a switch or a router, you may have to update the routing tables for the networking equipment in order to make sure that DHCP traffic is directed correctly.

Such a process is known as performing IP Helper table updates. When you perform this process, you must configure the networking equipment so that all DHCP broadcasts from the client computer are directed to both a valid DHCP server and to a valid network boot server.

After the client computer has obtained an IP address, it contacts the network boot server directly in order to obtain the name and the path of the network boot file to download. Again, this process is handled by using DHCP packets.

DHCP options 60, 66, and 67

In some environments, it may be appropriate to use following DHCP options to direct PXE clients to an appropriate network boot file to download:

•	60 = client Identifier set to the string value of PXEClient
•	66 = boot server host name
•	67 = boot file name

When you use these DHCP options, client computers receive the following information directly from the DHCP server:

•	An IP address lease
•	Information about the correct boot server
•	Information about the correct boot file

In this scenario, client computers do not contact the network boot server by using DHCP. Instead, TFTP is used to specify a file that is downloaded directly. This method may be used as an alternative to the IP Helper update method that is described in this article. However, we do not recommend that you use this method for the following reasons:

•	Using DHCP options is not as reliable as updating the IP Helper tables. In testing, Microsoft has observed that some client computers do not correctly parse the DHCP options that are returned from the DHCP server. This problem occurs most frequently when older PXE ROMs are used. The result is that booting client computers will report the following error message: TFTP Failed This problem occurs when the PXE ROM does not process the boot server host name value and tries to download the network boot application directly from the DHCP server.
•	If multiple network boot servers are available to service client requests, and if a network boot server name is explicitly provided as part of the DHCP scope, load-balancing may not occur correctly.
•	Client computers may be directed to a network boot server that is unavailable. Because client computers do not have to contact a network boot server directly in order to determine the appropriate network boot file to download, you may discover that client computers are directed by the DHCP server to a boot file that does not exist or to a server that is unavailable.
•	Client computers may bypass the answer settings for the network boot server. Many network boot servers provide an on/off mechanism that enables you to control whether certain client requests are answered. According to the PXE standard, client computers must contact the network boot server directly to obtain the path and the file name of the network boot application. Additionally, when you use DHCP options 66 and 67, the client computer may completely bypass communication with the network boot server. When this occurs, the settings for the network boot server are not used.

Network boot referrals

A network boot referral, or a PXE boot referral, occurs when a client computer is directed to download a network boot application from a different server than the one with which it is communicating by using DHCP.

A network boot referral or a PXE boot referral occurs as part of the discovery process to determine the network boot server name and the network boot file name. Either a network boot server or a DHCP server may initiate this referral.

First order referral from a PXE server

Consider the following scenario:

•	Computer A broadcasts a DHCP packet and receives an IP address lease from a DHCP server. Computer A also receives a network boot response from PXE Server 1.
•	Computer A contacts PXE Server 1 directly by using port 4011.
•	PXE Server 1 directs Computer A to download the boot x86 wdsnbp.com file from the TFTP server.
•	Computer A downloads the boot x86 wdsnbp.com file from the TFTP server.

In this scenario, PSS fully supports referral of x86-based client computers and the referral of x64-based client computers as long as all the following requirements are met:

•	The name of the network boot application that the client computer is directed to download from the TFTP server must be wdsnbp.com. Warning Pointing to pxeboot.com is an unsupported scenario.
•	The network boot server (PXE Server 1) that performs the referral must be running Microsoft Windows Deployment Services.

First order referral by using DHCP options

Consider the following scenario:

•	Computer A broadcasts a DHCP packet and receives an IP address lease from a DHCP server.
•	The lease also contains values for DHCP options 66 and 67. These refer the Computer A to download the boot x86 wdsnbp.com file from Server 1.
•	Computer A downloads the boot x86 wdsnbp.com file from Server 1.

In this scenario, PSS fully supports referral of x86-based client computers and the referral of x64-based client computers as long as all the following requirements are met:

•	The name of the network boot application that the TFTP server directs the client computer to download must be wdsnbp.com.

Second order referral by using both DHCP options and PXE server

Consider the following scenario:

•	Computer A broadcasts a DHCP packet and receives an IP address lease from a DHCP server.
•	The lease also contains values for DHCP options 66 and 67. These options refer Computer A to download the boot x86 wdsnbp.com file from the PXE server.
•	Computer A downloads the boot x86 wdsnbp.com file from the PXE server.
•	Computer A executes the boot x86 wdsnbp.com file, and Wdsnbp.com contacts the PXE server on port 4011.
•	The PXE server refers Computer A to download the boot x86 wdsnbp.com file from the TFTP server.
•	Computer A downloads the boot x86 wdsnbp.com file from the TFTP server.

In this scenario, PSS fully supports referral of x86-based client computers and the referral of x64-based client computers as long as all the following requirements are met:

•	The name of the network boot application that the PXE Server directs the client computer to download must be wdsnbp.com.
•	The network boot server (PXE Server) that performs the referral must be running Windows Deployment Services.

Network boot of Windows PE 2.0 by using a Microsoft PXE server

At the time of this writing, the following network boot servers, or PXE servers, are available from Microsoft:

•	Windows Deployment Services We recommend that you use Windows Deployment Services for network booting Windows PE 2.0. This solution is fully supported by PSS.
•	Remote Installation Services (RIS) PSS does not support the network boot of Windows PE 2.0 from this platform. Upgrade your existing RIS servers to Windows Deployment Services in order to acquire this functionality.
•	Automated Deployment Services (ADS) PSS does not support the network boot of Windows PE 2.0 from this platform.
•	Windows Embedded Remote Boot PSS does not support the network boot of Windows PE 2.0 from this platform.

Network boot of Windows PE 2.0 by using a third-party PXE server

PSS support for network boot issues that result from the use of a third-party PXE server is limited to a commercially reasonable effort. If PSS determines that the issue is related to the third-party PXE server implementation, you must obtain support directly from the third-party software vendor. This support policy also covers scenarios in which the server implementation does not handle DHCP traffic and provides only TFTP functionality.

Network boot of Windows PE 2.0 by using a third-party boot application

PSS fully supports the network boot process of Windows PE 2.0 when a Microsoft boot loader is responsible for all the following actions:

•	Downloading the boot image
•	Creating a RAMDISK
•	Booting Windows PE

If you use third-party software to perform any of the actions in this list, the PSS support policy is defined as follows:

•	You use a third-party network boot program to call into a Microsoft network boot application PSS support for network boot issues that result from the use of a third-party network boot program to boot Windows PE 2.0 is limited to a commercially reasonable effort. If PSS determines that the issue is related to the third-party implementation, you must obtain support directly from the third-party software vendor.
•	You use a third-party network boot program to call directly into the Microsoft Windows PE loader PSS does not support this method for booting Windows PE 2.0.
•	You use a third-party download manager in order to download the Windows PE 2.0 image PSS does not support this method for booting Windows PE 2.0.
•	You use a third-party loader to create the RAMDISK image and you try to boot Windows PE PSS does not support this method of booting Windows PE 2.0.
•	You use a third-party boot loader or download manager, or both, as a piece of intermediate software in order to intercept or redirect calls, or both, from a Microsoft network boot program or boot loader PSS does not support this method of booting Windows PE 2.0.

Image Formats

Windows PE 2.0 can boot by using two boot image formats. Only one of the supported boot image formats may be used when network booting.

•

RAMDISK boot By using this boot method, a virtual disk volume is created in RAM to hold a boot image for Windows PE. The Windows PE image is downloaded as part of the network boot process and is put into the virtual disk memory space. Windows PE is then loaded and run directly from that media. This method of booting Windows PE 2.0 is fully supported by PSS as long as the following requirements are met: • The Windows PE image is provided in Windows Imaging (WIM) format. • The computer that is trying to network boot Windows PE has at least 512mb of RAM. Note Additional RAM may be required on the client computer depending on application requirements or the size of the WIM image that contains the Windows PE boot image, or both.

•

Flat file boot PSS does not support this method of network booting Windows PE 2.0.By using this method, Windows PE files are not stored in a boot image. Instead, Windows PE files are stored in a flat file directory structure. Windows PE is booted directly from the flat file directory structure. If the flat file directory structure exists in a network location, Windows PE tries to load and then execute directly over the network. When this occurs, the files in the flat file directory structure are not copied to the client computer.

Back to the top

For more information about how to configure Windows PE 2.0 for download from a third-party PXE server, refer to the documentation that is included with the Windows OEM Preinstallation Kit (Windows OPK), or the documentation that is provided with Windows Automated Installation Kit (Windows AIK) for Windows Vista.For more information about the PXE client DHCP conversation, click the following article number to view the article in the Microsoft Knowledge Base:

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

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.

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

 

·         Hyper-V does not appear as installed role

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

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

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

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

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

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

To prevent this issue from occurring, follow these steps:

 

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

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

3.       Run upgrade. 

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

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

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

4.       Reinstall the Hyper-V update.

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

6.       Import your virtual machines.

 

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

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

2.       Reinstall the Hyper-V update.

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

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

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

 

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

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

 

 

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.

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 you try to use custom data types on the columns of data tables inside a data set with the DataSet Designer your project will not compile and you receive the following error:

 

Custom tool error: Failed to generate code. Unable to convert input xml file content to a DataSet. Column requires a valid DataType. Column requires a valid DataType.

The DataSet designer does not allow custom data types to be used on the columns of data tables inside the data set.

Do not use the local type in DataColumn.Type

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.

Consider the following scenario:

•	You connect a Windows Vista-based computer to a network.
•	A router or other device that is configured as a Dynamic Host Configuration Protocol (DHCP) server is configured on the network.
•	The router or the other device does not support the DHCP BROADCAST flag.

In this scenario, Windows Vista cannot obtain an IP address.

Back to the top

This issue occurs because of a difference in design between Windows Vista and Microsoft Windows XP Service Pack 2 (SP2). Specifically, in Windows XP SP2, the BROADCAST flag in DHCP discovery packets is set to 0 (disabled). In Windows Vista, the BROADCAST flag in DHCP discovery packets is not disabled. Therefore, some routers and some non-Microsoft DHCP servers cannot process the DHCP discovery packets.

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 resolve this issue, disable the DHCP BROADCAST flag in Windows Vista. To do this, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then click regedit in the Programs list. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Tcpip Parameters Interfaces {GUID} In this registry path, click the (GUID) subkey that corresponds to the network adapter that is connected to the network.
3.	On the Edit menu, point to New, and then click DWORD (32-bit) Value.
4.	In the New Value #1 box, type DhcpConnEnableBcastFlagToggle, and then press ENTER.
5.	Right-click DhcpConnEnableBcastFlagToggle, and then click Modify.
6.	In the Value data box, type 1, and then click OK.
7.	Close Registry Editor.

Back to the top

If the router or the non-Microsoft DHCP server does not support the DHCP BROADCAST flag, you can set the following registry entry as follows:

Note A data value of 0 disables this registry entry. You can use this registry entry to prevent Windows Vista from using the DHCP BROADCAST flag. After you set this registry entry, Windows Vista never uses the DHCP BROADCAST flag.

Back to the top

Microsoft has released security bulletin MS08-030. The security bulletin contains all the relevant information about the security update. This information includes deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites:

•	Home users: http://www.microsoft.com/protect/computer/updates/bulletins/200806.mspx (http://www.microsoft.com/protect/computer/updates/bulletins/200806.mspx) Skip the details: Download the updates for your home computer or laptop from the Microsoft Update Web site now: http://update.microsoft.com/microsoftupdate/ (http://update.microsoft.com/microsoftupdate/)
•	IT professionals: http://www.microsoft.com/technet/security/bulletin/ms08-030.mspx (http://www.microsoft.com/technet/security/bulletin/ms08-030.mspx)

Back to the top

How to obtain help and support for this security update

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

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

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

Back to the top

Information about the re-release version of security update 951376 for all supported 32-bit editions of Windows XP (June 19, 2008)

Microsoft Security Bulletin MS08-030 has been re-released to re-offer the security update to customers who are running a 32-bit edition of Windows XP Service Pack 2 (SP2) or Windows XP Service Pack 3 (SP3). The Windows XP SP2 and Windows XP SP3 update that was offered in the security bulletin did not fully address the vulnerability that was discussed in the security bulletin. All other versions of the security update provide protection against the issues that were discussed in the security bulletin.

The purpose of reissuing this bulletin is to provide the updated version of the security update that affects Windows XP SP2 and Windows XP SP3. Customers who are running Windows XP SP2 and Windows XP SP3 should download and deploy this new security update.

Customers who are running Windows XP Professional x64 Edition, Windows XP Professional x64 Edition Service Pack 2, and all supported versions of Windows Vista and who have already applied these original security updates do not have to take any additional action.

The updated versions of the affected security updates will be made available through the same distribution channels as the original security updates. These distribution channels include Automatic Updates, Windows Update, and Windows Server Update Services.

Back to the top

Known issues with this security update

•	This issue does not affect Windows Server 2008. However, it is possible to install this security update on a Windows Server 2008-based computer. There are no known issues that may occur if you install this security update on a computer that is running Windows Server 2008.

Back to the top

File information

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

For all supported x64-based editions of Windows Vista

File name	File version	File size	Date	Time	Platform
Amd64_bth.inf_31bf3856ad364e35_6.0.6000.16682_none_cc28a24d77072a10.manifest	Not Applicable	3,402	30-Apr-2008	00:04	Not Applicable
Amd64_bth.inf_31bf3856ad364e35_6.0.6000.20824_none_ccf5211a8ff25209.manifest	Not Applicable	3,402	30-Apr-2008	00:04	Not Applicable
Amd64_bth.inf_31bf3856ad364e35_6.0.6001.18064_none_ce26815f741bb5cd.manifest	Not Applicable	3,402	30-Apr-2008	00:04	Not Applicable
Amd64_bth.inf_31bf3856ad364e35_6.0.6001.22168_none_ceb41f528d35baf3.manifest	Not Applicable	3,402	30-Apr-2008	00:04	Not Applicable
Package_1_for_kb951376_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,941	29-Apr-2008	23:50	Not Applicable
Package_1_for_kb951376~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	2,674	29-Apr-2008	23:49	Not Applicable
Package_2_for_kb951376_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,781	29-Apr-2008	23:50	Not Applicable
Package_2_for_kb951376~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	2,510	29-Apr-2008	23:49	Not Applicable
Package_3_for_kb951376_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,781	29-Apr-2008	23:50	Not Applicable
Package_3_for_kb951376~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	2,510	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_client_0_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,423	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_client_0~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,442	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_client_1_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,365	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_client_1~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,384	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_client_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,699	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_client~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,732	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_server_0_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,423	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_server_0~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,442	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_server_bf~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,428	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_server~31bf3856ad364e35~amd64~~6.0.1.1.mum	Not Applicable	1,448	29-Apr-2008	23:49	Not Applicable
Update-bf.mum	Not Applicable	2,068	29-Apr-2008	23:50	Not Applicable
Bthenum.sys	6.0.6000.16682	23,040	29-Apr-2008	01:58	x64
Bthport.sys	6.0.6000.16682	276,480	29-Apr-2008	01:58	x64
Bthusb.sys	6.0.6000.16682	34,304	29-Apr-2008	01:58	x64
Fsquirt.exe	6.0.6000.16682	187,904	29-Apr-2008	04:00	x64
Bthenum.sys	6.0.6000.20824	23,040	29-Apr-2008	02:01	x64
Bthport.sys	6.0.6000.20824	276,480	29-Apr-2008	02:01	x64
Bthusb.sys	6.0.6000.20824	34,304	29-Apr-2008	02:01	x64
Fsquirt.exe	6.0.6000.20824	187,904	29-Apr-2008	02:01	x64
Bthenum.sys	6.0.6001.18000	23,040	19-Jan-2008	06:34	x64
Bthport.sys	6.0.6001.18064	276,480	29-Apr-2008	02:10	x64
Bthusb.sys	6.0.6001.18064	34,304	29-Apr-2008	02:10	x64
Fsquirt.exe	6.0.6001.18064	187,904	29-Apr-2008	04:16	x64
Bthenum.sys	6.0.6001.22168	23,040	29-Apr-2008	02:12	x64
Bthport.sys	6.0.6001.22168	276,480	29-Apr-2008	02:12	x64
Bthusb.sys	6.0.6001.22168	34,816	29-Apr-2008	02:12	x64
Fsquirt.exe	6.0.6001.22168	187,904	29-Apr-2008	02:12	x64

For all supported 32-bit editions of Windows Vista

File name	File version	File size	Date	Time	Platform
Package_1_for_kb951376_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,929	29-Apr-2008	23:50	Not Applicable
Package_1_for_kb951376~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	2,658	29-Apr-2008	23:49	Not Applicable
Package_2_for_kb951376_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,771	29-Apr-2008	23:50	Not Applicable
Package_2_for_kb951376~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	2,496	29-Apr-2008	23:49	Not Applicable
Package_3_for_kb951376_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,771	29-Apr-2008	23:50	Not Applicable
Package_3_for_kb951376~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	2,496	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_client_0_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,415	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_client_0~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,434	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_client_1_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,357	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_client_1~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,376	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_client_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,689	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_client~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,722	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_server_0_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,415	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_server_0~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,434	29-Apr-2008	23:49	Not Applicable
Package_for_kb951376_server_bf~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,420	29-Apr-2008	23:50	Not Applicable
Package_for_kb951376_server~31bf3856ad364e35~x86~~6.0.1.1.mum	Not Applicable	1,440	29-Apr-2008	23:49	Not Applicable
Update-bf.mum	Not Applicable	2,054	29-Apr-2008	23:50	Not Applicable
X86_bth.inf_31bf3856ad364e35_6.0.6000.16682_none_700a06c9bea9b8da.manifest	Not Applicable	3,400	30-Apr-2008	00:01	Not Applicable
X86_bth.inf_31bf3856ad364e35_6.0.6000.20824_none_70d68596d794e0d3.manifest	Not Applicable	3,400	30-Apr-2008	00:01	Not Applicable
X86_bth.inf_31bf3856ad364e35_6.0.6001.18064_none_7207e5dbbbbe4497.manifest	Not Applicable	3,400	30-Apr-2008	00:01	Not Applicable
X86_bth.inf_31bf3856ad364e35_6.0.6001.22168_none_729583ced4d849bd.manifest	Not Applicable	3,400	30-Apr-2008	00:01	Not Applicable
Bthenum.sys	6.0.6000.16682	19,456	29-Apr-2008	01:42	x86
Bthport.sys	6.0.6000.16682	220,160	29-Apr-2008	01:42	x86
Bthusb.sys	6.0.6000.16682	29,184	29-Apr-2008	01:42	x86
Fsquirt.exe	6.0.6000.16682	181,760	29-Apr-2008	03:50	x86
Bthenum.sys	6.0.6000.20824	19,456	29-Apr-2008	01:35	x86
Bthport.sys	6.0.6000.20824	220,160	29-Apr-2008	01:35	x86
Bthusb.sys	6.0.6000.20824	29,184	29-Apr-2008	01:35	x86
Fsquirt.exe	6.0.6000.20824	181,760	29-Apr-2008	01:35	x86
Bthenum.sys	6.0.6001.18000	19,456	19-Jan-2008	05:53	x86
Bthport.sys	6.0.6001.18064	220,160	29-Apr-2008	01:42	x86
Bthusb.sys	6.0.6001.18064	29,184	29-Apr-2008	01:42	x86
Fsquirt.exe	6.0.6001.18064	181,760	29-Apr-2008	03:54	x86
Bthenum.sys	6.0.6001.22168	19,456	29-Apr-2008	01:43	x86
Bthport.sys	6.0.6001.22168	220,160	29-Apr-2008	01:43	x86
Bthusb.sys	6.0.6001.22168	29,184	29-Apr-2008	01:43	x86
Fsquirt.exe	6.0.6001.22168	181,760	29-Apr-2008	01:43	x86

For all supported x64-based editions of Windows XP Professional

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Bthport.sys	5.2.3790.3122	320,512	09-May-2008	03:26	x64	SP1	SP1GDR
Bthport.sys	5.2.3790.3122	320,512	09-May-2008	03:26	x64	SP1	SP1QFE
Bthport.sys	5.2.3790.4274	320,512	09-May-2008	03:30	x64	SP2	SP2GDR
Bthport.sys	5.2.3790.4274	320,512	09-May-2008	03:26	x64	SP2	SP2QFE

For all supported 32-bit editions of Windows XP

File name	File version	File size	Date	Time	Platform	SP requirement	Service branch
Bthport.sys	5.1.2600.3389	272,128	13-Jun-2008	13:10	x86	SP2	SP2GDR
Bthport.sys	5.1.2600.3389	272,128	13-Jun-2008	09:52	x86	SP2	SP2QFE
Bthport.sys	5.1.2600.5620	272,128	13-Jun-2008	11:05	x86	SP3	SP3GDR
Bthport.sys	5.1.2600.5620	272,128	13-Jun-2008	11:27	x86	SP3	SP3QFE

Back to the top