Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

MS16-093: Security update for Adobe Flash Player: July 12, 2016


View products that this article applies to.

Summary

This update resolves vulnerabilities in Adobe Flash Player when it is installed on all supported editions of Windows Embedded 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows RT 8.1, Windows 10, and Windows 10 Version 1511.

To learn more about the vulnerability, see Microsoft Security Bulletin MS16-093.

↑ Back to the top


More Information

Important
  • All future security and non-security updates for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 require update 2919355 to be installed. We recommend that you install update 2919355 on your Windows RT 8.1-based, Windows 8.1-based, or Windows Server 2012 R2-based computer so that you receive future updates.
  • If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
  • This security update applies to the Windows operating systems that are listed in the "Applies to" section in this article. If you want to install Adobe Flash Player update on an earlier version of Windows, try Adobe Flash Player Download.

↑ Back to the top


How to obtain and install the update

Method 1: Windows Update

This update is available through Windows Update. When you turn on automatic updating, this update will be downloaded and installed automatically. For more information about how to turn on automatic updating, see
Get security updates automatically.

Note For Windows RT 8.1, this update is available through Windows Update only.
 

Method 2: Microsoft Download Center

You can obtain the stand-alone update package through the Microsoft Download Center. Follow the installation instructions on the download page to install the update.

Click the download link in Microsoft Security Bulletin MS16-093 that corresponds to the version of Windows that you are running.

↑ Back to the top


More Information

Detection and deployment tools and guidance

Security Central

You can manage the software and security updates that you have to deploy to the servers, desktops, and mobile systems in your organization. For more information, see the TechNet Update Management Center. The
Microsoft TechNet Security website provides more 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 security updates most easily by doing a keyword search for "security update."

You can download security updates from the
Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content that is 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 common security misconfigurations. For more information, see
Microsoft Baseline Security Analyzer.

Note Customers who use legacy software that is not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services should see the "Legacy Product Support" section of
Microsoft Baseline Security Analyzer. Here, they will find information about how to create comprehensive security update detection by using legacy tools.

Windows Server Update Services

Windows Server Update Services (WSUS) lets information technology administrators deploy the latest Microsoft product updates to computers that are running Windows. For more information about how to deploy security updates by using Windows Server Update Services, see the following Microsoft TechNet topic:

Systems Management Server

The following table provides the Microsoft Systems Management Server (SMS) detection and deployment summary for this security update.


SoftwareSMS 2003 with ITMUSystem Center Configuration Manager
Windows 8.1 for 32-bit systems NoYes
Windows 8.1 for 64-bit systemsNoYes
Windows Server 2012 and Windows Server 2012 R2NoYes
Note 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 who remain 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, see Systems Management Server 2003. For more information about SMS scanning tools, see
Systems Management Server 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 Toolkit

Updates frequently write to the same files and registry settings that are required for your applications to run. This can trigger incompatibilities and increase the time that is required to deploy security updates. You can streamline the testing and validation of Windows updates against installed applications by using the Update Compatibility Evaluator components that are included in the Application Compatibility Toolkit.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and decrease 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.1 (all editions)

Reference table
The following table contains the security update information for this software. You can find more information in the "Deployment information" section.


DeploymentInformation
For Adobe Flash Player in Internet Explorer 11 on all supported 32-bit editions of Windows 8.1:
Windows8.1-KB3174060-x86.msu /quiet
For Adobe Flash Player in Internet Explorer 11 on all supported x64-based editions of Windows 8.1:
Windows8.1-KB3174060-x64.msu /quiet
For Adobe Flash Player in Internet Explorer 11 on all supported 32-bit editions of Windows 8.1:

Windows8.1-KB3174060-x86.msu /quiet /norestart
For Adobe Flash Player in Internet Explorer 11 on all supported x64-based editions of Windows 8.1:

Windows8.1-KB3174060-x64.msu /quiet /norestart
More informationSee the "Detection and deployment tools and guidance" subsection.
Restart requirementIn some cases, this update does not require a restart. If the required files are being used, this update requires 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, you should stop all affected services and close all applications that may use the affected files before you install the security update. For more information about why you may be prompted to restart, see
Microsoft Knowledge Base article 887012.
HotpatchingNot applicable
Removal informationTo uninstall an update that was installed by WUSA, use the /Uninstall setup switch. Or, click Control Panel, click System and Security, click View installed updates under Windows Update, and then select from the list of updates.
Registry key verificationThere is no registry key to validate the presence of this update.
Inclusion in future service packsThe update for this issue will be included in a future service pack or update rollup.

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 installation switches.


SwitchDescription
/?, /h, /helpDisplays help about supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen 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.
/promptrestartWhen it is combined with /quiet, the installer prompts before it begins restart.
/forcerestartWhen it is combined with /quiet, the installer forcibly closes applications and begins the restart.
/log:<file name>Enables logging to the specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB number>Uninstalls the security update.
Note For more information about the Wusa.exe installer, see the "Windows Update Stand-alone Installer" section in the TechNet article
Miscellaneous Changes in Windows 7.
Verifying that the update was applied
Because there are several editions of Windows, the following steps may be different on your system. If they are different, see your product documentation to complete these steps.

Verifying the file version
  1. Click Start, and then type an update file name in the Search box.
  2. When the file appears under Programs, right-click the file name, and then click Properties.
  3. On the General tab, compare the file size to that listed in the file information tables that are provided in this 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.
  4. You can also click the Details tab to compare information, such as file version and date changed, to that in the file information tables that are 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 are renamed during installation. If the file or version information does not exist, use one of the other available methods to verify update installation.
  5. You can also click the Previous Versions tab to compare file information for the earlier version of the file together with the file information for the new, or updated, version of the file.

Windows Server 2012 and Windows Server 2012 R2 (all editions)

Reference table
The following table contains the security update information for this software. You can find more information in the "Deployment information" subsection in this section.


DeploymentInformation
Installing without requiring user interventionFor Adobe Flash Player in Internet Explorer 10 on all supported editions of Windows Server 2012:
Windows8-RT-KB3174060-x64.msu /quiet
For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2:

Windows8.1-KB3174060-x64.msu /quiet
Installing without restartingFor Adobe Flash Player in Internet Explorer 10 on all supported editions of Windows Server 2012:
Windows8-RT-KB3174060-x64.msu /quiet /norestart
For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2:

Windows8.1-KB3174060-x64.msu /quiet /norestart
More informationSee the "Detection and deployment tools and Guidance" subsection.
Restart requirementIn some cases, this update does not require a restart. If the required files are being used, this update requires 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, you should stop all affected services and close all applications that may use the affected files before you install the security update. For more information about why you may be prompted to restart, see
Microsoft Knowledge Base article 887012.
HotpatchingNot applicable
Removal informationTo uninstall an update that was installed by WUSA, use the /Uninstall setup switch. Or, click Control Panel, click System and Security, click View installed updates under Windows Update, and then select from the list of updates.
Registry key verification

There is no registry key to validate the presence of this update.
Inclusion in future service packsThe update for this issue will be included in a future service pack or update rollup.

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 were previously 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 installation switches.


SwitchDescription
/?, /h, /helpDisplays help about supported switches.
/quietSuppresses the display of status or error messages.
/norestartWhen it is combined with/quiet, the system does not restart after the 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.
/promptrestartWhen it is combined with /quiet, the installer prompts the user before it begins the restart.
/forcerestartWhen it is combined with /quiet, the installer forcibly closes applications and begins the restart.
/log:<file name>Enables logging to the specified file.
/extract:<destination>Extracts the package contents to the destination folder.
/uninstall /kb:<KB number>Uninstalls the security update.

Note
For more information about the Wusa.exe installer, see "Windows Update Stand-alone Installer" in the following Microsoft TechNet topic:
Verifying that the update was applied
Because there are several editions of Windows, the following steps may be different on your system. If they are different, see your product documentation to complete these steps.

Verifying the file version
  1. Click Start, and then type an update file name in the Start Search box.
  2. When the file appears under Programs, right-click the file name, and then click Properties.
  3. On the General tab, compare the file size to that in the file information tables that are provided in the Knowledge Base article.

    Note Depending on the edition of the operating system or the programs that are installed in your system, some files that are listed in the file information table may not be installed.
  4. You can also click the Details tab to compare information, such as file version and date changed, to that in the file information tables that are provided in the 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 does not exist, use one of the other available methods to verify update installation.
  5. You can also click the Previous Versions tab, and then compare file information for the earlier version of the file together with the file information for the new or updated version of the file.

How to obtain help and support for this security update
Help for installing updates: Support for Microsoft Update

Security solutions for IT professionals: TechNet Security Troubleshooting and Support

Help for protecting your Windows-based computer from viruses and malware: Virus Solution and Security Center

Local support according to your country: International Support

↑ Back to the top


File Information

File hash information
File nameSHA1 hashSHA256 hash
Windows8.1-KB3174060-x86.msu9B5E0CB7F05A62A5503D2C1FE51E04CABB0B2508802722ECC310C0DFB44ACD177270D80DA1698006578B3C9194923FF0C81F6C12
Windows8.1-KB3174060-x64.msuE664044BE81E1E878D304D245F40842843FCBC2E2708EB5AD4EF8F79916F6D9EC7E13C45ECA949E4DAD5928E57E7D07DCB74F147
Windows8-RT-KB3174060-x86-custom.msu12044391AE1408DF26344903CA0D67F5314064B3A5087F10CF4DB78205BFAE8731BB53498609DD93C07D9AB399B687FC2E973A93
Windows8-RT-KB3174060-x64-custom.msuC3F8877EF07286269BBE7CE49428C098ABEC4B0333AC2FBB348C17286D5788E2112BAA024059F25C3ED049A64BA077EB3AE20135

File information
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables.

Windows 8.1 and Windows Server 2012 R2 file information

Notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductMilestoneService branch
    6.3.960 0.16xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
    6.3.960 0.17xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
    6.3.960 0.18xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and MUM files (.mum) that are installed are not listed.
For all supported x86-based versions
File nameFile versionFile sizeDateTimePlatform
Activex.vchNot applicable729,18602-Jul-201604:29Not applicable
Flash.ocx22.0.0.20921,638,12802-Jul-201604:29x86
Flashplayerapp.exe22.0.0.209828,40802-Jul-201604:29x86
Flashplayercplapp.cpl22.0.0.209176,63202-Jul-201604:29Not applicable
Flashutil_activex.dll22.0.0.209607,22402-Jul-201604:29x86
Flashutil_activex.exe22.0.0.2091,281,01602-Jul-201604:29x86
For all supported x64-based versions
File nameFile versionFile sizeDateTimePlatform
Activex.vchNot applicable159,49402-Jul-201604:29Not applicable
Flash.ocx22.0.0.20928,026,36002-Jul-201604:29x64
Flashutil_activex.dll22.0.0.209687,60802-Jul-201604:29x64
Flashutil_activex.exe22.0.0.209921,59202-Jul-201604:29x64
Activex.vchNot applicable729,18602-Jul-201604:29Not applicable
Flash.ocx22.0.0.20921,638,12802-Jul-201604:29x86
Flashplayerapp.exe22.0.0.209828,40802-Jul-201604:29x86
Flashplayercplapp.cpl22.0.0.209176,63202-Jul-201604:29Not applicable
Flashutil_activex.dll22.0.0.209607,22402-Jul-201604:29x86
Flashutil_activex.exe22.0.0.2091,281,01602-Jul-201604:29x86

Windows Embedded 8 and Windows Server 2012 file information

For all supported x86-based versions of Windows Embedded 8
File nameFile versionFile sizeDateTimePlatform
Activex.vchNot applicable729,18602-Jul-201604:32Not applicable
Flash.ocx22.0.0.20921,637,60002-Jul-201604:32x86
Flashplayerapp.exe22.0.0.209827,86402-Jul-201604:32x86
Flashplayercplapp.cpl22.0.0.209176,09602-Jul-201604:32Not applicable
Flashutil_activex.dll22.0.0.209606,68002-Jul-201604:32x86
Flashutil_activex.exe22.0.0.2091,280,47202-Jul-201604:32x86
For all supported x64-based versions of Windows Embedded 8 and Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Activex.vchNot applicable159,49402-Jul-201604:32Not applicable
Flash.ocx22.0.0.20928,025,82402-Jul-201604:32x64
Flashutil_activex.dll22.0.0.209687,07202-Jul-201604:32x64
Flashutil_activex.exe22.0.0.209921,05602-Jul-201604:32x64
Activex.vchNot applicable729,18602-Jul-201604:32Not applicable
Flash.ocx22.0.0.20921,637,60002-Jul-201604:32x86
Flashplayerapp.exe22.0.0.209827,86402-Jul-201604:32x86
Flashplayercplapp.cpl22.0.0.209176,09602-Jul-201604:32Not applicable
Flashutil_activex.dll22.0.0.209606,68002-Jul-201604:32x86
Flashutil_activex.exe22.0.0.2091,280,47202-Jul-201604:32x86

↑ Back to the top


Keywords: atdownload, kbbug, kbexpertiseinter, kbfix, kblangall, kbmustloc, kbsecbulletin, kbsecreview, kbsecurity, kbsecvulnerability, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 3174060
Revision : 5
Created on : 4/13/2020
Published on : 4/16/2020
Exists online : False
Views : 948