Microsoft Security Bulletin MS08-008 – Critical

I am a third-party application developer and I use OLE Automation in my application. Is my application vulnerable and how do I update it? 
Visual Basic 6.0 is the only development platform affected by this security update. This bulletin provides a link to download an update for Visual Basic 6.0 Service Pack 6. Developers that use the VB6 Package and Deployment Wizard to redistribute oleaut32.dll should ensure that they update the version of oleaut32.dll installed with their application by downloading the Visual Basic 6.0 update provided in this bulletin. Developers are encouraged to follow recommended best practices for using a shared component. For more information on best practices on shared component use, please see the Microsoft Knowledge Base Article 835322 on Isolated Applications.

I am developing software which contains the redistributable file oleaut32.dll from Visual Basic6.0. What do I do? 
You should install the security update included in this security bulletin for Visual Basic 6.0. If you have redistributed oleaut32.dll with your application, you should issue an updated version of your application to your customers with the updated version of this file included in Visual Basic 6.0 download of this security update.

If third-party applications use or install the affected OLE component, could I still be vulnerable even after I have installed all required Microsoft security updates? 
No, this security update replaces and re-registers the affected OLE component provided with the operating system. If third party applications follow the recommended best practices for using a shared component as a side by side assembly then they are also not affected. Customers are potentially at risk if third party applications do not follow the recommended best practices and instead redistribute a version of oleaut32.dll with their application. Microsoft Knowledge Base Article 921503 also contains instructions for customers that wish to manually check for the registered affected OLE component. Customers are encouraged to contact their third party solutions developer for addition information.

I am using an older edition of the software discussed in this security bulletin. What should I do? 
The affected software listed in this bulletin has been tested to determine which editions are affected. Other editions are past their support life cycle. To determine the support life cycle for your product and edition, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older editions of the software to migrate to supported editions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle. For more information about the extended security update support period for these operating system editions, visit the Microsoft Product Support Services Web site.

Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

A remote code execution vulnerability exists in Object Linking and Embedding (OLE) Automation. An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2007-0065.

Mitigating Factors for OLE Heap Overrun Vulnerability - CVE-2007-0065

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

•	In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. An attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
•	An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
•	By default, all supported editions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce the number of successful attacks that exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail, they could still be vulnerable to this issue through the Web-based attack scenario.
•	By default, Internet Explorer on Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.

Top of section

Workarounds for OLE Heap Overrun Vulnerability - CVE-2007-0065

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

•

Disable attempts to instantiate the Microsoft Forms 2.0 ImageActiveX Control in Internet Explorer You can disable attempts to instantiate a COM object in Internet Explorer by setting the kill bit for the control in the registry. Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use the Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note We recommend backing up the registry before you edit it. For detailed steps that you can use to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow these steps in this article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer. To set the kill bit for the Microsoft Forms 2.0 Image ActiveX Control, paste the following text in a text editor such as Notepad. Then, save the file by using the .reg file name extension. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{4C599241-6926-101B-9992-00000B65C6F9}] "Compatibility Flags"=dword:00000400 You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, visit the following Microsoft Web sites: • Step-by-Step Guide to Understanding the Group Policy Feature Set • Windows 2000 Group Policy • Group Policy in Windows Server 2003 Note You must restart Internet Explorer for your changes to take effect.

•

Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone You can help protect against this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps: 1. In Internet Explorer, click Internet Options on the Tools menu. 2. Click the Security tab. 3. Click Internet, and then click Custom Level. 4. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. 5. Click Local intranet, and then click Custom Level. 6. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. 7. Click OK two times to return to Internet Explorer. Impact of Workaround: Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly. Add sites that you trust to the Internet Explorer Trusted sites zone. After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone. To do this, follow these steps: 1. In Internet Explorer, click Tools, click Internet Options, and then click the Security tab. 2. In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites. 3. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box. 4. In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add. 5. Repeat these steps for each site that you want to add to the zone. 6. Click OK two times to accept the changes and return to Internet Explorer. Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.

•

Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High. To raise the browsing security level in Microsoft Internet Explorer, follow these steps: 1. Tools menu, click Internet Options. 2. Internet Options dialog box, click the Security tab, and then click the Internet icon. 3. Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High. Note If no slider is visible, click Default Level, and then move the slider to High. Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High. Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone”.

Top of section

FAQ for OLE Heap Overrun Vulnerability - CVE-2007-0065

What is the scope of the vulnerability? 
This is a remote code execution vulnerability. A remote, anonymous attacker who successfully exploited this vulnerability could run arbitrary code in the context of the logged-on user.

What causes the vulnerability? 
Specially crafted script requests may cause memory corruption when using OLE Automation.

What is OLE Automation? 
Object linking and embedding (OLE) Automation is a Windows protocol that allows an application to share data or control another application. OLE Automation is an industry standard that applications use to expose their OLE objects to development tools, macro languages, and other containers that support OLE Automation.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

How could an attacker exploit the vulnerability? 
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site. This can also include Web sites that accept user-provided content or advertisements, Web sites that host user-provided content or advertisements, and compromised Web sites. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.

What systems are primarily at risk from the vulnerability?  
This vulnerability requires that a user is logged on and visits a Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.

What does the update do? 
The update removes the vulnerability by validating the memory request within OLE Automation.

I am running Internet Explorer for Windows Server 2003. Does this mitigate this vulnerability? 
Yes. By default, Internet Explorer for Windows Server 2003 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running malicious Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration.

When this security bulletin was issued, had this vulnerability been publicly disclosed? 
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? 
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Top of section

Manage the software and security updates you need to deploy to the servers, desktop, and mobile computers in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Note for Windows Vista Microsoft does not support installing MBSA 2.0.1 on computers that run Windows Vista, but you may install MBSA 2.0.1 on a supported operating system and then scan the Windows Vista-based computer remotely. For additional information about MBSA support for Windows Vista, visit the MBSA Web site. See also Microsoft Knowledge Base Article 931943: Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista.

For more information about MBSA 2.0.1, see MBSA 2.0 Frequently Asked Questions.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 to Windows 2000 and later operating systems. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager (SCCM) 2007 uses WSUS 3.0 for detection of updates. For more information about SCCM 2007 Software Update Management, visit System Center Configuration Manager 2007.

Note for Windows Vista Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista manageability.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Affected Software

For information about the specific security update for your affected software, click the appropriate link:

Windows 2000 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue may be included in a future update rollup
Deployment
Installing without user intervention	Windows 2000 Service Pack 4: Windows2000-KB943055-x86-enu /quiet
Installing without restarting	Windows 2000 Service Pack 4: Windows2000-KB943055-x86-enu /norestart
Update log file	Windows 2000 Service Pack 4: KB943055.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update
Hotpatching	Not applicable
Removal Information	Windows 2000 Service Pack 4: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB943055$\Spuninst folder
File Information	See the next subsection, File Information, for the full file manifest
Registry Key Verification	For Windows 2000 Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB943055\Filelist

File Information

The English version of this security update has the 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 tool in Control Panel.

For all supported editions of Microsoft Windows 2000:

File Name	Version	Date	Time	Size
oleaut32.dll	2.40.4532.0	06-Dec-2007	00:10	631,056

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Top of section

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem	Overwrites OEM files without prompting
/nobackup	Does not back up files needed for uninstall
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files
/extract[:path]	Extracts files without starting the Setup program
/ER	Enables extended error reporting
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification 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. 1. Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Windows XP (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	Windows XP Service Pack 2: WindowsXP-KB943055-x86-enu /quiet
	Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB943055-x64-enu /quiet
Installing without restarting	Windows XP Service Pack 2: WindowsXP-KB943055-x86-enu /norestart
	Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB943055-x64-enu /norestart
Update log file	KB943055.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB943055$\Spuninst folder
File Information	See the next subsection, File Information, for the full file manifest
Registry Key Verification	For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB943055\Filelist
	For all supported x64 editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB943055\Filelist

File Information

The English version of this security update has the 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 tool in Control Panel.

For all supported 32-bit editions of Windows XP:

File Name	Version	Date	Time	Size	Folder
oleaut32.dll	5.1.2600.3266	04-Dec-2007	18:38	550,912	SP2GDR
oleaut32.dll	5.1.2600.3266	04-Dec-2007	18:29	551,936	SP2QFE

For all supported x64-based editions of Windows XP Professional:

File Name	Version	Date	Time	Size	CPU	Folder
oleaut32.dll	5.2.3790.3057	14-Dec-2007	00:11	1,116,672	X64	SP1GDR
woleaut32.dll	5.2.3790.3057	14-Dec-2007	00:11	557,568	X86	SP1GDR\wow
oleaut32.dll	5.2.3790.3057	14-Dec-2007	00:19	1,117,696	X64	SP1QFE
woleaut32.dll	5.2.3790.3057	14-Dec-2007	00:19	558,080	X86	SP1QFE\wow
oleaut32.dll	5.2.3790.4202	14-Dec-2007	00:27	1,123,328	X64	SP2GDR
woleaut32.dll	5.2.3790.4202	14-Dec-2007	00:28	553,984	X86	SP2GDR\wow
oleaut32.dll	5.2.3790.4202	14-Dec-2007	00:20	1,124,352	X64	SP2QFE
woleaut32.dll	5.2.3790.4202	14-Dec-2007	00:20	554,496	X86	SP2QFE\wow

Note For a complete list of supported editions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Top of section

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem	Overwrites OEM files without prompting
/nobackup	Does not back up files needed for uninstall
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files
/integrate:path	Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]	Extracts files without starting the Setup program
/ER	Enables extended error reporting
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files

Verifying That the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification 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. 1. Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Windows Server 2003 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: WindowsServer2003-KB943055-x86-enu /quiet
	Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB943055-x64-enu /quiet
	Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems: WindowsServer2003-KB943055-ia64-enu /quiet
Installing without restarting	Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2: WindowsServer2003-KB943055-x86-enu /norestart
	Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB943055-x64-enu /norestart
	Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems: WindowsServer2003-KB943055-ia64-enu /norestart
Update log file	KB943055.log
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update
Hotpatching	This security update does not support HotPatching. For more information about HotPatching see Microsoft Knowledge Base Article 897341.
Removal Information	Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 Service Pack 2: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the Use the Spuninst.exe utility, located in the %Windir%\$NTUninstallKB943055$\Spuninst folder
File Information	See the next subsection, File Information, for the full file manifest
Registry Key Verification	For all supported 32-bit editions, Itanium-based versions, and x64-based versions of Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 Service Pack 2: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB943055\Filelist

File Information

The English version of this security update has the 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 tool in Control Panel.

For all supported 32-bit editions of Windows Server 2003:

File Name	Version	Date	Time	Size	Folder
oleaut32.dll	5.2.3790.3057	13-Dec-2007	08:14	557,568	SP1GDR
oleaut32.dll	5.2.3790.3057	13-Dec-2007	08:01	558,080	SP1QFE
oleaut32.dll	5.2.3790.4202	13-Dec-2007	07:49	553,984	SP2GDR
oleaut32.dll	5.2.3790.4202	13-Dec-2007	07:05	554,496	SP2QFE

For all supported x64-based editions of Windows Server 2003:

File Name	Version	Date	Time	Size	CPU	Folder
oleaut32.dll	5.2.3790.3057	14-Dec-2007	00:11	1,116,672	X64	SP1GDR
woleaut32.dll	5.2.3790.3057	14-Dec-2007	00:11	557,568	X86	SP1GDR\wow
oleaut32.dll	5.2.3790.3057	14-Dec-2007	00:19	1,117,696	X64	SP1QFE
woleaut32.dll	5.2.3790.3057	14-Dec-2007	00:19	558,080	X86	SP1QFE\wow
oleaut32.dll	5.2.3790.4202	14-Dec-2007	00:27	1,123,328	X64	SP2GDR
woleaut32.dll	5.2.3790.4202	14-Dec-2007	00:28	553,984	X86	SP2GDR\wow
oleaut32.dll	5.2.3790.4202	14-Dec-2007	00:20	1,124,352	X64	SP2QFE
woleaut32.dll	5.2.3790.4202	14-Dec-2007	00:20	554,496	X86	SP2QFE\wow

For all supported Itanium-based editions of Windows Server 2003:

File Name	Version	Date	Time	Size	CPU	Folder
oleaut32.dll	5.2.3790.727	14-Dec-2007	00:45	3,790,848	IA-64	RTMGDR
woleaut32.dll	5.2.3790.727	14-Dec-2007	00:45	499,200	X86	RTMGDR\wow
oleaut32.dll	5.2.3790.727	14-Dec-2007	00:45	3,791,360	IA-64	RTMQFE
woleaut32.dll	5.2.3790.727	14-Dec-2007	00:45	499,200	X86	RTMQFE\wow
oleaut32.dll	5.2.3790.3057	14-Dec-2007	00:36	3,972,608	IA-64	SP1GDR
woleaut32.dll	5.2.3790.3057	14-Dec-2007	00:37	557,568	X86	SP1GDR\wow
oleaut32.dll	5.2.3790.3057	14-Dec-2007	00:45	2,241,536	IA-64	SP1QFE
woleaut32.dll	5.2.3790.3057	14-Dec-2007	00:45	558,080	X86	SP1QFE\wow
oleaut32.dll	5.2.3790.4202	14-Dec-2007	01:16	3,980,800	IA-64	SP2GDR
woleaut32.dll	5.2.3790.4202	14-Dec-2007	01:16	553,984	X86	SP2GDR\wow
oleaut32.dll	5.2.3790.4202	14-Dec-2007	00:36	2,252,288	IA-64	SP2QFE
woleaut32.dll	5.2.3790.4202	14-Dec-2007	00:37	554,496	X86	SP2QFE\wow

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Top of section

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/overwriteoem	Overwrites OEM files without prompting
/nobackup	Does not back up files needed for uninstall
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files
/integrate:path	Integrates the update into the Windows source files. These files are located at the path that is specified in the switch.
/extract[:path]	Extracts files without starting the Setup program
/ER	Enables extended error reporting
/verbose	Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.

Removing the Update

This security update supports the following setup switches.

Supported Spuninst.exe Switches
Switch	Description
/help	Displays the command-line options
Setup Modes
/passive	Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.
/quiet	Quiet mode. This is the same as unattended mode, but no status or error messages are displayed.
Restart Options
/norestart	Does not restart when installation has completed
/forcerestart	Restarts the computer after installation and force other applications to close at shutdown without saving open files first.
/warnrestart[:x]	Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch.
/promptrestart	Display a dialog box prompting the local user to allow a restart
Special Options
/forceappsclose	Forces other programs to close when the computer shuts down
/log:path	Allows the redirection of installation log files

Verifying that the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification 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. 1. Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

•

Registry Key Verification You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section. These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.

Top of section

Top of section

Windows Vista (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	All supported 32-bit editions of Windows Vista: Windows6.0-KB943055-x86 /quiet
	All supported x64-based editions of Windows Vista: Windows6.0-KB943055-x64 /quiet
Installing without restarting	All supported 32-bit editions of Windows Vista: Windows6.0-KB943055-x86 /quiet /norestart
	All supported x64-based editions of Windows Vista: Windows6.0-KB943055-x64 /quiet /norestart
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	Yes, you must restart your system after you apply this security update
Hotpatching	Not applicable
Removal Information	WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information	See the next subsection, File Information, for the full file manifest.
Registry Key Verification	Note: A registry key does not exist to validate the presence of this update. To detect the presence of the update, use Windows Management Instrumentation (WMI).

File Information

The English version of this security update has the 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 tool in Control Panel.

For all supported 32-bit editions of Windows Vista:

File Name	Version	Date	Time	Size	Folder
oleaut32.dll	6.0.6000.16607	04-Dec-2007	05:01	558,080	x86_microsoft-windows-ole-automation_31bf3856ad364e35_6.0.6000.16607_none_bb20ededfe4d5398
oleaut32.dll	6.0.6000.20732	04-Dec-2007	04:19	559,104	x86_microsoft-windows-ole-automation_31bf3856ad364e35_6.0.6000.20732_none_bb8519831787c882

For all supported x64-based editions of Windows Vista:

File Name	Version	Date	Time	Size	CPU	Folder
oleaut32.dll	6.0.6000.16607	04-Dec-2007	06:20	869,376	X64	amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.0.6000.16607_none_173f8971b6aac4ce
oleaut32.dll	6.0.6000.20732	04-Dec-2007	05:16	867,840	X64	amd64_microsoft-windows-ole-automation_31bf3856ad364e35_6.0.6000.20732_none_17a3b506cfe539b8
oleaut32.dll	6.0.6000.16607	04-Dec-2007	05:01	558,080	X86	wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.0.6000.16607_none_219433c3eb0b86c9
oleaut32.dll	6.0.6000.20732	04-Dec-2007	04:19	559,104	X86	wow64_microsoft-windows-ole-automation_31bf3856ad364e35_6.0.6000.20732_none_21f85f590445fbb3

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Top of section

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/?, /h, /help	Displays help on supported switches.
/quiet	Suppresses the display of status or error messages.
/norestart	When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.

Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.

Verifying that the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information

•

File Version Verification 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. 1. Click Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Top of section

Top of section

Office 2004 for Mac

Deployment Information

Prerequisites

•	Mac OS X 10.2.8 or a later version of Mac OS on 700 MHz native PowerPC G3, G4, or G5 processor (Intel processors are not supported)
•	Mac OS X user accounts must have administrator privileges to install this security update.

Installing the Update

Download and install the appropriate language version of the Microsoft Office 2004 for Mac 11.4.0 Update from the Microsoft Mactopia Web site.

Removing the Update

This security update cannot be uninstalled.

Additional Information

If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Support to learn about the support options that are available to you.

Top of section

Top of section

Microsoft Visual Basic 6.0 Service Pack 6

Reference Table

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	Visual Basic 6.0 SP6: VB6-KB946235-x86-enu /q:a
Installing without restarting	Visual Basic 6.0 SP6: VB6-KB946235-x86-enu /r:n
Update log file	Not applicable
Further information	See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required	No, you do not need to restart your system after you apply this security update
Removal Information	This update cannot be removed
File Information	See the next subsection, File Information, for the full file manifest
Registry Key Verification	Not applicable

File Information

The English version of this security update has the 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 tool in Control Panel.

For all supported editions of Microsoft Visual Basic 6.0:

File Name	Version	Date	Time	Size
oleaut32.dll	2.40.4532.0	21-Dec-2007	21:14	640,408
oleaut32.dll	2.40.4520.0	21-Dec-2007	21:14	939,144
oleaut32.dll	2.40.4520.0	21-Dec-2007	21:14	939,144
oleaut32.dll	5.2.3790.727	21-Dec-2007	21:14	508,552
oleaut32.dll	5.2.3790.3057	21-Dec-2007	21:14	567,432
oleaut32.dll	5.2.3790.4202	21-Dec-2007	21:14	563,848
oleaut32.dll	6.0.6000.20732	21-Dec-2007	21:14	568,456
oleaut32.dll	3.50.5022.0	21-Dec-2007	21:14	586,888
oleaut32.dll	5.1.2600.3266	21-Dec-2007	21:14	561,288

Note For a complete list of supported versions, see the Support Lifecycle Index. For a complete list of service packs, see Lifecycle Supported Service Packs. For more information on the support lifecycle policy, see Microsoft Support Lifecycle.

Top of section

Deployment Information

Installing the Update

When you install this security update, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch	Description
/?	Displays the command-line options.
Setup Modes
/q [:u | :a]	/q - Specifies quiet mode, or suppresses prompts. /q:u - Specifies user-quiet mode, which presents some dialog boxes to the user. /q:a - Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
Install Options
/C	Extracts the files without installing them. If /t: path is not specified, you are prompted for a target folder.
/T:path	Specifies the target folder for extracting files.
/C:path	Specifies the UNC path and name of the Setup.inf or .exe file.
/n:v	No version checking. Install the package over any previous version.
Restart Options
/r:n	Never restarts the system after installation.
/r:i	Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a	Always restarts the system after installation.
/r:s	Restarts the computer after installation without prompting the user.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 197147.

Verifying that the Update Has Been Applied

•

Microsoft Baseline Security Analyzer To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.

•

File Version Verification 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. 1. Start, and then click Search. 2. In the Search Results pane, click All files and folders under Search Companion. 3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search. 4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Top of section

Top of section