•	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 package.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

Back to the top

Issues that the hotfix package fixes

List of issues that are fixed

This hotfix fixes the following issues:

•	954540 (/Feedback.aspx?kbNumber=954540/) The changes in the TOC and PageRef fields do not appear when you compare Word 2007 documents
•	954541 (/Feedback.aspx?kbNumber=954541/) The Ref field is updated incorrectly when you print a Word 2007 document

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	When you compare and merge documents that are written in Chinese characters or in Japanese characters in Word 2007, the text that is marked as deleted and inserted is much larger than the text that is actually changed. For example, if you delete only one character or one word, a large chunk of text around this character or word is marked as deleted. Additionally, the chunk of text is marked as reinserted, except for the character or for the word that is actually deleted. Note The issue occurs for both character-level comparison and word-level comparison. However, this issue does not occur if you delete the word or the character at the end of the sentence.
•	Consider the following scenario. You create and then save a new document from a template on a trusted network share. This template contains Microsoft Visual Basic for Application (VBA) code. Then, you open the document again. In this scenario, you cannot save the document again. Additionally, you receive the following error message: The save failed due to out of memory or disk space.
•	Consider the following scenario. You create and then save a document that contains a table. You delete one row, and you modify the content in the following row. Then, you save the document as a different name. In this scenario, if you compare the revised document to the original document, the result is incorrect.
•	Consider the following scenario. You create a Microsoft Office Word 2003 document, and you apply a new style such as Style1 to some paragraphs that have outline numbering enabled. Then, you change the number format of Style1. To change this number format, you add text before the number in that document. In this scenario, when you use the Compare Documents functionality to compare the revised document to the original document, the comparison document shows the formatting as the formatting in the original document. However, the comparison document should show the formatting as the formatting in the revised document.
•	You create a document that is based on a template that has customized Ribbons. When you open the document, Word 2007 may not display the Ribbon customizations. This issue can occur if the following conditions are true: • The template uses the editing restriction, Filling in forms. Note This issue does not occur if the template is unprotected or if the template uses one of the following editing restrictions: • Comments • No changes (Read only) • Tracked changes • The document is saved in one of the following file formats: • Word 2003 XML Document (*.xml) • Word XML Document (*.xml) • Word Document (*.docx) • Word Macro-Enabled Document (*.docm) Note This issue does not occur if the document is saved in a rich text format (RTF) or in a binary document file format. However, the template is still correctly loaded as a base template.
•	When you add one or more letters at the beginning or at the end of a word, a word-level comparison only marks the inserted letters as an insertion, as if the inserted characters are a separate word. The expected behavior is that the original word should be marked as deleted, and the new word should be marked as an insertion.
•	If you click to clear the White space check box in the Compare Documents dialog box, the closing paragraph mark of an insertion is ignored. The expected behavior is that the closing paragraph mark should be displayed as part of the insertion, and the closing paragraph mark should not be ignored.
•	When you insert or delete a text box in the revised document, and then you compare this document to the original document, there is a revision bar next to the border of the text box. However, there is no revision markup in the text box.
•	If two plain text content controls are grouped, you may experience the following issues when you run the Spelling and Grammar check: • The last word in the first content control is selected together with part of the first word of the second content control. This behavior occurs when the following conditions are true: • There is no space after the last word in the first content control. • The last word of the first content control is proofed in the Spelling and Grammar dialog box. This issue occurs whether the last word of the first content control is spelled correctly. • After the last word of the first content control is proofed, the Spelling and Grammar check is complete. However, misspelled words are not checked in the second content control.

Back to the top

Hotfix information

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

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

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

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

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

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

Hotfix replacement information

This hotfix package does not replace any other hotfix packages.

Registry information

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 uses a Microsoft Windows Installer package to install the hotfix. 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 name	File version	File size	Date	Time	Platform
Office-kb954576-fullfile-x86-glb.exe	12.0.6320.5000	15,929,040	19-Jun-2008	14:28	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,252,608	19-Jun-2008	18:33	Not Applicable
Wordconv.msp	Not Applicable	6,301,696	19-Jun-2008	18:33	Not Applicable

Word.msp file information

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	06-Dec-2007	17:05	Not Applicable
Winword.exe	12.0.6320.5000	349,720	19-Jun-2008	15:00	x86
Wwlib.dll	12.0.6320.5000	17,491,480	19-Jun-2008	15:00	x86

Wordconv.msp file information

File name	File version	File size	Date	Time	Platform
Wordcnv.dll	12.0.6320.5000	4,281,368	19-Jun-2008	22:42	x86
Wordconv.exe	12.0.6300.5000	24,584	13-Dec-2007	01:08	x86

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

After you apply hotfix 955572, you may receive an error message when you open an appointment in a shared calendar:

This issue may occur if the following conditions are true:

• You are the delegate in a delegate and manager scenario.
• You enable caching of shared folders.

  For more information about how to enable caching of shared folders, click the following article number to view the article in the Microsoft Knowledge Base:

  955572  (/Feedback.aspx?kbNumber=955572/ ) You cannot cache shared mail folders in Outlook 2007

To resolve this issue, apply hotfix 957692. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

On a Windows Vista-based client computer, you try to open a Microsoft Office document from a Web site hyperlink in a 2007 Microsoft Office application. When you do this, you may experience the following symptoms:

•	Performance is slow, or the 2007 Office application may stop responding for several minutes.
•	You are prompted for authentication even though you previously entered your credentials.
•	You lose session state. Then, you are redirected to a logon page or to an error page on the Web site.
•	The document is downloaded two times. When the files are large, the download process consumes more network bandwidth.

Note These problems do not occur when you try to open the document on a Windows XP-based computer or on a Windows Server 2003-based computer.

Back to the top

This problem occurs because, on a Windows Vista-based client computer, 2007 Office applications use the Windows WebDAV Mini-Redirector Client component to open URL-based files. This component provides read/write permissions to DAV-based Web servers that support Web authoring.

When you try to open a document from a hyperlink, 2007 Office applications may request that the Windows WebDAV Client try to author the document at the URL location. However, if the authoring attempt is not expected on certain Web servers or in certain situations, the symptoms that are mentioned in the Symptoms section may occur.

Back to the top

To resolve this problem, follow these steps.

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

1.

Apply hotfix 954573. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base: 954573 (/Feedback.aspx?kbNumber=954573/) Description of the 2007 Office system hotfix package: June 26, 2008

2.

Enable the hotfix by configuring the UseWinINETCopy registry entry. To do this, follow these steps: a. Click Start, click Run, type regedit, and then click OK. b. Locate and then click the following registry subkey: HKEY_CURRENT_USER SOFTWARE Microsoft Office 12.0 Common Internet c. On the Edit menu, point to New, and then click DWORD Value. d. Type UseWinINETCopy, and then press ENTER. e. Right-click UseWinINETCopy, and then click Modify. f. In the Value data box, type 1, and then click OK. g. Exit Registry Editor.

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 Web folders issues that are fixed in the Software Update for Web Folders that is dated May 18, 2007.

•	The issues that the update fixes.
•	The prerequisites for installing the update.
•	Whether you must restart the computer after you install the update.
•	Whether the update is replaced by any other update.
•	Whether you must make any registry changes.
•	The files that the update contains.

Back to the top

List of issues fixed

This update fixes various issues that may occur when you use Web folders from the client computer to connect to a server that supports Web Distributed Authoring and Versioning (WebDAV).

This update fixes the following issues:

•	A document that is opened from a Microsoft Office SharePoint Server 2007site may be downloaded two times when you click Edit in Microsoft Office program.
•	The download progress indicator does not work for some documents on the SharePoint site.
•	You cannot rename or copy files that have a display name in a non-Internet Information Services (IIS) Web folder.

Additionally, this update includes security enhancements to Web folders.

Back to the top

Update information

The following file is available for download from the Microsoft Download Center:
Download the Software Update for Web Folders package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=17C36612-632E-4C04-9382-987622ED1D64)

Release Date: May 18, 2007

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

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

Restart information

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

Update replacement information

This update replaces the Software Update for Web Folders that is dated January 25, 2005.

For more information about the Software Update for Web Folders that is dated January 25, 2005, click the following article number to view the article in the Microsoft Knowledge Base:

File information

After the update is installed, the English version of this update has the file attributes, or a later version of the file attributes, that are listed in the following table:

File name	File version	File size	Date	Time
Fp4autl.dll	4.0.2.3216	589,880	17-Nov-2004	22:33
Fp4awec.dll	4.0.2.2611	450,669	17-Nov-2004	22:33
Fpext_fp4.msg	Not Applicable	78,706	17-Nov-2004	22:33
Msdaipp.dll	12.0.4518.1014	1,011,488	27-Oct-2006	00:49
Msdapml.dll	12.0.4518.1014	163,104	27-Oct-2006	00:49
Msonsext.dll	12.0.4518.1014	970,528	27-Oct-2006	00:49
Nsextint.dll	12.0.4518.1014	75,552	27-Oct-2006	00:49

Additional notes

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

You update some page values in a Microsoft Office Word 2007 document. When you compare the revised document to the original document, the changes in the TOC and PageRef fields do not appear.

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, follow these steps:

1.

Install hotfix 954576.For more information, click the following article number to view the article in the Microsoft Knowledge Base: 954576 (/Feedback.aspx?kbNumber=954576/) Description of the Word 2007 hotfix package: June 20, 2008

2.

Set the CompDiffSupressPageRefOnlyInHdr registry entry. To do this, follow these steps: a. Click Start, click Run, type regedit, and then click OK. b. Locate and then click the following registry subkey: HKEY_CURRENT_USER Software Microsoft Office 12.0 Word Options c. On the Edit menu, point to New, and then click DWORD Value. d. Type CompDiffSupressPageRefOnlyInHdr, and then press ENTER. e. Right-click CompDiffSupressPageRefOnlyInHdr, and then click Modify. f. In the Value data box, type 1, and then click OK. g. Exit Registry Editor.

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

Security update replacement information

This security update replaces the following security update:

File Information

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

32-bit editions

64-bit editions

Currently, the 2007 Microsoft Office system supports only forms-based authentication (FBA) through persistent cookies, such as the authentication cookies that are written to disk. Office does not support the acquisition of session cookies from a process in Internet Explorer 7.

However, in Windows Server 2008 Service Pack 2 (SP2) and in Windows Vista Service Pack 2 (SP2), the 2007 Microsoft Office system supports authenticating against FBA sites. Specifically, when you receive a particular response from the Web site, the 2007 Microsoft Office system now creates a Trident window that you can use to sign in to the Web site. The 2007 Microsoft Office system obtains cookies from that session, and you can access the content in the Web site.

To resolve this issue, obtain Windows Server 2008 SP2 or Windows Vista SP2 Release Candidate (RC). To obtain these programs, visit the following Microsoft Web site:

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

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

Back to the top

List of issues that this hotfix package fixes

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

•	You install 2007 Microsoft Office servers Service Pack 1 (SP1) on a computer that is running the release version of Microsoft Office SharePoint Server 2007. However, all DCOM permissions for the WSS_ADMIN_WPG security group and for the WSS_WPG security group are removed from the OSearch DCOM application. Additionally, if the Office SharePoint Server service is running under an account that is not in the Administrators group, the search function will not work. Note To work around this issue, manually add DCOM permissions for the WSS_ADMIN_WPG security group and for the WSS_WPG security group. To do this, follow these steps: 1. Click Start, click Run, type dcomcnfg, and then press ENTER. 2. Expand Component Services, expand Computers, expand My Computer, and then click DCOM Config. 3. In the details pane, right-click OSearch, and then click Properties. 4. Click the Security tab. 5. Under Launch and Activation Permissions, click Customize, and then click Edit. 6. Click Add to add the local WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them Local Launch and Local Activation permissions, and then click OK. 7. Under Access Permissions, click Customize, and then click Edit. 8. Click Add to add the local WSS_ADMIN_WPG security group and the local WSS_WPG security group, grant them Local Access Activation permission, and then click OK two times. 9. Restart the computer.
•	After you perform a crawl on a computer that is running Microsoft Office SharePoint Server 2007, you may receive an error message that resembles the following in the crawl log: Filtering of this file ended because the file reached the maximum filter output limit. Check that the filter does not generate a large amount of data relative to the size of the document. 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: 322756 (/Feedback.aspx?kbNumber=322756/) How to back up and restore the registry in Windows Note To work around this issue, follow these steps: 1. Click Start, click Run, type regedit, and then press ENTER. 2. Locate the following registry subkey: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Office Server 12.0 Search Global Gathering Manager MaxGrowFactor 3. Double-click MaxGrowFactor, type 4096, click to select Decimal, and then click OK. 4. Exit Registry Editor.
•	You perform an incremental crawl on a computer that is running Microsoft Office SharePoint Server 2007. However, any documents in a meeting workplace template document library are not crawled. Note To work around this issue, perform a full crawl.
•	Consider the following scenario: • You create a Calendar list on a computer that is running Microsoft Office SharePoint Server 2007. • You use Microsoft Office SharePoint Designer 2007 to use a Display item form to display items in the Calendar list in a custom .aspx page. • You create a series of repeating calendar items. When you try to edit one of the repeating calendar items on the custom .aspx page, the first calendar item in the series opens instead of the calendar item that you selected. Note To work around this issue, edit the calendar item in the All Events view of the Calendar list.

Back to the top

Known issue of the hotfix package

•

Symptoms Consider the following scenario. You add a custom list as a Web Part on the home page of a SharePoint site. When you try to edit the current view of the custom list by clicking Edit the current view, the Create View page opens. However, you expect the Edit View page for this custom list to open. Workaround To work around this issue, edit the list view before you add the custom list as a Web Part on the home page of the SharePoint site. To do this, follow these steps: 1. Remove the Web Part that contains the custom list from the home page. 2. Open the custom list, click Modify this View. 3. On the Edit View page, make any changes that you want, and then click OK. 4. Add the custom list back as a Web Part on the home page.

Back to the top

Hotfix information

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

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

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

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

Prerequisites

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

This hotfix package is not replaced by any later 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.

32-bit hotfix package

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 name	File version	File size	Date	Time	Platform
Wss-kb953137-fullfile-x86-glb.exe	12.0.6300.5000	23,351,296	21-May-2008	16:31	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Sts.msp	Not Applicable	23,581,184	21-May-2008	22:18	Not Applicable

After the hotfix package is installed, the global version of this hotfix package has the file attributes, or a later version of the file attributes, that are listed in the following table:

File name	File version	Flie size	Date	Time	Platform
Atl80.dll	8.0.50727.762	96,256	6-Dec-2007	09:22	Not applicable
Atl80.dll	8.0.50727.762	114,688	6-Dec-2007	09:22	Not applicable
Dbghelp.dll	6.6.7.5	1,030,144	20-Feb-2007	20:14	x86
Dwdcw20.dll	12.0.6300.5000	441,864	6-Dec-2007	17:41	x86
Mfc80.dll	8.0.50727.762	1,101,824	6-Dec-2007	09:22	Not applicable
Mfc80chs.dll	8.0.50727.762	40,960	6-Dec-2007	09:22	Not applicable
Mfc80cht.dll	8.0.50727.762	45,056	6-Dec-2007	09:22	Not applicable
Mfc80deu.dll	8.0.50727.762	65,536	6-Dec-2007	09:22	Not applicable
Mfc80enu.dll	8.0.50727.762	57,344	6-Dec-2007	09:22	Not applicable
Mfc80esp.dll	8.0.50727.762	61,440	6-Dec-2007	09:22	Not applicable
Mfc80fra.dll	8.0.50727.762	61,440	6-Dec-2007	09:22	Not applicable
Mfc80ita.dll	8.0.50727.762	61,440	6-Dec-2007	09:22	Not applicable
Mfc80jpn.dll	8.0.50727.762	49,152	6-Dec-2007	09:22	Not applicable
Mfc80kor.dll	8.0.50727.762	49,152	6-Dec-2007	09:22	Not applicable
Mfc80u.dll	8.0.50727.762	1,093,120	6-Dec-2007	09:22	Not applicable
Mfcm80.dll	8.0.50727.762	69,632	6-Dec-2007	09:22	Not applicable
Mfcm80u.dll	8.0.50727.762	57,856	6-Dec-2007	09:22	Not applicable
Microsoft.sharepoint.administrationoperation.dll	12.0.6313.5000	472,104	23-Apr-2008	14:26	Not applicable
Microsoft.sharepoint.applicationpages.administration.dll	12.0.6300.5000	271,400	13-Dec-2007	20:55	x86
Microsoft.sharepoint.applicationpages.dll	12.0.6315.5000	627,784	8-May-2008	12:24	x86
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:39	Not applicable
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:39	x86
Microsoft.sharepoint.intl.dll	12.0.6300.5000	463,912	13-Dec-2007	20:55	x86
Microsoft.sharepoint.library.dll	12.0.6300.5000	132,136	13-Dec-2007	20:55	Not applicable
Microsoft.sharepoint.search.dll	12.0.6315.5000	1,433,648	6-May-2008	15:51	Not applicable
Microsoft.sharepoint.search.intl.dll	12.0.6309.5000	193,632	25-Mar-2008	14:07	Not applicable
Microsoft.sharepoint.setupconfiguration.intl.dll	12.0.6300.5000	2,081,832	13-Dec-2007	20:55	x86
Microsoft.sharepoint.workflowactions.dll	12.0.6300.5000	197,704	13-Dec-2007	20:55	x86
Msscntrs.dll	12.0.6300.5000	91,656	13-Dec-2007	20:56	Not applicable
Mssdmn.exe	12.0.6309.5000	282,144	25-Mar-2008	14:07	Not applicable
Mssearch.exe	12.0.6309.5000	159,304	25-Mar-2008	14:07	Not applicable
Mssph.dll	12.0.6316.5000	695,808	20-May-2008	15:57	Not applicable
Mssrch.dll	12.0.6309.5000	2,059,776	25-Mar-2008	14:07	Not applicable
Msvcm80.dll	8.0.50727.762	479,232	6-Dec-2007	09:22	Not applicable
Msvcp80.dll	8.0.50727.762	548,864	6-Dec-2007	09:22	Not applicable
Msvcr80.dll	8.0.50727.762	626,688	6-Dec-2007	09:22	Not applicable
Nlhtml.dll	2006.1206.6300.5000	126,488	12-Dec-2007	17:26	Not applicable
Offfilt.dll	2006.1206.6300.5000	202,784	12-Dec-2007	17:26	Not applicable
Offparser.dll	12.0.6314.5000	1,078,856	29-Apr-2008	14:05	x86
Oisimg.dll	12.0.6300.5000	26,152	13-Dec-2007	20:55	x86
Onetnative.dll	12.0.6300.5000	356,920	6-Dec-2007	13:43	x86
Onetutil.dll	12.0.6316.5000	1,983,528	20-May-2008	16:19	x86
Owssvr.dll	12.0.6316.5000	3,014,696	15-May-2008	15:39	Not applicable
Owstimer.exe	12.0.6315.5000	57,888	8-May-2008	12:24	Not applicable
Prescan.exe	12.0.6300.5000	103,424	13-Dec-2007	20:55	x86
Psconfig.exe	12.0.6300.5000	578,664	13-Dec-2007	20:55	x86
Psconfigui.exe	12.0.6300.5000	824,424	13-Dec-2007	20:55	x86
Query.dll	12.0.6300.5000	84,480	13-Dec-2007	20:56	Not applicable
Setup.exe	12.0.6309.5000	442,408	27-Mar-2008	12:21	x86
Sigconfigdb.dll	Not Applicable	11,280	13-Mar-2008	09:16	x86
Sigsearchdb.dll	Not Applicable	11,280	6-May-2008	15:51	Not applicable
Sigstore.dll	Not Applicable	11,272	8-May-2008	12:24	x86
Spwriter.exe	12.0.6300.5000	37,928	13-Dec-2007	20:55	Not applicable
Stsadm.exe	12.0.6300.5000	525,392	13-Dec-2007	20:55	x86
Stsmmc.dll	12.0.6300.5000	99,896	13-Dec-2007	20:55	x86
Stssoap.dll	12.0.6316.5000	312,360	15-May-2008	15:39	x86
Stswel.dll	12.0.6316.5000	1,930,792	15-May-2008	15:39	x86
Tquery.dll	12.0.6315.5000	2,336,768	6-May-2008	15:51	Not applicable
Wrapinst.exe	12.0.6300.5000	54,312	13-Dec-2007	20:55	x86
Wsssetup.dll	12.0.6309.5000	6,786,584	27-Mar-2008	12:21	x86
Wsstracing.exe	12.0.6300.5000	48,680	13-Dec-2007	20:55	x86
Xmlfilter.dll	2006.1206.6300.5000	105,496	12-Dec-2007	17:26	Not applicable

64-bit hotfix package

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 name	File version	File size	Date	Time	Platform
Wss-kb953137-fullfile-x64-glb.exe	12.0.6300.5000	26,564,392	21-May-2008	16:31	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Sts.msp	Not Applicable	26,820,608	21-May-2008	22:18	Not Applicable

After the hotfix package is installed, the global version of this hotfix package has the file attributes, or a later version of the file attributes, that are listed in the following table:

File name	File version	Flie size	Date	Time	Platform
Atl80.dll	8.0.50727.762	113,152	6-Dec-2007	09:22	Not applicable
Dbghelp.dll	6.6.7.5	1,319,936	20-Feb-2007	20:14	x64
Dwdcw20.dll	12.0.6300.5000	1,092,616	6-Dec-2007	13:48	x64
Mfc80.dll	8.0.50727.762	1,656,320	6-Dec-2007	09:22	Not applicable
Mfc80chs.dll	8.0.50727.762	33,280	6-Dec-2007	09:22	Not applicable
Mfc80cht.dll	8.0.50727.762	33,792	6-Dec-2007	09:22	Not applicable
Mfc80deu.dll	8.0.50727.762	54,272	6-Dec-2007	09:22	Not applicable
Mfc80enu.dll	8.0.50727.762	47,104	6-Dec-2007	09:22	Not applicable
Mfc80esp.dll	8.0.50727.762	51,712	6-Dec-2007	09:22	Not applicable
Mfc80fra.dll	8.0.50727.762	52,736	6-Dec-2007	09:22	Not applicable
Mfc80ita.dll	8.0.50727.762	52,224	6-Dec-2007	09:22	Not applicable
Mfc80jpn.dll	8.0.50727.762	38,912	6-Dec-2007	09:22	Not applicable
Mfc80kor.dll	8.0.50727.762	38,400	6-Dec-2007	09:22	Not applicable
Mfc80u.dll	8.0.50727.762	1,652,736	6-Dec-2007	09:22	Not applicable
Mfcm80.dll	8.0.50727.762	65,536	6-Dec-2007	09:22	Not applicable
Mfcm80u.dll	8.0.50727.762	64,000	6-Dec-2007	09:22	Not applicable
Microsoft.sharepoint.administrationoperation.dll	12.0.6313.5000	472,104	23-Apr-2008	14:18	Not applicable
Microsoft.sharepoint.applicationpages.administration.dll	12.0.6300.5000	271,400	13-Dec-2007	20:30	x86
Microsoft.sharepoint.applicationpages.dll	12.0.6315.5000	627,784	8-May-2008	12:10	x86
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:19	Not applicable
Microsoft.sharepoint.dll	12.0.6316.5000	9,339,944	15-May-2008	15:19	x86
Microsoft.sharepoint.intl.dll	12.0.6300.5000	463,912	13-Dec-2007	20:30	x86
Microsoft.sharepoint.library.dll	12.0.6300.5000	132,136	13-Dec-2007	20:30	Not applicable
Microsoft.sharepoint.search.dll	12.0.6315.5000	1,534,512	6-May-2008	15:57	Not applicable
Microsoft.sharepoint.search.intl.dll	12.0.6309.5000	193,632	25-Mar-2008	13:59	Not applicable
Microsoft.sharepoint.setupconfiguration.intl.dll	12.0.6300.5000	2,081,832	13-Dec-2007	20:30	x86
Microsoft.sharepoint.workflowactions.dll	12.0.6300.5000	197,704	13-Dec-2007	20:30	x86
Msscntrs.dll	12.0.6300.5000	438,280	13-Dec-2007	20:48	Not applicable
Mssdmn.exe	12.0.6309.5000	797,216	25-Mar-2008	13:59	Not applicable
Mssearch.exe	12.0.6309.5000	574,024	25-Mar-2008	13:59	Not applicable
Mssph.dll	12.0.6316.5000	1,938,944	15-May-2008	15:52	Not applicable
Mssrch.dll	12.0.6309.5000	4,743,680	25-Mar-2008	13:59	Not applicable
Msvcm80.dll	8.0.50727.762	516,096	6-Dec-2007	09:22	Not applicable
Msvcp80.dll	8.0.50727.762	1,061,376	6-Dec-2007	09:22	Not applicable
Msvcr80.dll	8.0.50727.762	796,672	6-Dec-2007	09:22	Not applicable
Nlhtml.dll	2006.1206.6300.5000	231,448	6-Dec-2007	10:35	Not applicable
Offfilt.dll	2006.1206.6300.5000	392,224	6-Dec-2007	10:35	Not applicable
Offparser.dll	12.0.6314.5000	1,670,728	29-Apr-2008	13:49	x64
Oisimg.dll	12.0.6300.5000	37,928	13-Dec-2007	20:30	x64
Onetnative.dll	12.0.6300.5000	954,936	6-Dec-2007	13:41	x64
Onetutil.dll	12.0.6316.5000	3,388,456	15-May-2008	14:42	x64
Owssvr.dll	12.0.6316.5000	5,138,984	15-May-2008	15:19	Not applicable
Owstimer.exe	12.0.6315.5000	92,704	8-May-2008	12:10	Not applicable
Prescan.exe	12.0.6300.5000	103,424	13-Dec-2007	20:30	x86
Psconfig.exe	12.0.6300.5000	578,664	13-Dec-2007	20:30	x86
Psconfigui.exe	12.0.6300.5000	824,424	13-Dec-2007	20:30	x86
Query.dll	12.0.6300.5000	223,232	13-Dec-2007	20:48	Not applicable
Setup.exe	12.0.6309.5000	442,408	27-Mar-2008	12:21	x86
Sigconfigdb.dll	Not Applicable	11,280	13-Mar-2008	09:16	x86
Sigsearchdb.dll	Not Applicable	11,280	6-May-2008	15:51	Not applicable
Sigstore.dll	Not Applicable	11,272	8-May-2008	12:24	x86
Spwriter.exe	12.0.6300.5000	59,432	13-Dec-2007	20:30	Not applicable
Stsadm.exe	12.0.6300.5000	525,392	13-Dec-2007	20:30	x86
Stsmmc.dll	12.0.6300.5000	163,896	13-Dec-2007	20:30	x64
Stssoap.dll	12.0.6316.5000	312,360	15-May-2008	15:19	x86
Stswel.dll	12.0.6316.5000	3,317,288	15-May-2008	15:19	x64
Tquery.dll	12.0.6315.5000	4,746,752	6-May-2008	15:57	Not applicable
Wrapinst.exe	12.0.6300.5000	54,312	13-Dec-2007	20:30	x86
Wsssetup.dll	12.0.6309.5000	6,786,584	27-Mar-2008	12:21	x86
Wsstracing.exe	12.0.6300.5000	87,592	13-Dec-2007	20:30	x64
Xmlfilter.dll	2006.1206.6300.5000	207,384	6-Dec-2007	10:35	Not applicable

Back to the top

Back to the top

List of issues that the hotfix package fixes

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	You paste a range of cells from Excel into a text box in Word 2007 and then click Keep Source Formatting and Link to Excel. You right-click in a cell of the pasted table, point to Linked Worksheet Object, and then click Links. You click Preserve formatting after update and then click Manual update. When you right-click in a cell of the pasted table, click Update Link, and then click the Undo button, duplicate tables may appear in the text box.
•	You set the default font and style in Outlook 2007. To do this, you click All caps or Bold in the Font style list. After you restart Outlook 2007, the default font and style settings are lost.
•	You add the Header Position from Top command, the Footer Position from Bottom command, or both to the Quick Access Toolbar (QAT) in Word 2007. When you add a table to a new document, and you type text in a cell of the table, the whole table row flashes between white and the text highlight color. Note You can see the typed text clearly when you click other cells.

Back to the top

Hotfix information

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

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

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

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

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

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 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-kb953924-fullfile-x86-glb.exe	12.0.6300.5000	15,860,320	05-Jun-2008	09:25	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,234,176	05-Jun-2008	14:01	Not Applicable
Wordconv.msp	Not Applicable	6,219,776	05-Jun-2008	14:01	Not Applicable

Contents of Word.msp

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	07-Dec-2007	01:05	x86
Winword.exe	12.0.6318.5000	349,720	05-Jun-2008	17:04	x86
Wwlib.dll	12.0.6318.5000	17,494,552	05-Jun-2008	17:04	x86

Contents of Wordconv.msp

File name	File version	File size	Date	Time	Platform
Wordcnv.dll	12.0.6318.5000	4,280,856	05-Jun-2008	17:02	x86
Wordconv.exe	12.0.6300.5000	24,584	13-Dec-2007	01:08	x86

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

This article describes the Microsoft Office Project 2007 issue that is fixed in the hotfix package that is dated May 8, 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

Issue that this hotfix package fixes

This hotfix fixes the following issue that is not previously documented in a Microsoft Knowledge Base article:
In Office Project Professional 2007, when you create a report by using a Visual Reports template, the week number that is displayed in the report differs from the week number that is displayed in Office Project Professional 2007. Therefore, the incorrect week number is displayed in the report.

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 Project 2007 installed on the client computer.

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-kb952293-fullfile-x86-glb.exe	12.0.6300.5000	10,438,496	02-May-2008	09:04	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Project.msp	Not Applicable	9,967,616	01-May-2008	17:53	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:

File name	File version	File size	Date	Time	Platform
P12migrationtool.exe	12.0.6312.5000	7,886,072	18-Apr-2008	08:49	x86
Pj11od11.dll	12.0.6308.5000	1,332,312	22-Mar-2008	11:05	x86
Pjresc.dll	12.0.6300.5000	328,768	08-Dec-2007	12:30	x86
Prjres.dll	12.0.6300.5000	3,650,624	12-Dec-2007	16:18	x86
Serconv.dll	12.0.6308.5000	738,344	22-Mar-2008	11:06	x86
Winproj.exe	12.0.6314.5000	17,339,424	01-May-2008	14:29	x86

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

Back to the top

You install the 2007 Microsoft Office suite Service Pack 1 (SP1), or you install post-SP1 updates for the 2007 Office suite. Then, you run one of the following tools:

•	Microsoft Baseline Security Analyzer (MBSA) 1.2.1
•	The Office Scan Tool in Microsoft Systems Management Server (SMS) 2.0
•	The Office Update Inventory Tool 2.2

When you do this, the service pack or the updates are not detected.

Back to the top

This issue occurs because MBSA 1.2.1, the Office Scan Tool in SMS 2.0, and the Office Update Inventory Tool 2.2 are not designed to detect the 2007 Office suite SP1 or post-SP1 updates for the 2007 Office suite.

Back to the top

To resolve this issue, use one of the following tools instead of the tools that are mentioned in the Symptoms section:

•	MBSA 2.0.1 or a later version of MBSA For more information about MBSA 2.0.1, visit the following Microsoft Web site: http://www.microsoft.com/technet/security/tools/mbsahome.mspx (http://www.microsoft.com/technet/security/tools/mbsahome.mspx)
•	SMS 2003 Inventory Tool for Microsoft Updates (ITMU) For more information about ITMU, visit the following Microsoft Web site: http://technet.microsoft.com/en-us/sms/bb676783.aspx (http://technet.microsoft.com/en-us/sms/bb676783.aspx)
•	Microsoft Update To use Microsoft Update, visit the following Web site: http://update.microsoft.com/microsoftupdate/v6/default.aspx (http://update.microsoft.com/microsoftupdate/v6/default.aspx)
•	Windows Server Update Services (WSUS) For more information about WSUS, visit the following Microsoft Web site: http://technet.microsoft.com/wsus/default.aspx (http://technet.microsoft.com/wsus/default.aspx)
•	Office Update To use Office Update, visit the following Microsoft Web site: http://office.microsoft.com/officeupdate/ (http://office.microsoft.com/officeupdate) Note Office Update is not available for users who are running Windows Vista.

For more information about the supported versions of MBSA, click the following article number to view the article in the Microsoft Knowledge Base:

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.

A User may get the following popup when doing either of the following actions:

1. Opening Office Word or PowerPoint
2. Open Notepad or Wordpad, click on <File> and then try to <Open> file or <Print>.

Popup will have text similar to this (parameters may be different):

 

Windows – No Disk
Exception Processing Message 0xc0000013 Parameters
0x000007FEFD9F7240 0×0000000000000004 0x000007FEFD9F7240
0x000007FEFD9F7240
<Cancel> <Try Again> <Continue>

The “D:” drive is a removable device and there is no media in the “D:” drive at the time that the application is opened.

To resolve this issue do one of the following:

1.  Locate and remove Mxdwdui.BUD (C: Windows System32 spool drivers x64 3 mxdwdui.bud for 64-bit and C: Windows system32 spool drivers w32x86 3 mxdwdui.bud for 32-bit).
   Note: Need administrative privileges to remove this file. If you are in Audit mode you have Administrative privileges.

   OR

2. On the machine exhibiting the issue: Open the Printers folder, right click on the installed “Microsoft XPS Document Writer” printer, Properties, and in the “Microsoft XPS Document Writer Properties” dialog, and click on OK to close it. This will update the .BUD file to have the correct path to the system drive. 

   OR

3. Adding in another printer and setting it as default or removing and re-installing the “Microsoft XPS Document Writer” will also work around this issue.

 

 

 

This issue is likely to occur if your D: drive drive is a removable device and there is no media in the “D:” drive at the time that the application is opened. This is due to an incorrect file reference, pointing to D: Windows, in a binary file used by a default printing device.

 
This .BUD file contains an incorrect path to the system drive and is checked when opening up certain Office products and the error messsage can also be seen when using Notepad or Wordpad.

Clicking <Continue> will move beyond this message and you can use Office / Notepad / WordPad without any issues.

The .BUD file was designed to increase printing performance. It is a binary data file for the corresponding text data file mxdwdui.GPD file. If the .BUD file is not located then the process continues on where the .GPD file will be used with a slight increase in the time needed to process the data file.

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.

•	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 package.
•	Whether you must make any registry changes.
•	The files that the hotfix package contains.

Back to the top

Issue that the hotfix package fixes

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

•

Outlook 2003 provided a method for members of the Administrators group to force a specific signature to be used in e-mail messages and to prevent users from changing that signature. This method uses one the following registry subkeys: • HKEY_CURRENT_USER Software Policies Microsoft Office 11.0 Common MailSettings • HKEY_CURRENT_USER Software Microsoft Office 11.0 Common MailSettings However, users can still use the Signature feature to change the e-mail signature settings in Outlook 2007, even if members of the Administrators group configure one of the following registry subkeys for Outlook 2007: • HKEY_CURRENT_USER Software Policies Microsoft Office 12.0 Common MailSettings • HKEY_CURRENT_USER Software Microsoft Office 12.0 Common MailSettings

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 2007 Microsoft Office suites 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

There are no prerequisites for installing this hotfix.

Restart information

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

Hotfix replacement information

This hotfix is not replaced by any later 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 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-kb948939-fullfile-x86-glb.exe	12.0.6300.5000	24,159,712	15-Feb-2008	03:29	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Outlook.msp	Not Applicable	14,142,976	15-Feb-2008	08:56	Not Applicable
Word.msp	Not Applicable	13,070,848	15-Feb-2008	08:56	Not Applicable

Outlook.msp file information

File name	File version	File size	Date	Time	Platform
Contab32.dll	12.0.6300.5000	136,232	12-Dec-2007	23:56	x86
Digsig32.dll	12.0.6300.5000	394,752	12-Dec-2007	23:56	x86
Dlgsetp.dll	12.0.6302.5000	90,144	06-Feb-2008	20:57	x86
Emsmdb32.dll	12.0.6302.5000	1,477,224	06-Feb-2008	20:57	x86
Mapi32.dll	12.0.6303.5000	2,953,776	15-Feb-2008	12:21	x86
Mimedir.dll	12.0.6300.5000	342,032	07-Dec-2007	00:04	x86
Mspst32.dll	12.0.6302.5000	1,080,416	06-Feb-2008	20:57	x86
Omsmain.dll	12.0.6300.5000	663,088	13-Dec-2007	01:40	x86
Omsxp32.dll	12.0.6300.5000	195,136	13-Dec-2007	01:40	x86
Outlmime.dll	12.0.6300.5000	599,624	12-Dec-2007	23:56	x86
Outlook.exe	12.0.6303.5000	12,836,896	15-Feb-2008	12:21	x86
Outlph.dll	12.0.6300.5000	180,800	12-Dec-2007	23:56	x86
Outlrpc.dll	12.0.6302.5000	47,624	06-Feb-2008	20:57	x86
Outlvbs.dll	12.0.6300.5000	60,448	07-Dec-2007	00:05	x86
Pstprx32.dll	12.0.6300.5000	415,768	07-Dec-2007	00:05	x86
Scanpst.exe	12.0.6300.5000	40,520	07-Dec-2007	00:05	x86
Scnpst32.dll	12.0.6302.5000	265,816	06-Feb-2008	20:57	x86
Scnpst64.dll	12.0.6302.5000	275,552	06-Feb-2008	20:57	x86

Word.msp file information

File name	File version	File size	Date	Time	Platform
Winword.exe	12.0.6300.5000	349,720	12-Dec-2007	23:54	x86
Wwlib.dll	12.0.6303.5000	17,490,456	15-Feb-2008	11:43	x86

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

This article describes the 2007 Microsoft Office system issues that are fixed in the hotfix package that is dated February 26, 2008.

•	The issues that the hotfix fixes.
•	The prerequisites for installing the hotfix.
•	Whether you must restart the computer after you install the hotfix.
•	Whether the hotfix is replaced by any other hotfix.
•	Whether you must make any registry changes.
•	The files that the hotfix contains.

Back to the top

Issues that the hotfix package fixes

This hotfix fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

•

A server that is running Windows Server 2003 experiences high CPU usage, and Microsoft Office Outlook 2007 runs very slowly. This issue occurs when many users run Outlook 2007 in Terminal Server client sessions that are connected to the Windows Server 2003-based server.

•

You use the Microsoft Access Developer Extensions 2007 Package Solution wizard to package a Microsoft Office Access 2007 database application. Then, you install the packaged application on a computer. When you open the packaged application, you receive the following message: A potential security concern has been identified. Warning: It is not possible to determine that this content came from a trustworthy source. You should leave this content disabled unless the content provides critical functionality and you trust its source. File path: <path> This file might contain unsafe content that could harm your computer. Do you want to open this file or cancel the operation?

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 2007 Office suite 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

There are no prerequisites for installing this hotfix.

Restart information

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

Hotfix replacement information

This hotfix is not replaced by any later 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 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-kb948950-fullfile-x86-glb.exe	12.0.6300.5000	13,446,032	15-Feb-2008	03:29	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Mso.msp	Not applicable	18,952,192	15-Feb-2008	08:59	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:

File name	File version	File size	Date	Time	Platform
Mso.dll	12.0.6303.5000	16,906,288	15-Feb-2008	03:58	x86

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

This article describes the 2007 Office system issue that is fixed in the 2007 Office system hotfix package that is dated December 16, 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 package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issue that this hotfix package fixes

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

• You cannot search for anything beyond the third slide of a PowerPoint file (.pptx) in any Microsoft Search products.
• On 64-bit operating systems, a crawl for .vsd files generates an error message, such as The filtering process has been terminated in the crawl logs.

Hotfix information

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

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

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

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

Prerequisites

There are no prerequisites for installing this hotfix.

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 issue that is 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

Microsoft Windows Installer .msp file information

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.

Note The Offfiltx.msp file and the Visfilter.msp file contain the updated files for both the x86 version and the x64 version.

Offfiltx.msp

Visfilter.msp

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

This article describes the Microsoft Office Word 2007 issues that are fixed in the hotfix package that is dated October 28, 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 package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issues that this hotfix package fixes

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

• When you check the spelling of English language text in word 2007, one of the following words is not recognized and is flagged as a possible misspelling:
  • Palin
  • Palin’s
  • Silverlight
  • Silverlight’s
  • Malia
  • Malia’s
  • Sebelius
  • Sebelius’
  • Medvedev
  • Medvedev’s
• Consider the following scenario. You have the Catalan proofing tools for 2007 Microsoft Office system installed. You type a string that has an acute accent. Word 2007 suggests that you use an apostrophe to replace the acute accent. You select the replacement, and then click Change. In this scenario, you may receive the following error message:
  You have chosen a word that is not found in the main or custom dictionaries. Do you want to use this word and continue checking?

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.

Prerequisites

There are no prerequisites for installing this hotfix.

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

Microsoft Windows Installer .msp file information

Proof-en-us.msp information

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

When you apply a hotfix on a computer that is running Microsoft Office PerformancePoint Server 2007, you receive the following error message:

Back to the top

This issue occurs if you apply the hotfix on a computer that is running Microsoft Office PerformancePoint Server 2007 Evaluation Version.

Note You cannot apply a hotfix on a computer that is running Microsoft Office PerformancePoint Server 2007 Evaluation Version.

Back to the top

To resolve this issue, apply the hotfix after you upgrade to Microsoft Office PerformancePoint Server 2007.

Back to the top

Upgrade procedure for the PerformancePoint Monitoring Server component of Microsoft Office PerformancePoint Server 2007

To upgrade the evaluation edition of the PerformancePoint Monitoring Server component of Microsoft Office PerformancePoint Server 2007, follow these steps:

1.	On the computer that is running the evaluation edition of the PerformancePoint Monitoring Server component of Microsoft Office PerformancePoint Server 2007, remove the evaluation edition binaries of the PerformancePoint Monitoring Server component. To do this, use the Add or Remove Programs item in Control Panel.
2.	Install the enterprise edition binaries for the PerformancePoint Monitoring Server component of Microsoft Office PerformancePoint Server 2007.

Back to the top

Upgrade procedure for the PerformancePoint Planning Server component of Microsoft Office PerformancePoint Server 2007

To upgrade the evaluation edition of the PerformancePoint Planning Server component of Microsoft Office PerformancePoint Server 2007, follow these steps:

1.	On the computer that is running the evaluation edition of the PerformancePoint Planning Server component of Microsoft Office PerformancePoint Server 2007, remove the evaluation edition binaries of the PerformancePoint Planning Server component. To do this, use the Add or Remove Programs item in Control Panel.
2.	Install the enterprise edition binaries for the PerformancePoint Planning Server component of Microsoft Office PerformancePoint Server 2007.

For more information about how to upgrade the PerformancePoint Planning Server component of Microsoft Office PerformancePoint Server 2007, visit the following Microsoft Web site:

Back to the top

This article describes the 2007 Microsoft Office system issue that is fixed in the hotfix package that is dated December 16, 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 package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Issue that this hotfix package fixes

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

When you use a 2007 Office system application to interact with servers that require forms based authentication, you must enter your credentials persistently.

Hotfix information

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

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

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

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

Prerequisites

There are no prerequisites for installing this hotfix.

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 issue that is 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

Microsoft Windows Installer .msp file information

Infopath.msp information

Ipeditor.msp information

Mso.msp information

Powerpoint.msp information

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

When you start Microsoft Office Outlook 2007 for the first time, you may receive the following error message:

Then, when you start Outlook 2007, you may receive the following error message:

This issue occurs if the user names contain Unicode characters. When you run Outlook 2007 for the first time, Outlook does not translate user names that are stored as part of the user profile path in the registry from Unicode to ANSI correctly.

To resolve this issue, restart the computer.

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

Consider the following scenario:

•	You have a shared folder that is available offline.
•	On a Windows Vista-based computer, in an Office application or in WordPad, you use the Open File dialog box to open an offline file that is in the shared folder.

In this scenario, the shared folder goes offline. After the shared folder goes offline, you cannot make the shared folder go online from Windows Explorer.

Back to the top

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

Back to the top

Method 1

Wait awhile. The shared folder will come online again by itself.

Back to the top

Method 2

Do not open the file by using the Open File dialog box in an Office application or in WordPad. Instead, double-click the file to open it.

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, visit the following Microsoft TechNet Web site:

Back to the top

As part of an ongoing commitment to provide detection tools and deployment recommendations for security updates, Microsoft is delivering this detection and deployment guidance for all updates that are released during a Microsoft Security Response Center (MSRC) release cycle.

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

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

This article describes the detection and deployment guidance for the security release that is dated May 13, 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 May 13, 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 Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.

Specific exceptions

•	Security update 952044 (security bulletin MS08-029) Microsoft Update supports only the Forefront Client Security and Windows Defender parts of this update. The other products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

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 May 13, 2008 if you use MBSA version 2.1.

Note MBSA version 2.1 is now released and fully supports security and vulnerability assessment scans on Windows Vista and Windows Server 2008.General exceptions

•	MBSA version 2.1 does not support any Office 2000 components.
•	MBSA version 2.1 does not support any Macintosh products.
•	MBSA version 1.2.1 and 2.0.1 are no longer supported.

Specific exceptions

•	Security update 952044 (security bulletin MS08-029) MBSA version 2.1 does not support the Malware Protection Engine update. The products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

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 May 13, 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 exceptions

•	Security update 952044 (security bulletin MS08-029) WSUS 2.0 and WSUS 3.0 support only the Forefront Client Security and Windows Defender parts of this update. The other products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

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 May 13, 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 exceptions

•

Security update 952044 (security bulletin MS08-029) SMS ITMU and SUS Feature Pack do not support the Malware Protection Engine update. System Center Configuration Manager 2007 supports only the Forefront Client Security and Windows Defender parts of this update. The products that use the Malware Protection Engine update provide built-in mechanisms for automatic detection and deployment.

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 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 partly 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.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
951207	MS08-026	Word	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
951208	MS08-027	Publisher	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
950749	MS08-028	Jet	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
952044	MS08-029	Malware Protection Engine	Not applicable	Not applicable	Yes	No	Partly, see the WSUS section	No	No	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 May 14, 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 page:

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

This article describes the 2007 Microsoft Office system issue that is fixed in the 2007 Office post-Service Pack 1 hotfix package that is dated February 14, 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

Issue that this hotfix package fixes

This hotfix package fixes the following issue that is not previously documented in a Microsoft Knowledge Base article:
When you convert one of the following 2007 Office Trial edition products by using a newly purchased license key for Microsoft Office Basic 2007 or for Microsoft Office Small Business 2007, Picture Manager and Office Startup Assistant are not enabled as expected.

•	Microsoft Office Professional 2007 Trial
•	Microsoft Office Professional Plus 2007 Trial
•	Microsoft Office Standard 2007 Trial
•	Microsoft Office Ultimate 2007 Trial
•	Microsoft Office Enterprise 2007 Trial

Back to the top

Hotfix information

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

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

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

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

Prerequisites

There are no prerequisites for installing this hotfix.

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

You do not have to make any changes to the registry to apply this hotfix.

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-kb941469-fullfile-x86-glb.exe	12.0.6300.5000	5,770,704	28-Jan-2008	17:55	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Licensing.msp	Not Applicable	9,586,688	28-Jan-2008	18:16	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:

File name	File version	File size	Date	Time
ID_10035.DPC	Not Applicable	1,926	6-Dec-2007	16:37
ID_10031.DPC	Not Applicable	1,926	6-Dec-2007	16:37
ID_00045.DPC	Not Applicable	582	4-Oct-2007	20:58

Additional notes

•	For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
•	For more information, click the following article number to view the article in the Microsoft Knowledge Base: 824684 (/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top