How to download and install the administrative version of the Outlook 2002 Security Patch: KB828040Important
Before you install this update, make sure that the following requirements have been met:
- Microsoft Windows Installer 2.0
Before you install this update, you must install Windows Installer 2.0 or later. For additional information about this requirement, see the "Windows Installer update requirements" section of this article.
- Microsoft Office XP Service Pack 2
Before you install this update, install Office XP Service Pack 2.
For additional information about how to install Office XP Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
325671Note The full-file Outlook 2002 Security Patch: KB828040 installs successfully on Office XP Service Pack 1 or Office XP Service Pack 2 installations.
OFFXP: Overview of the Office XP Service Pack 2
The following file is available for download from the Microsoft Download Center:Download the English version of the Outlook 2002 Security Patch: KB828040 package now.
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
How to Obtain Microsoft Support Files from Online Services
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 to prevent any unauthorized changes to the file. Note
To obtain a localized version of the Outlook 2002 Security Patch: KB828040 package, visit the following Microsoft Web site:
If you are the server administrator, follow these steps to update the server location with the administrative update and deploy the update:
- Click Save to save the Officexp-kb828040-fullfile-enu.exe file to the selected folder.
- In Microsoft Windows Explorer, double-click officexp-kb828040-fullfile-enu.exe.
- Click Yes to accept the License Agreement.
- In the Type the location where you want to place the extracted files box, type c:\828040, and then click OK.
- Click Yes when you are prompted to create the folder.
- If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box where Admin Path is the path of your administrative installation point for Microsoft Office XP (for example, C:\OfficeXP), MSI File is the .msi database package for the Office XP product (for example, ProPlus.msi), and MSP File is the name of the administrative update (for example, OUTLOOKff.msp):
msiexec /a AdminPath\MSI File /p C:\828040\MSP File SHORTFILENAMES=TRUENote You can append /qb+ to the command line so that the Office XP AdministrativeInstallation dialog box and the End User LicenseAgreement dialog box do not appear.
- To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box where Admin Path is the path of your administrative installation point for Office XP (for example, C:\OfficeXP), MSI File is the MSI database package for the Office XP product (for example, ProPlus.msi), and FeatureList is the list of feature names (case sensitive) that have to be reinstalled for the update:
msiexec /i AdminPath\MSI FileREINSTALL=Feature List REINSTALLMODE=vomu To install all features, you can use REINSTALL=ALL, or you can install the following features:
After you install the update, you cannot remove it.
For additional information about how to update your administrative installation and deploy to client workstations, click the following article number to view the article in the Microsoft Knowledge Base:
HOW TO: Install a public update to administrative installations of Office XP
This article contains standard instructions for installing an administrative public update. You can also see the following article in the Microsoft Office Resource Kit:
How to determine whether the update is installed
The update contains updated versions of the following files:
File name Version ----------------------- OUTLOOK.EXE 10.0.5709.0 DLGSETP.DLL 10.0.5626.0 ENVELOPE.DLL 10.0.4817.0 EXCHCSP.DLL 10.0.5328.0 EXSEC32.DLL 10.0.4907.0 IMPMAIL.DLL 10.0.4406.0 OUTLCM.DLL 10.0.5424.0 OUTLCTL.DLL 10.0.5112.0 OUTLLIB.DLL 10.0.5709.0 OUTLMIME.DLL 10.0.4608.0 OUTLPH.DLL 10.0.5703.0 RECALL.DLL 10.0.4721.0
You do not have to install this update if you have a later version of one or more of the files that are listed in the table.
To determine the version of Outlook that is installed on your computer, follow these steps.Note
Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type Outlook.exe, and then click Search.
- In the list of files, right-click Outlook.exe, and then click Properties.
- On the Version tab, determine the version of Outlook that is installed on your computer.
For additional information about how to determine the version of product 2002 on your computer, click the following article number to view the article in the Microsoft Knowledge Base:
HOW TO: Check the version of Office XP
If the Outlook 2002 Security Patch: KB828040 is already installed on your computer, you receive the following error message when you try to install the Outlook 2002 Security Patch: KB828040:
This update has already been applied or is included in an update that has already been applied.
Windows Installer update requirements
To install the update that is described in this article, you must have Windows Installer 2.0 or later installed. Both Microsoft Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or later. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites.
Windows Installer for Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows Millennium Edition (Me):
Windows Installer for Microsoft Windows NT 4.0 and Windows 2000:
List of issues that are fixed by the update
The Outlook 2002 Security Patch: KB828040 includes the following earlier released updates for Outlook 2002:
Outlook 2002 update: December 4, 2002
The Outlook 2002 Security Patch: KB828040 fixes the issues that are described in the following Microsoft hotfix package articles:
Outlook 2002 post-Service Pack 2 hotfix package: July 1, 2003
Outlook 2002 post-Service Pack 2 hotfix package: September 12, 2003
Outlook 2002 post-Service Pack 2 hotfix package: July 18, 2003
Availability of the Outlook 2002 post-Service Pack 2 hotfix package: August 10, 2003
Availability of the Outlook 2002 post-Service Pack 2 hotfix package: August 15, 2003
Availability of the Outlook 2002 post-Service Pack 2 hotfix package: August 22, 2003
Outlook 2002 post-Service Pack 2 hotfix package: August 29, 2003
Outlook 2002 post-Service Pack 2 hotfix package: July 27, 2003
Outlook 2002 Security Patch: KB828040 fixes the issues that are described in the following Microsoft Knowledge Base articles:
OL2002: Error message: The Exchange mailbox conferencing resource is not configured properly
OL2002: Outlook phone dialer dials a zero before dialing an internal phone number
An HTML-formatted e-mail message is not received by a recipient that uses a different e-mail protocol when it is sent in Outlook 2002
OL2002: AlwaysSign or AlwaysEncrypt policy is not enforced on replied or forwarded messages
Line breaks are not inserted as expected in the text of an e-mail message in Outlook 2002
OL2000: Changes to a forwarded message cause undesirable changes to the original message
OL2002: Transport provider is not notified if configuration changes when the provider is subscribed to the nkConfigHasChanged event
OL2002: "Can't open this item. Operations on message headers can not be performed in this folder" error message when you open mail
OL2002: Runtime error when you add a shortcut to your Windows NT 4.0-based computer
OL2002: Error message: Microsoft Outlook could not access the specified folder location
OL2002: Offline address book is downloaded when you configure Outlook for offline use
OL2002: Remote mail downloads headers for deleted messages
OL2002: The Free/Busy bar incorrectly displays busy for the whole day
Info bar not updated when delegate accepts an exception to recurring meeting request
OL2002: Outlook View Control returns only the current date
OL2002: A calendar that you save as a Web page shows no appointments on the last day
OL2002: "Set ActiveExplorer.CurrentFolder = Session.GetDefaultFolder(olFolder<FolderName>)" does not work as expected in the FolderSwitch event
OL2002: You cannot send plain text only messages by using Extended MAPI
OL2002: The "Duplicate Contact Detected" dialog box is not displayed when you save a contact that already exists to the Contacts folder
OL2002: Public folder home page not available offline with no network connection
OL2002: File As format changes to first name and last name
OL2002: Error message: "Resource has declined your meeting because it is recurring"
OL2002: Programmatically inserted attachment has blank icon and no caption
OL2002: Keyboard language changes to a different language when you start Microsoft Outlook
OL2002: File path does not convert to UNC when inserted as a hyperlink
OL2002: E-mail messages that you send are lost if you pasted the address from a received e-mail message
OL2002: The wrong name becomes the focus in the list of e-mail messages when you type a DBCS for the first character of the sender's display name
OL2002: Error message in the Mso.dll file when you reply to an e-mail message that was sent by using the "Have Replies Sent To" option
OL2002: The incorrect date and time appears for read receipts
OL2002: Rules appear as turned off in the Rules Wizard
OL2002: Programmatically inserted attachment has bank icon and no text
OL2002: Error message "...The server is not available..." when you work offline
OL2002:"The document entered into the Office document field is not associated with an Office application..." error message when you attach a Microsoft Office document to your online meeting request
OL2002: Incorrect e-mail address in To box
OL2002: "Always Ask Before Opening This Type of File" check box not available
OL2002: Cannot set a filter when you programmatically create a Calendar View
OL2002: You cannot use the Outlook Databinding control to view another user's Outlook folder
OL2002: Tasks folder is repeatedly duplicated when you view the Mailbox folder of another user
OL2002: Items in Sent Items folder may show as sent when the items were not delivered
OL2000: Voting buttons are missing from e-mail messages that are opened on a DMS e-mail system
OL2002: The attendee status is reset after you add a new attendee to a recurring meeting
Custom form action causes Outlook to quit unexpectedly
OL2002: The To box is automatically populated with recipients when you forward a meeting request
OL2002: Error message: Microsoft LDAP Directory: Can't contact LDAP directory server (81)
OL2002: "The value for appointment busy status is not valid" error message when you try to open an appointment
OL2002: Add-ins are disabled if a process first starts Outlook
The Outlook 2002 Security Patch: KB828040 fixes the following issues that were previously not documented in the Microsoft Knowledge Base.
You can pass duplicate parameters to Outlook.exe
You can pass duplicate command line parameters to Outlook.exe.
If you remove Nortel encryption on a message, you may remove the text of the message
When you have a message in a personal folders (.pst) file that encrypted and signed with a Nortel certificate, and then you remove the encryption but leave the message signed, the body of the message becomes blank.
Word is not your e-mail editor when you add a custom user property
If you add a custom user property to an e-mail message in Microsoft Outlook, Microsoft Word no longer starts as your default e-mail editor when you try to forward or to reply to the modified e-mail message.Note
This problem occurs in both Rich Text Format (RTF) and HTML formatted e-mail messages.