Detection and deployment tools and guidance
Security Central
Manage the software and security updates that you have to deploy to the servers, desktop, and mobile systems in your organization. For more information, see the
TechNet Update Management Center. The
Microsoft TechNet Security website provides additional information about security in Microsoft products.
Security updates are available from
Microsoft Update and
Windows 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. This includes security updates, drivers and service packs. For more information about the Microsoft Update Catalog, see the
Microsoft Update Catalog FAQ.
Detection and deployment guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see
Microsoft Knowledge Base article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates and also common security misconfigurations. For more information, see
Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|
| Windows 8 for 32-bit Systems | No |
| Windows 8 for 64-bit Systems | No |
| Windows Server 2012 | No |
Customers who use legacy software that is not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, should see
Microsoft Baseline Security Analyzer and reference the "Legacy Product Support" section to find information about how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates by using Windows Server Update Services, see the TechNet article,
Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2003 with ITMU | System Center Configuration Manager |
|---|
| Windows 8 for 32-bit Systems | No | Yes |
| Windows 8 for 64-bit Systems | No | Yes |
| Windows Server 2012 | No | Yes |
Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to
System Center Configuration Manager. For customers remaining on SMS 2003 Service Pack 3, the
Inventory Tool for Microsoft Updates (ITMU) is also an option.
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. For more information about SMS scanning tools, see
SMS 2003 Software Update Scanning Tools. See also
Downloads for Systems Management Server 2003.
System Center Configuration Manager uses WSUS 3.0 for detection of updates. For more information, see
System Center.
For detailed information, see
Microsoft Knowledge Base article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility ToolkitUpdates frequently write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time that is required to deploy security updates. You can streamline testing and validating Windows updates against installed applications by using the
Update Compatibility Evaluator components that are included with
Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and lessen application compatibility issues before you deploy Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
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.
| Inclusion in future service packs | The update for this issue will be included in a future service pack or update rollup |
|---|
| Deployment | |
| Installing without requiring user intervention | For Adobe Flash Player in Internet Explorer 10 on all supported 32-bit editions of Windows 8:
Windows8-RT-KB2758994-x86.msu /quiet |
| For Adobe Flash Player in Internet Explorer 10 on all supported 64-bit editions of Windows 8:
Windows8-RT-KB2758994-x64.msu /quiet |
| Installing without restarting | For Adobe Flash Player in Internet Explorer 10 on all supported 32-bit editions of Windows 8:
Windows8-RT-KB2758994-x86.msu /quiet /norestart
|
| For Adobe Flash Player in Internet Explorer 10 on all supported x64-bit editions of Windows 8:
Windows8-RT-KB2758994-x64.msu /quiet /norestart |
| Additional information | See the Detection and deployment tools and guidance subsection. |
| 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, you receive a message that advises you to restart.
To help reduce the possibility that a restart will be required, stop all affected services and close all applications that may use the affected files before installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable. |
| Removal information | To uninstall an update installed by WUSA, use the /Uninstall setup switch. Or, click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
| Registry key verification | Note A registry key does not exist to validate the presence of this update. |
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 Knowledge Base Article, 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 it is combined with/quiet, the system is not restarted after installation even if a restart is required to complete installation. |
| /warnrestart:<seconds> | When it is combined with /quiet, the installer warns the user before it begins the restart. |
| /promptrestart | When it is combined with /quiet, the installer prompts before it begins restart. |
| /forcerestart | When it is combined with /quiet, the installer forcibly closes applications and begins the restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB number> | Uninstalls the security update. |
For more information about the Wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article,
Miscellaneous Changes in Windows 7.
Verifying that the update was applied
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.
File version verification- Click Start, and then type an update file name in the Search box.
- When the file appears under Programs, right-click the file name, and then click Properties.
- On the General tab, compare the file size with the file information tables that are provided in the Microsoft Knowledge Base 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 Microsoft Knowledge Base 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 was 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 together 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.
| Inclusion in future service packs | The update for this issue will be included in a future service pack or update rollup |
|---|
| Deployment | |
| Installing without requiring user intervention | For Adobe Flash Player in Internet Explorer 10 on all supported editions of Windows Server 2012:
Windows8-RT-KB2758994-x64.msu /quiet
|
| Installing without restarting | For Adobe Flash Player in Internet Explorer 10 on all supported editions of Windows Server 2008 R2:
Windows8-RT-KB2758994-x64.msu /quiet /norestart
|
| Additional information | See the Detection and deployment tools and Guidance subsection. |
| 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, you receive a message that advises you to restart.
To help reduce the possibility that a restart will be required, stop all affected services and close all applications that may use the affected files before installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base article 887012.
|
| HotPatching | Not applicable. |
| Removal information | To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates. |
| Registry key verification |
Note A registry key does not exist to validate the presence of this update. |
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 Knowledge Base article, 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 it is combined with/quiet, the system is not restarted after installation even if a restart is required to complete installation. |
| /warnrestart:<seconds> | When it is combined with /quiet, the installer warns the user before it begins the restart. |
| /promptrestart | When it is combined with /quiet, the installer prompts before it begins restart. |
| /forcerestart | When it is combined with /quiet, the installer forcibly closes applications and begins the restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB number> | Uninstalls the security update. |
For more information about the Wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article,
Miscellaneous Changes in Windows 7.
Verifying That the Update Was Applied
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.
File Version Verification- Click Start, and then type an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and then click Properties.
- On the General tab, compare the file size with the file information tables provided in the Microsoft Knowledge Base 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 Microsoft Knowledge Base 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 was 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 together with the file information for the new, or updated, version of the file.
