Back to the top

Back to the top

Back to the top

install.exe
install.res.1028.dll
install.res.1031.dll
install.res.1033.dll
install.res.1036.dll
install.res.1040.dll
install.res.1041.dll
install.res.1042.dll
install.res.2052.dll
install.res.3082.dll
vcredist.bmp
globdata.ini
install.ini
eula.1028.txt
eula.1031.txt
eula.1033.txt
eula.1036.txt
eula.1040.txt
eula.1041.txt
eula.1042.txt
eula.2052.txt
eula.3082.txt
vc_redist.msi
vc_redist.cab

Back to the top

Back to the top

Back to the top

Back to the top

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

Back to the top

If you have already deployed update 951072, read the descriptions of the specific time zone changes that are addressed in this article to determine whether you must deploy this update immediately. If systems are not directly affected, you can schedule deployment at the next available opportunity.

We recommend that you deploy the most current Windows cumulative time zone update to guarantee the consistency of the time zone database on all systems.

Important Before you apply the update that is described in this article, be aware of potential issues that may affect Microsoft Outlook.

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

Important

• If you are running Microsoft Exchange Server in an Information Technology (IT) environment, you must take additional measures to guarantee the correct operation of Exchange Server. For more information about the Exchange daylight saving time (DST) update, click the following article number to view the article in the Microsoft Knowledge Base:
  941018  (/Feedback.aspx?kbNumber=941018/ ) How to address daylight saving time by using the Exchange Calendar Update Tool
• Cumulative time zone updates contain only data that has changed for a specific region or that was added to maintain parity with other operating system versions. Therefore, if a time zone key has been deleted, some original values may not be restored after you apply the cumulative zone update.

  We do not recommend that you delete any registry keys that are related to time zones. On a computer that has incomplete time zone keys, first restore the time zone keys from a known good backup. Then, apply the update.

Back to the top

The update that this article describes is a cumulative update rollup that includes all the changes that were previously released in Microsoft Knowledge Base (KB) articles 928388, 929120, 933360, 942763 and 951072.

For more information about how DST changes may affect other Microsoft products, visit the following Microsoft Web site:

For more information about how daylight saving time changes may affect other Microsoft products, click the following article number to view the article in the Microsoft Knowledge Base:

Note When you apply this update, you may receive the following message:

This message indicates that you have already applied the correct update or that Windows Updates or Microsoft Update has automatically installed this update. No additional action is required to update the Windows operating system software.
Note The contents of this update are not included in Windows XP Service Pack 3 (SP3). However, you can apply the update that this article describes to Windows XP Service Pack 3 (SP3).
Note This update is not included in Windows XP SP3. If you apply this update to Windows XP SP2 and then upgrade to Windows XP SP3, you do not have to reapply this update. If you do not apply this update to Windows XP SP2 and then upgrade to Windows SP3, you must apply this update to Windows XP SP3.

Back to the top

Collapse this imageExpand this image

Download the Update for Windows Server 2003 (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=A8683CEC-6D69-4886-9FA7-E902797161E0)

Collapse this imageExpand this image

Download the Update for Windows Server 2003 for Itanium-based Systems (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=EE86700E-D484-4E91-B4B4-346CC396E850)

Collapse this imageExpand this image

Download the Update for Windows Server 2003 x64 Edition (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=F513778D-C698-4A1C-904B-3D50C0EDC3A3)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=7F2A1B29-F749-4F4E-B0A5-8D8504461B07)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 for Itanium-based Systems (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=B61D7862-C3E5-43BF-B300-5C469873DDD9)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 x64 Edition (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=8A82BD98-3E55-4164-9C90-E42540710DEB)

Collapse this imageExpand this image

Download the Update for Windows Vista (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=22F43320-8812-437D-BF66-B7F8DCBB51EF)

Collapse this imageExpand this image

Download the Update for Windows Vista for x64-based Systems (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=3FE36628-3B0D-479E-A892-F2D9CB5D4ECD)

Collapse this imageExpand this image

Download the Update for Windows XP (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=57A0E0A2-8E27-4DA1-B08D-DC008CC280BA)

Collapse this imageExpand this image

Download the Update for Windows XP x64 Edition (KB955839) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=D67870EE-420A-44C5-99A4-EF1852786F93)

Release Date: November 25, 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.

Back to the top

Updates from the previous cumulative Windows time zone update

The following changes were made since the previous Windows cumulative time zone update. This update was described in Microsoft Knowledge Base article 951072:

• Argentina Standard Time:

  Adjusts DST start dates and end dates for the Buenos Aires time zone for changes after the prior cumulative time zone update was created (August 2008).

• Egypt Standard Time:

  Adjusts the DST end dates for the Cairo time zone for changes after the prior cumulative time zone update was created (August 2008).

• Iran Standard Time:

  Introduces DST start dates and end dates for the Tehran time zone for changes after the prior cumulative time zone update was created (August 2008).

• Israel Standard Time:

  Adjusts the DST start and end dates for the Jerusalem time zone for changes after the prior cumulative time zone update was created (December 2007).

  Note Updates for the Jerusalem time zone are not included in the Windows Vista package for this update. The Jerusalem time zone updates were available in Windows Vista since Windows Vista was originally released.

• Mauritius Standard Time:

  Adds a new time zone for the Port Louis time zone which introduce DST start dates and ends dates for changes after the prior cumulative time zone update was created (August 2008).

• Morocco Standard Time:

  Adjusts the DST end dates for the Morocco time zone for changes after the prior cumulative time zone update was created (August 2008).

• Pacific SA Standard Time:

  Adjusts the DST end dates for the year 2009 for the Santiago time zone for changes after the prior cumulative time zone update was created (August 2008).

  Note Updates for the Pacific SA Standard Time are not included in the Windows Vista package for this update. The Santiago time zone update was available for Windows Vista in the prior time zone update (August 2008).

• Pakistan Standard Time:

  Adjusts the DST end date for the Islamabad / Karachi time zone for changes after the prior cumulative time zone update was created (August 2008).

• South America:
  E. South America Standard Time
  Central Brazilian Standard Time

  Adjusts the DST start dates and end dates for the Brasilia time zone and for the Manaus time zone for changes after the prior cumulative time zone update was created (August 2008).

Back to the top

Windows XP

Prerequisites

To apply this update, you must have Windows XP Service Pack 2 (SP2) or Windows XP Service Pack 3 (SP3) installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

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

Update replacement information

Note You can install this cumulative update rollup even after you have installed any of the following previously-released updates. This update replaces the following update:

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 XP with SP2, x86-based versions

If you apply this update to Windows XP SP2 and then upgrade to Windows XP SP3, the file version for Tzchange.exe after the upgrade is 5.1.2600.5512. This is the Tzchange.exe version from Windows XP SP3. This behavior is expected and does not affect the DST changes that this update applies. You do not have to reapply this update.

Note

• If you apply this update after you upgrade from Windows XP SP2 to Windows XP SP3, the file version for Tzchange.exe is 5.1.2600.5699.
• If you apply this update to Windows XP SP2 and then upgrade to Windows XP SP3, the file version for Tzchange.exe after the upgrade is 5.1.2600.5512. This is the Tzchange.exe version from Windows XP SP3. This behavior is expected and does not affect the DST changes that this update applies. You do not have to reapply this update.

Windows XP with SP3, x86-based versions

Back to the top

Windows Server 2003

Prerequisites

To apply this update, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 SP2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

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

Update replacement information

Note You can install this cumulative update rollup even after you have installed any of the following previously-released updates. This update replaces the following update:

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 Server 2003 with SP1, x86-based versions

Windows Server 2003 with SP2, x86-based versions

Windows Server 2003 with SP1, x64-based versions and Windows XP x64 Edition

Windows Server 2003 with SP2, x64-based versions and Windows XP x64 Edition with SP2

Windows Server 2003 with SP1, Itanium-based versions

Windows Server 2003 with SP2, Itanium-based versions

Back to the top

Windows Vista

Prerequisites

To apply this update, you must have Windows Vista Service Pack 1 (SP1) installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

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

Update replacement information

Note You can install this cumulative update rollup even after you have installed any of the following previously-released updates. This update replaces the following update:

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

Windows Vista and Windows Server 2008 file information note

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

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

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

For all supported Itanium-based versions of Windows Server 2008

Additional file information for Windows Server 2008 and Windows Vista

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

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

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

Back to the top

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

Back to the top

Back to the top

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

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

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

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

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

Back to the top

How to obtain help and support for this security update

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

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

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

Back to the top

Known issues with this security update

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

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

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

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

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

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

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

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

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

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

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

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

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

Back to the top

File information

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

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top

Files in the working directory do not have the read only attribute even though they are not checked out from Visual SourceSafe.

Several scenarios can cause this behavior:

1. You may have selected make writable option when getting files from SourceSafe.

2.  You may not have Tools> Options> Local Files tab  Use Read-only Flag for files not checked out selected.

3. You may be sharing a working directory with another user that does have the file checked out.

4. You may have intentionally uncheck the read only attribute in order to do testing on the file without checking the file out.

5. You may not have NTFS permissions to set the read only in the working directory. 

6. In the dialog Tools> Options> expand Source Control and choose Environment, you set the On Edit option to do nothing and you have checked the box in the same dialogue to Allow checked in items to be edited.

Back to the top

Make sure the user has full permissions to their working folder.

In VSS  Explorer:

Open the Tools> Options> Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

or

In Visual Studio:

 Go to Tools> Options> expand Source Control and choose Plug-in Settings.  Click on the advance button and select the Local Files tab and make sure the Use Read-only Flag for files not checked out option has a check mark in it.

In Visual Studio you have the option to be prompted when editing or to automatically check the file out.

In the dialog Tools> Options> expand Source Control and choose Environment.

Set the On Edit option to Prompt for Check out or Automatically check out depending on preference.

Move all the files from the working folder and re-issue the Get Latest (making sure you do not select make writable) and try to edit the file.

Back to the top

If you do a Get Latest, typically the files should be marked with a read only attribute.  However, sometimes the attribute is not set for some reason. Please review the cause section for most common reasons.

Sharing of working directories is not recommend because it can easily lead to the problem described in this article.

If you are editing directly from the SourceSafe Explorer

Open the Tools> Options> General tab and make sure that the Double-click on a file option is set to Ask.

You are prompted by a dialog that contains the following question in a option group:

Do you want to:

View SourceSafe’s copy of this file

Check out this file and edit it in your working folder.

Back to the top

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

Back to the top

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

Back to the top

Windows Vista helps business users significantly increase productivity by helping them find and use information, empower mobility and collaboration, improve security, and increase overall efficiency while keeping IT costs low.

This session will discuss and demonstrate how 2007 Microsoft Office System users can leverage Windows Vista features to achieve an even greater competitive advantage. Features in Word, Excel, PowerPoint, and the other Office programs can use the search, mobility, security, and efficiency of Windows Vista to get a lot more done, much faster, and more easily.

For example, we will see how the new Ribbon in the main Office programs can quickly harness the search capability of Windows Vista online. This helps bring vital data into Word and Excel documents. We will see how this information can then be easily shared with others on mobile devices or though online collaboration tools.

This is a Level 200 (http://support.microsoft.com/default.aspx?scid=gp;en-us;webcastlevels&sd=gn) session presented by Tom Bunzel.

Tom Bunzel specializes in knowing what presenters need and how to make technology work. He has appeared on Tech TV’s Call for Help, formerly as “Professor PowerPoint” and has been a featured speaker at InfoComm and PowerPoint LIVE. Tom also works as a “technology coach” for corporations, including the Neuroscience Education Institute. He teaches regularly at West LA College Extension and privately around Southern California.

Tom has written several books, the latest being Solving the PowerPoint Predicament: Using Digital Media for Effective Communication, Sams Teach Yourself PowerPoint 2003 in 24 Hours, and Easy Digital Music for QUE Publishing. Tom Bunzel’s other books are Easy Creating CDs and DVDs, How to Use Ulead DVD Workshop, Digital Video on the PC: Video Production on Your Multimedia PC, and the update to Peachpit Press’s PowerPoint 2002/2001 for Windows & Macintosh (Visual QuickStart Guide). He is Contributing Editor to “Presentations” magazine, and also writes a weekly column as the Office Reference Guide for InformIT.com.

He can be reached through his Web site http://www.professorppt.com/ (http://www.professorppt.com/).

Viewing the Presentation

To view, click this link: View this On-demand Recording (https://www118.livemeeting.com/cc/msevents/view?id=WV113006) (Length: 1 hour 9 minutes)

Provide Feedback on this Broadcast (http://support.microsoft.com/common/survey.aspx?scid=sw;en;1326&p0=WV&p1=en-us&p2=113006)

Support WebCasts Home (http://support.microsoft.com/webcasts)

Back to the top

Back to the top

Back to the top

Method 1

Add the following property to the connection string for the Oracle database.

Workaround Oracle Bug 914652=true

Back to the top

Method 2

Update the Oracle 8.x database to version 8.1.7.3.0 or to a later version. Or, update the Oracle 9.x database to version 9.0.1.3.0 or to a later version.

Back to the top

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:

You 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

Additional information about this security update

For more information about this security update and for information about any known issues with specific releases of this software, click the following article number to view the article in the Microsoft Knowledge Base:

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.

Microsoft Publisher 2000

Microsoft Publisher 2002

Microsoft Office Publisher 2003

Microsoft Office Publisher 2007

Back to the top

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

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

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

Back to the top

Detection and deployment

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

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

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

Windows Update

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

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

Microsoft Update

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

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

General exceptions

•	Microsoft Update does not support Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.

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

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

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

Office Update

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

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

General Exceptions

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

Mactopia

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

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

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

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

General Exceptions

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

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

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

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

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

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

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

General Exceptions

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

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

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

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

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

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

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

General Exceptions

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

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

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

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

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

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

Summary of detection and deployment guidance

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

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

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

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.0.1	WSUS 2.0 and WSUS 3.0	SMS SUS Feature Pack	SMS Inventory Tool for Microsoft Updates	System Center Configuration Manager 2007
			Detect and deploy	Detect and deploy	Detect and deploy	Detect only	Detect and deploy	Detect and deploy	Detect and deploy	Detect and deploy
949029	MS08-014	Microsoft Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949031	MS08-015	Microsoft Outlook	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949030	MS08-016	Office	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
933103	MS08-017	Microsoft Office Web Components	Partially. See Office Update section.	Not applicable	Partially. See Microsoft Update section.	Partially. See MBSA section.	Partially. See WSUS section.	Yes	Partially. See SMS section.	Partially. See System Center Configuration Manager section.

Rereleased security updates

There are no rereleases this month.

Back to the top

Frequently asked questions

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

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

What other information should I know about MBSA?

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

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

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

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

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

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

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

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

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

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

Back to the top

In some instances, a credential dialog box may appear in the Outlook user interface when you encounter this issue.

Back to the top

Note Windows Server 2003 and earlier versions of Microsoft Windows operating systems do not exhibit this behavior. The change of behavior in Windows Server 2008 is intended to protect domain controllers against clients that open too many NSPI connections without then closing the connections. Too many connections such as these can result in resource depletion.

Back to the top

Note The Outlook NSPI MAPI provider that is installed with Microsoft Outlook is only intended for use with Microsoft Outlook. External scripts and applications that rely on the Outlook NSPI MAPI provider are not supported.

How to modify the registry to allow for additional NSPI connections

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

If more concurrent NSPI connections per user are legitimately required, you can change the default limit. To do this, follow these steps:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate and then click the following registry key: HKEY_LOCAL_MACHINE System CurrentControlSet Services NTDS
3.	On the Edit menu, point to New, and then click Key.
4.	Type Parameters, and then press ENTER.
5.	Click the Parameters key.
6.	On the Edit menu, point to New, and then click DWORD Value.
7.	Type NSPI max sessions per user, and then press ENTER.
8.	Double-click NSPI max sessions per user, type the maximum number of the NSPI connections that you want to have, and then click OK.
9.	Exit Registry Editor.

Back to the top

To confirm that you encountered the issue that is described in the Symptoms section, follow these steps:

1.

Enable event logging for NSPI connections. To do this, follow these steps: a. On the domain controller that is targeted for the NspiBind connection, click Start, click Run, type regedit, and then click OK. b. Locate and then double-click the following registry entry: HKEY_LOCAL_MACHINE System CurrentControlSet Services NTDS Diagnostics 4 MAPI Interface Events c. In the Value data box, type 5, and then click OK. Note The default value of this registry entry is 0. d. On the File menu, click Exit. Note This is a verbose level of event logging and may generate many events. This verbose level of event logging includes events that are unrelated to the diagnosis of this issue. We recommend that you restore this setting to the default value after you finish troubleshooting.

2.

After you enable event logging, an event that resembles the following is logged in the Directory Services event log when this issue occurs: Event ID: 2820NSPI max connection limit for the user has reached.You need to do NSPI unbind on old connections before making new connections.Additional DataMax NSPI connections per user: %1User: %2

A network capture of the failure may contain packets that resemble the following:

Source	Destination	Protocol	Information
ClientIP	ServerIP	NSPI	NspiBind request
ServerIP	ClientIP	NSPI	NspiBind response, Status: MAPI_E_LOGON_FAILED

Back to the top

Back to the top

Back to the top

Back to the top

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

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

To do this, follow these steps:

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

Back to the top

Note The exact number of OABs that causes the problem depends on the server resources. For example, this problem may occur if there are more than 12,000 OABs. Typically, this problem occurs in a hosting environment.

Back to the top

Back to the top

Back to the top

Detection and deployment

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

Security updates that were released on June 12, 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, and 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 Server and Exchange Server 2003 • Microsoft Internet Security and Acceleration Server 2004 • Microsoft SQL Server 2005
•	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 June 12, 2007. Any exceptions are in the following list.

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

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

Note MBSA 2.0.1 is not supported on Windows Vista. However, MBSA 2.0.1 supports remote scans of computers that are running Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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

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

If you use SUS, WSUS 2.0, or WSUS 3.0 to detect and to deploy security updates, you can detect most security updates that were released on June 12, 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 927051 (security bulletin MS07-030) SUS does not support any part of this security update.
•	Security update 931213 (security bulletin MS07-032) 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 June 12, 2007. Any exceptions are in the following list.

Note SMS together with SUIT does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

•	Security update 931213 (security bulletin MS07-032) SMS SUIT does not support any part of this security update.
•	Security update 929123 (security bulletin MS07-034) 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

927051

MS07-030

Microsoft Visio

Yes

Not applicable

Yes

Yes

Yes

Not applicable

Yes

Not applicable

Yes

Yes

935840

MS07-031

Schannel

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

931213

MS07-032

Windows Vista

Not applicable

Yes

Yes

Not applicable

Yes

Not applicable

Yes

Not applicable

Not applicable

Yes

933566

MS07-033

Windows Internet Explorer

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

929123

MS07-034

Microsoft Outlook Express

Not applicable

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes, with ESUIT

Yes

935839

MS07-035

Win32 API

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

Back to the top

Rereleased security updates

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 June 13, 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 June 12, 2007.

Microsoft Knowledge Base article number	Bulletin ID	Component	Detection note
931213	MS07-032	Windows Vista	See the MBSA section
929123	MS07-034	Outlook Express	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
929123	MS07-034	Outlook Express

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, click the following article number to view the article 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. 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 Web site:

Back to the top

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

Back to the top

How to obtain the August 2008 cumulative update packages

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

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

Back to the top

Packages that are included in the August 2008 cumulative update

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

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

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

Back to the top

Prerequisites

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

Back to the top

You may experience this issue if the MN-700 device is configured to use only the 802.11g mode.

Note You may also experience this issue if you try to connect to the MN-700 device from a Microsoft Windows XP-based computer that has certain driver and firmware combinations.

For more information about how to configure wireless local area network (LAN) tracing in Windows Vista, see the More Information section.

Back to the top

Back to the top

For more information about how to configure the MN-700 device, see the support documentation that is included with the device. If you no longer have the Microsoft Broadband Networking CD, download the contents of the installation CD. To do this, visit the following Microsoft Web site:

Back to the top

To configure wireless LAN tracing in Windows Vista, follow these steps:

1.	Open an elevated Command Prompt window. To do this, click Start, type cmd in the Start Search box, right-click cmd in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or confirmation, type your password or click Continue.
2.	At the command prompt, type the following command, and then press ENTER: netsh wlan set tra yes Note If you want to enable persistent tracing to continue tracing after you restart the computer, type the following command instead: netsh wlan set tra persistent
3.	To disable wireless LAN tracing, type the following command, and then press ENTER: netsh wlan set tra no

After you enable wireless LAN tracing, the tracing log files are stored in the %WINDIR% tracing wireless folder.

Back to the top

Back to the top

Issue that the hotfix package fixes

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

Consider the following scenario. On a computer that has the East Asian languages enabled, you have a Microsoft Office Word 2003 document. The document contains numbers that are enclosed in parentheses. Some numbers are used to number a list. You open the document in Microsoft Office Word 2007. In this scenario, you may experience a delay of 1 second to 5 seconds after you type a character in the last line of the numbered list.

Note You do not experience a delay when you type successive characters.

Back to the top

Hotfix package information

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

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

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

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

Prerequisites

There are no prerequisites for installing this hotfix package.

Restart information

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

Hotfix package replacement information

This hotfix package does not replace a previously released hotfix package.

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

The global version of this hotfix package 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-kb953139-fullfile-x86-glb.exe	12.0.6300.5000	11,972,416	21-May-2008	16:27	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,243,392	21-May-2008	23:05	Not Applicable

Contents of Word.msp

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

In this scenario, the workflow displays the following message:

Back to the top

Note This metadata page problem is not exclusive to a picture library. This problem may also occur if you allow for management of content types on any other library, regardless of what content types are enabled. Additionally, adding certain columns to other library types, such as a document library, can cause this problem to occur.

When you click OK on the metadata entry page, the workflow sees this action as a change to the item. This unintended change to the item causes the workflow rule to cancel the workflow when the Cancel this workflow when the: Document is changed rule is enabled.

Back to the top

After you change these settings, a CheckIn button appears instead of an OK button on the metadata entry page when a picture item is uploaded. The CheckIn button does not cause the workflow to be canceled upon upload. This button still allows for successive change to the picture item to cancel the workflow as intended.

You can also work around this problem by clicking Cancel on the metadata page. By clicking Cancel, you receive the effect that you want on the workflow. However, this is not intuitive to the upload process and does not let the user add metadata during upload.

Another way to work around this problem is to click Upload or Upload Multiple Pictures. When you click one of these buttons, the metadata does not appear during the upload process.

Back to the top

Back to the top

In this scenario, when you open the PDF file or the XPS file, the text is right-aligned. Additionally, if a dash appears in the text, the text that appears before the dash is right-aligned. However, the text after the dash is left-aligned. Therefore, a large blank space appears in the text.

To resolve this problem, follow these steps:

1. Apply hotfix 956064.

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

   956064  (/Feedback.aspx?kbNumber=956064/ ) Description of the Word 2007 hotfix package (Word.msp): August 26, 2008
2. Set the value of the UseGlyphsForExport registry entry. To do this, follow these steps:
   1. Click Start, click Run, type regedit, and then click OK.
   2. Locate and then click the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Word Options
   3. On the Edit menu, point to New, and then click DWORD Value.
   4. Type UseGlyphsForExport, and then press ENTER.
   5. Right-click UseGlyphsForExport, and then click Modify.
   6. In the Value data box, type 1, and then click OK.
   7. Exit Registry Editor.

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

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

Back to the top