The following security updates may appear to install correctly on your Windows XP Service Pack 2 (SP2)-based computer:

KB article	September 14, 2004 security update package name
832332 (http://support.microsoft.com/kb/832332/EN-US/)	Officexp-kb832332-client-enu, Officexp-kb832332-fullfile-enu
831932 (http://support.microsoft.com/kb/831932/EN-US/)	Visio2002-KB831932-FullFile-ENU
831931 (http://support.microsoft.com/kb/831931/EN-US/)	Project2002-kb831931-fullfile-enu

However, the installation of the original versions of these updates that was released on September 14, 2004, may not correctly update the Mso.dll file in your %Programfiles%\Common Files\Microsoft Shared\Office10 folder. See the "How to determine whether you are affected" section to determine whether this issue affects you.

Note This issue only affects the original security updates that were released on September 14, 2004. The original security update packages that are affected by this issue are named Officexp-kbnumber-filetype-localization.exe. For example, the original English client security update package for Security Update 832332 is named Officexp-kb832332-client-enu.exe.

On October 12, 2004, the 832332, 831932, and 831931 security updates were re-released to address the issue that is described in this article. The re-released updates that resolve this issue are named Officexp-kbnumber-v2-filetype-localizationv2.exe. For example, the re-released update package for Security Update 832332 is named Officexp-kb832332-v2-client-enu.exe.

Back to the top

This issue occurs if you have previously installed one of the software updates (http://support.microsoft.com/kb/824684/EN-US/) for Office XP, Visio 2002, or Microsoft Project 2002 that are documented in Microsoft Knowledge Base article 886992 (http://support.microsoft.com/kb/886992/EN-US/) on a Windows XP SP2-based computer.

Note The following broadly released software updates may cause this issue:

Back to the top

Single computer users

If your computer has not been updated correctly, you have the following options:

•	You can install the revised update. To do this, use either the method that is described in the "Automatic Updates or Windows Update" section, or the method that is described in the "Office Update" section.
•	You can repair Office. To do this, follow the instructions that are in the "Repair Office" section.

Automatic Updates or Windows Update

To resolve this issue, use the Automatic Update feature or use the Windows Update Web site to install Critical Update 885884 (http://support.microsoft.com/kb/885884/EN-US/).

For additional information about configuring the Automatic Update feature in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

To install this update from the Windows Update Web site, follow these steps:

1.	Visit the following Microsoft Web site: http://windowsupdate.microsoft.com/ (http://windowsupdate.microsoft.com/)
2.	Click Express Install (Recommended).
3.	If your computer is affected by this issue, Critical Update 885884 is automatically selected for you to install. Click Install.
4.	Review and accept the End User License Agreement (EULA).

Critical Update 885884 (http://support.microsoft.com/kb/885884/EN-US/) will be downloaded to your computer, and the Setup wizard will help you install it. For additional information about the 885884 critical update, click the following article number to view the article in the Microsoft Knowledge Base:

Office Update

To resolve this issue, install the revised 832332, 831932, or 831931 security updates from the Office Update Web site. To do this, follow these steps:

1.	Visit the following Microsoft Web site: http://officeupdate.microsoft.com (http://office.microsoft.com/en-us/downloads/maincatalog.aspx)
2.	Click Check for Updates. The Office Update Web site will scan your computer for installed updates.
3.	If you are affected by this issue, the re-released updates will be listed in the "Updates for Office XP" section.
4.	Click Start Installation, and then follow the instructions that appear on the screen to install the appropriate re-released security updates.

Repair Office

To resolve this issue, repair your installation of Office XP. To do this, follow these steps:

1.	Click Start, click Run, type appwiz.cpl in the Open box, and then press ENTER.
2.	Click Change or Remove Programs.
3.	In the list of currently installed programs, click your Microsoft Office XP, Microsoft Project 2002, or Visio 2002 product in the list of installed products.
4.	Click Click here for support information.
5.	Click Repair. Note If you installed your Office XP product from a CD-ROM, you may be prompted for your CD-ROM during the Detect and Repair process. If you installed your Office product from a network share and the network share is not available during the Detect and Repair process, you may be prompted for the location of the network resource that holds your Microsoft Office installation source files.
6.	If you are prompted to restart your computer, click Yes.

Back to the top

Enterprise customers

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

Note We recommend that you use the method that is described in the “Install revised security updates” section.

Install revised security updates

To resolve this issue, install the revised version of the affected security updates that are associated with MS04-028, released on October 12, 2004, by using the Office Update (http://office.microsoft.com/en-us/downloads/maincatalog.aspx) Web site or by downloading and installing the appropriate updates from the Microsoft Download Center:

•	Office XP: http://www.microsoft.com/downloads/details.aspx?FamilyId=7D128614-6D34-49DF-8D63-6C17E9A2D312 (http://www.microsoft.com/downloads/details.aspx?FamilyId=7D128614-6D34-49DF-8D63-6C17E9A2D312)
•	Visio 2002: http://www.microsoft.com/downloads/details.aspx?FamilyId=16C2DFFD-7B73-43C4-AB0D-2B5EFC80EB63 (http://www.microsoft.com/downloads/details.aspx?FamilyId=16C2DFFD-7B73-43C4-AB0D-2B5EFC80EB63)
•	Microsoft Project 2002: http://www.microsoft.com/downloads/details.aspx?FamilyId=B3EBCCEA-B0E4-41C7-A6F4-413864D2CCF3 (http://www.microsoft.com/downloads/details.aspx?FamilyId=B3EBCCEA-B0E4-41C7-A6F4-413864D2CCF3)

Install Critical Update 885884

To resolve this issue, install Critical Update 885884.

For additional information about Critical Update 885884, click the following article number to view the article in the Microsoft Knowledge Base:
Software Update Services (SUS) may also be used to deploy Critical Update 885884. SUS allows customers to install a service that can download all critical updates, security updates, and service packs as they are posted to the following Microsoft Windows Update Web site: When administrators have approved these updates, SUS will automatically make them available to all preconfigured servers that are running Microsoft Windows Server 2003 and Microsoft Windows 2000, and to desktops that are running Microsoft Windows XP Professional and Microsoft Windows 2000 Professional.

For more information about Software Update services and Windows Update services, the next generation of Software Update services, visit the following Microsoft Web site:

The MS04-028 Update Scanning Tools

IT Professionals can use one of the MS04-028 update scanning tools to scan computers for the required MS04-028 security updates and apply any missing updates from a local area network share. The tool can be run from a startup or logon script or by a user who has local administrator rights. There are two versions of this tool:

•

One version is intended for use in environments where Systems Management Server (SMS) or any other enterprise management solution is not used for update management. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 886988 (http://support.microsoft.com/kb/886988/) How to obtain and use the MS04-028 Enterprise Update Scanning Tool in environments that do not use Systems Management Server

•

One version is intended for use in environments where SMS is used for update management. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 885920 (http://support.microsoft.com/kb/885920/) How to obtain and use the MS04-028 Enterprise Update Scanning Tool in environments that use Systems Management Server 2003 and Systems Management Server 2.0

Repair Office

To resolve this issue, repair your installation of Office XP. To do this, follow these steps:

1.	Click Start, click Run, type appwiz.cpl in the Open box, and then press ENTER.
2.	Click Change or Remove Programs.
3.	In the list of currently installed programs, click your Office XP, Microsoft Project 2002, or Visio 2002 product in the list of installed products.
4.	Click Click here for support information.
5.	Click Repair. Note If you installed your Office XP product from a CD-ROM, you may be prompted for your CD-ROM during the Detect and Repair process. If you installed your Office product from a network share and the network share is not available during the Detect and Repair process, you may be prompted for the location of the network resource that holds your Office installation source files.
6.	If you are prompted to restart your computer, click Yes.

If you are an administrator and you do not want to reinstall the revised version of the MS04-028 updates individually, you can use the REINSTALL=<FeatureName> command. Use the following method if you are an administrator and you use the Msiexec.exe command to install updates.

Note Do not use this method if you are updating an administrative image, or if you are updating an administrative installation point.

The following are examples of the command lines that you can use to repair specific Microsoft Office products by using the Msiexec.exe /I {Product GUID} REINSTALL=<FeatureName> command:

For Microsoft Office 2003 (all products), Microsoft Office Project 2003, and Microsoft Office Visio 2003, use the following command line: For Office XP (all products), Microsoft Project 2002, and Visio 2002, use the followng command line: Notes

•

The FeatureName or ProductFiles are case sensitive. To install all the features, you can use the REINSTALL=ALL value, or you can install only the feature that is updated.

•

In these commands, Product GUID is the GUID for your Office 2003 or Office XP product. For example, {90110409-6000-11D3-8CFE-0150048383C9} is the GUID for US English Microsoft Office 2003 Professional Enterprise Edition. For your reference, the following articles provide information about the numbering scheme for each Office 2003 and Office XP product. For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base: 832672 (http://support.microsoft.com/kb/832672/) Description of numbering scheme for product code GUIDs in Office 2003 302663 (http://support.microsoft.com/kb/302663/) Description of the numbering scheme for product code GUIDs for Office XP programs

You can use the command line to install all the updates in a batch file that you can run on the destination computer, or as part of an SMS logon script when the user logs on to the computer.

Back to the top

If you are not running Windows XP SP2, this issue does not affect you. If you are running Windows XP SP2, use one of the methods in this section to determine whether you are affected by this issue:

Back to the top

Use the Microsoft Baseline Security Analyzer (MBSA)

Use MBSA to determine whether the revised updates (832332, 831932, and 831931) are installed on client computers for local computer scans only. For detailed information about how MBSA detects Office updates, visit the following Microsoft Web site: For additional information about the programs that MBSA does not detect, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about MBSA and to obtain MBSA, visit the following Microsoft Web site:

Back to the top

Verify the version of the Mso.dll file

The affected updates do not install the correct version of the Mso.dll file. Therefore, you can determine whether you are affected by this issue by manually checking the version of the Mso.dll file in your %Programfiles%\Common Files\Microsoft Shared\Office10 folder. To do this, follow these steps:

1.	Click Start, click Run, type %Programfiles%\Common Files\Microsoft Shared\Office10, and then click OK.
2.	Right-click the Mso.dll file, and then click Properties.
3.	On the Version tab, note the version number of the Mso.dll file. If the version number is not 10.0.6714.0 or a later version, you may be affected by this issue.

Back to the top