Description of the Excel 2007 hotfix package (Excel.msp, Xlconv.msp, Graph.msp): April 30, 2009


This article describes the Microsoft Office Excel 2007 issues that are fixed in the hotfix package that is dated April 30, 2009.


Issues that this hotfix package fixes

  • You have an Excel workbook that contains defined names. The names may be silently removed during save.BUG #: 23862 (OfficeQFE)
  • You experience a performance problem when you try to set cell values by running a VBA macro in Excel 2007. It takes two to three times longer to run a macro that sets cell values in Excel 2007 than it takes to run the macro in Excel 2003. This depends on whether ScreenUpdating and AutoCalculation is enabled.BUG #: 23797 (OfficeQFE)
  • Consider the following scenario:
    • A Microsoft Office Excel 2003 workbook (.xls) has a cell that contains a long formula.

      Note The length of the formula is within the limit to correctly work and save in Excel 2003.
    • In Excel 2007, you open the Excel 2003 workbook and then try to save it in the Excel 97-2003 format.
    In this scenario, the compatibility checker reports that the cell uses more operands than you are able to in this file format, and the cell value is converted to the #VALUE! error.BUG #: 23809 (OfficeQFE)
  • After you change the data source of a chart in an Excel 2007 workbook, the data that is previously displayed on the horizontal axis of the chart is displayed on the vertical axis unexpectedly. BUG #: 23668 (OfficeQFE)
  • In the Japanese version of Excel, you change the font of a cell that has rich text in a workbook. If the initial characters in the rich text cannot be represented by the font that you are applying, formatting information for the cell may become corrupted. After that, if you save it as .xlsx file and then reopen the book in Excel 2007, you may receive the following error message:
    Excel found unreadable content '<file name>.xlsx'. Do you want to recover the contents of this workbook? If you trust source of this workbook, click Yes.
    BUG #: 23686 (OfficeQFE)
  • In Excel 2007, when you try to delete the rows by running a macro, you experience performance issues. The macro runs slower in Excel 2007 that it runs in Excel 2003.BUG #: 23562 (OfficeQFE)
  • In Excel 2007, when you run an application to return more than 256 columns from an Excel-link library (XLL), the #NUM! error value will be returned. BUG #: 24191 (OfficeQFE)
  • You copy a data range that contains hidden columns from an Excel 2007 workbook. Then, when you try to use the Paste Special command to paste the data range as formatted text (RTF) in a Word document, you receive the following error message:
    A table in this document has become corrupted.
    Finally, the data range is displayed incorrectly in the document.BUG #: 24201 (OfficeQFE)
  • Consider the following scenario:
    • An Excel 2007 workbook contains several shapes that are linked to macros in a .xla file. When you click a shape in the workbook, the macro will run.
    • The location of the .xla file is changed. In this case, you programmatically call the ChangeLinks method in the workbook to update the link to the .xla file.
    In this scenario, when you delete a shape and then try to save the changes to the workbook, Excel 2007 crashes.

    Note This problem occurs when the shapes are on any sheet other than the first sheet of the workbook.BUG #: 24011 (OfficeQFE)
  • Excel 2007 may crash when you try to use function wizard to call a VBA user-defined function recursively.BUG #: 23999 (OfficeQFE)
  • Excel 2007 may crash when the active sheet is a chart sheet and Dynamic Data Exchange (DDE) update performs on another sheet.BUG #: 23878 (OfficeQFE)
  • Consider the following scenario:
    • You run a Remote Desktop Protocol (RDP) session that is connected to a Windows Server 2003 or Windows Server 2008-based computer which has 2007 Office Suite SP1 installed.
    • In the RDP session, you create a document in Microsoft Office Word 2007.
    In this scenario, when you insert an Excel workbook that contains either a sharp or a chart into the Word document, the size of the document will be very large as 111 MB unexpectedly.BUG #: 23739 (OfficeQFE)
  • In Excel 2007, when you run the Compatibility Checker on a Pivot Table that contains a calculated field, you receive the following error message:
    A PivotTable in this workbook exceeds former limits and will be lost if it is saved to earlier file formats. Only PivotTables that are created in Compatibility Mode will work in earlier versions of Excel.
    BUG #: 23632 (OfficeQFE)
  • There is a custom application that uses Excel 2007 for the calculation. However, Excel 2007 crashes when you run this application.BUG #: 23865 (OfficeQFE)
  • In a Word 2007 document, you embed an Excel workbook that contains a Pivot Table as an OLE object. Then, you open the embeded workbook in Excel 2007 and perform an update to the Pivot Table. After that, when you try to open the data for the row of the Pivot Table, Excel 2007 crashes.BUG #: 24069 (OfficeQFE)
  • In a Microsoft Office PowerPoint presentation, you add an Excel Chart Object that is linked to a chart that is in an Excel 2007 worksheet. Then, you zoom in or out the display of the chart in Excel 2007. In this case, when you update the link to the chart in the presentation, the size of the Excel chart grows or shrinks unexpectedly in the presentation.BUG #: 24141 (OfficeQFE)
  • 970228 The text in a Graph object in a 2007 Office application is squeezed together on a Terminal Services client that is running in Monitor Spanning mode with a screen resolution of 2560 x 1024 pixels or higher

    BUG #: 23687 (OfficeQFE)
  • 968494 Description of the Excel 2007 hotfix package: March 9, 2009

    BUG #: 23915 (OfficeQFE)

More Information

Hotfix information

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

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

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


You must have 2007 Microsoft Office suite Service Pack 1 installed to apply this hotfix package.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949585 How to obtain the latest service pack for the 2007 Office suite

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File nameFile versionFile sizeDateTimePlatform

Microsoft Windows Installer .msp file information

File nameFile versionFile sizeDateTimePlatform
Excel.mspNot Applicable9,124,35204-May-200907:44Not Applicable
Graph.mspNot Applicable1,799,16804-May-200907:44Not Applicable
Xlconv.mspNot Applicable8,299,00804-May-200907:44Not Applicable

Excel.msp information
File nameFile versionFile sizeDateTimePlatform
Excel.exe.manifestNot applicable79103-May-200901:33Not applicable

Graph.msp information
File nameFile versionFile sizeDateTimePlatform

Xlconv.msp information
File nameFile versionFile sizeDateTimePlatform


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 968863 - Last Review: Jun 10, 2009 - Revision: 1