Registry Key Verification For Microsoft XML Core Services 3.0 on all supported editions of Windows Vista: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Vista: HKEYLOCALMACHINE SOFTWARE Microsoft Updates MSXML4SP3 Q2758694 For Microsoft XML Core Services 6.0 on all supported editions of Windows Vista: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch.

• Msxml Parser

• Microsoft XML Parser (MSXML) 3.0 Service Pack 7 (SP7) v1 Offer bug fixes for previous released of MSXML 3.0 SP. Microsoft XML Parser (MSXML) 3.0 Service Pack 7 (SP7) Editor's review.
• To install Microsoft XML Parser 3.0, follow these steps: Check if the operating system meets the requirement to install Microsoft XML Parser 3.0. The following operating systems are support by Microsoft XML Parser 3.0.

Deployment Information Installing the Update When you install this security update, the installer checks whether 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. The security updates for MSXML 3.0 and MSXML 6.0 support 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.

Original title - Program install I'm installing MSXML 4.0 sp3 parser for windows 10, during the installation it ask me where do I want to place the extracted files.

The security update for MSXML 4.0 supports the following setup switches: Supported Security Update Installation Switches Switch Description /help Displays the command-line options. Setup Modes /qn b r f or /quiet Sets user interface level. N - No user interaction b - Basic user interaction r - Reduced user interaction f - Full user interaction (default) 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. /promptrestart Displays a dialog box prompting the local user to allow a restart.

Logging Options /li w e a r u c m o p v x + !. i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file! - Flush each line to the log. Log all information, except for v and x options /log Equivalent of /l.

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. 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 editions of Microsoft Windows, the following steps may be different on your system.

If they are, see your product documentation to complete these steps. Click Start and then enter an update file name in the Start Search box. When the file appears under Programs, right-click the file name and click Properties. On the General tab, compare the file size with the file information tables provided in the bulletin KB article. Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 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. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. Windows Server 2008 (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.

Registry Key Verification For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008: HKEYLOCALMACHINE SOFTWARE Microsoft Updates MSXML4SP3 Q2758694 For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. Deployment Information Installing the Update When you install this security update, the installer checks whether 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.

The security updates for MSXML 3.0 and MSXML 6.0 support 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. The security update for MSXML 4.0 supports the following setup switches: Supported Security Update Installation Switches Switch Description /help Displays the command-line options.

Setup Modes /qn b r f or /quiet Sets user interface level. N - No user interaction b - Basic user interaction r - Reduced user interaction f - Full user interaction (default) 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. /promptrestart Displays a dialog box prompting the local user to allow a restart. Logging Options /li w e a r u c m o p v x + !.

i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file! - Flush each line to the log. Log all information, except for v and x options /log Equivalent of /l. 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. 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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. Click Start and then enter an update file name in the Start Search box.

When the file appears under Programs, right-click the file name and click Properties. On the General tab, compare the file size with the file information tables provided in the bulletin KB article. Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 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. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. Windows 7 (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. Registry Key Verification For Microsoft XML Core Services 3.0 on all supported editions of Windows 7: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 7: HKEYLOCALMACHINE SOFTWARE Microsoft Updates MSXML4SP3 Q2758694 For Microsoft XML Core Services 6.0 on all supported editions of Windows 7: Note A registry key does not exist to validate the presence of this update.

Use WMI to detect for the presence of this patch. Deployment Information Installing the Update When you install this security update, the installer checks whether 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. The security updates for MSXML 3.0 and MSXML 6.0 support 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. /warnrestart: When combined with /quiet, the installer will warn the user before initiating restart. /promptrestart When combined with /quiet, the installer will prompt before initiating restart.

/forcerestart When combined with /quiet, the installer will forcefully close applications and initiate restart. /log: Enables logging to specified file. /extract: Extracts the package contents to the destination folder.

/uninstall /kb: Uninstalls the security update. Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article,. The security update for MSXML 4.0 supports the following setup switches: Supported Security Update Installation Switches Switch Description /help Displays the command-line options. Setup Modes /qn b r f or /quiet Sets user interface level. N - No user interaction b - Basic user interaction r - Reduced user interaction f - Full user interaction (default) 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. /promptrestart Displays a dialog box prompting the local user to allow a restart.

Logging Options /li w e a r u c m o p v x + !. i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file!

- Flush each line to the log. Log all information, except for v and x options /log Equivalent of /l. 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.

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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. Click Start and then enter an update file name in the Search box.

When the file appears under Programs, right-click the file name and click Properties. On the General tab, compare the file size with the file information tables provided in the bulletin KB article. Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 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. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2008 R2 (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.

Registry Key Verification For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008 R2: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008 R2: HKEYLOCALMACHINE SOFTWARE Microsoft Updates MSXML4SP3 Q2758694 For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008 R2: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. Deployment Information Installing the Update When you install this security update, the installer checks whether 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. The security updates for MSXML 3.0 and MSXML 6.0 support 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. /warnrestart: When combined with /quiet, the installer will warn the user before initiating restart.

/promptrestart When combined with /quiet, the installer will prompt before initiating restart. /forcerestart When combined with /quiet, the installer will forcefully close applications and initiate restart. /log: Enables logging to specified file. /extract: Extracts the package contents to the destination folder. /uninstall /kb: Uninstalls the security update. Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article,. The security update for MSXML 4.0 supports the following setup switches: Supported Security Update Installation Switches Switch Description /help Displays the command-line options.

Setup Modes /qn b r f or /quiet Sets user interface level. N - No user interaction b - Basic user interaction r - Reduced user interaction f - Full user interaction (default) 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. /promptrestart Displays a dialog box prompting the local user to allow a restart. Logging Options /li w e a r u c m o p v x + !. i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file! - Flush each line to the log.

Log all information, except for v and x options /log Equivalent of /l. 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.

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 editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. Click Start and then enter an update file name in the Start Search box. When the file appears under Programs, right-click the file name and click Properties.

On the General tab, compare the file size with the file information tables provided in the bulletin KB article. Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

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. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. Windows 8 (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. Registry Key Verification For Microsoft XML Core Services 3.0 on all supported editions of Windows 8: Note A registry key does not exist to validate the presence of this update.

Use WMI to detect for the presence of this patch. For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 8: HKEYLOCALMACHINE SOFTWARE Microsoft Updates MSXML4SP3 Q2758694 For Microsoft XML Core Services 6.0 on all supported editions of Windows 8: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. Deployment Information Installing the Update When you install this security update, the installer checks whether 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. The security updates for MSXML 3.0 and MSXML 6.0 support 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. /warnrestart: When combined with /quiet, the installer will warn the user before initiating restart. /promptrestart When combined with /quiet, the installer will prompt before initiating restart. /forcerestart When combined with /quiet, the installer will forcefully close applications and initiate restart. /log: Enables logging to specified file.

/extract: Extracts the package contents to the destination folder. /uninstall /kb: Uninstalls the security update. Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article,.

The security update for MSXML 4.0 supports the following setup switches: Supported Security Update Installation Switches Switch Description /help Displays the command-line options. Setup Modes /qn b r f or /quiet Sets user interface level. N - No user interaction b - Basic user interaction r - Reduced user interaction f - Full user interaction (default) 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. /promptrestart Displays a dialog box prompting the local user to allow a restart. Logging Options /li w e a r u c m o p v x + !.

i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file! - Flush each line to the log. Log all information, except for v and x options /log Equivalent of /l. 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. Verifying That the Update Has Been Applied. File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.

Click Start and then enter an update file name in the Search box. When the file appears under Programs, right-click the file name and click Properties. On the General tab, compare the file size with the file information tables provided in the bulletin KB article. Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

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. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Windows Server 2012 (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.

Registry Key Verification For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2012: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012: HKEYLOCALMACHINE SOFTWARE Microsoft Updates MSXML4SP3 Q2758694 For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2012: Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch.

Deployment Information Installing the Update When you install this security update, the installer checks whether 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. The security updates for MSXML 3.0 and MSXML 6.0 support 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.

/warnrestart: When combined with /quiet, the installer will warn the user before initiating restart. /promptrestart When combined with /quiet, the installer will prompt before initiating restart. /forcerestart When combined with /quiet, the installer will forcefully close applications and initiate restart.

/log: Enables logging to specified file. /extract: Extracts the package contents to the destination folder. /uninstall /kb: Uninstalls the security update.

Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article,. The security update for MSXML 4.0 supports the following setup switches: Supported Security Update Installation Switches Switch Description /help Displays the command-line options. Setup Modes /qn b r f or /quiet Sets user interface level. N - No user interaction b - Basic user interaction r - Reduced user interaction f - Full user interaction (default) 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. /promptrestart Displays a dialog box prompting the local user to allow a restart. Logging Options /li w e a r u c m o p v x + !. i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file! - Flush each line to the log. Log all information, except for v and x options /log Equivalent of /l. 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. Verifying That the Update Has Been Applied. File Version Verification Because there are several editions of Microsoft Windows, the following steps may be different on your system.

If they are, see your product documentation to complete these steps. Click Start and then enter an update file name in the Start Search box. When the file appears under Programs, right-click the file name and click Properties. On the General tab, compare the file size with the file information tables provided in the bulletin KB article. Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 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.

Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. Windows RT (all editions) The following table contains the security update information for this software. Inclusion in Future Service Packs The update for this issue will be included in a future service pack or update rollup.

Deployment This update is available via. Restart Requirement Restart required? Yes, you must restart your system after you apply this security update. Removal Information Click Control Panel, click System and Security, and then under Windows Update, click Installed updates and select from the list of updates. File Information See the following. Office 2003 (all editions) Reference Table The following table contains the security update information for this software. You can find additional information in the Deployment Information subsection below.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. Deployment Installing without user intervention For Microsoft XML Core Services 5.0 when installed with Microsoft Office 2003 Service Pack 3: office2003-kb2760574-fullfile-enu.exe /q:a Installing without restarting For Microsoft XML Core Services 5.0 when installed with Microsoft Office 2003 Service Pack 3: office2003-kb2760574-fullfile-enu.exe /r:n Update log file Not applicable Further information For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. For features you can selectively install, see the Office Features for Administrative Installations subsection in this section. Restart Requirement Restart required? In some cases, this update does not require a restart. If the required files are being used, this update will require a restart.

If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see. HotPatching Not applicable Removal Information Use Add or Remove Programs item in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive.

Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see. File Information See Registry Key Verification Not applicable Office Features The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features: Product Feature ACCESSRT, OUTLS11, VISVEA, RMS, BASIC11, FP11, ONOTE11, OUTLSM11, PERS11, PUB11, STDP11, STD11, INF11, PRJPROE, PRJPRO, PRJSTDE, PRJSTD, VISPRO, VISPROR, VISSTD, VISSTDR ProductNonBootFiles PPT11, ACC11, OUTL11, PRO11SB, PROI11, PRO11, WORD11, EXCEL11 ProductNonBootFiles,LISTFiles Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The also provides more information about the parameters supported by Windows Installer.

Deployment Information Installing the Update You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection. This security update requires that Windows Installer 2.0 or later version be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version. To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft websites:.

Msxml Parser

For more information about the terminology that appears in this bulletin, such as hotfix, see. This security update supports the following setup switches. Supported Security Update Installation Switches Switch Description /q Specifies quiet mode, or suppresses prompts, when files are being extracted. /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. /t:path Specifies the target folder for extracting files. /c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. /c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or.exe file.

/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 system after installation without prompting the user. /n:v No version checking - Install the program over any earlier version. 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. Removing the Update To remove this security update, use the Add or Remove Programs item in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel.

There are several possible causes for this issue. For more information about the removal, see. 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 editions of Microsoft Windows, the following steps may be different on your system.

If they are, see your product documentation to complete these steps. Click Start and then enter an update file name in the Start Search box.

When the file appears under Programs, right-click the file name and click Properties. On the General tab, compare the file size with the file information tables provided in the bulletin KB article. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.

Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. Office 2007, Office Compatibility Pack, Word Viewer, Expression Web, and Expression Web 2 (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.