MS16-127: Security update for Adobe Flash Player: October 11, 2016

Summary

This security update resolves vulnerabilities in Adobe Flash Player when installed on all supported editions of Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows RT 8.1, and Windows 10.


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

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.

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 Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

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-127 that corresponds to the version of Windows that you are running.

More Information



Security CentralYou 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 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 guidanceMicrosoft 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 AnalyzerMicrosoft 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 ServicesWindows 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:

Windows Server Update Services

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


Software

SMS 2003 with ITMU

System Center Configuration Manager

Windows 8.1 for 32-bit systems

No

Yes

Windows 8.1 for 64-bit systems

No

Yes

Windows Server 2012 and Windows Server 2012 R2

No

Yes

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 SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are supported by
Windows Server Update Services. For more information, see 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 (ACT).

The Application Compatibility Toolkit 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.



Windows 8.1 (all editions)

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


Deployment

Information

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

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

For Adobe Flash Player in Internet Explorer 11 on all supported 32-bit editions of Windows 8.1:

Windows8.1-KB3194343-x86.msu /quiet /norestart

For Adobe Flash Player in Internet Explorer 11 on all supported x64-based editions of Windows 8.1:

Windows8.1-KB3194343-x64.msu /quiet /norestart

More information

See the "Detection and deployment tools and guidance" subsection.

Restart requirement

In 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.

Hotpatching

Not applicable

Removal information

To 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 packs

The update for this issue will be included in a future service pack or update rollup.



Deployment information

Installing the updateWhen 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.


Switch

Description

/?, /h, /help

Displays help about 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 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 appliedBecause 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 tableThe following table contains the security update information for this software. You can find more information in the "Deployment information" subsection in this section.


Deployment

Information

Installing without requiring user intervention

For Adobe Flash Player in Internet Explorer 10 on all supported editions of Windows Server 2012:
Windows8-RT-KB3194343-x64.msu /quiet

For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2:

Windows8.1-KB3194343-x64.msu /quiet

Installing without restarting

For Adobe Flash Player in Internet Explorer 10 on all supported editions of Windows Server 2012:
Windows8-RT-KB3194343-x64.msu /quiet /norestart

For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2:

Windows8.1-KB3194343-x64.msu /quiet /norestart

More information

See the "Detection and deployment tools and Guidance" subsection.

Restart requirement

In 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.

Hotpatching

Not applicable

Removal information

To 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 packs

The update for this issue will be included in a future service pack or update rollup.



Deployment information

Installing the updateWhen 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.


Switch

Description

/?, /h, /help

Displays help about supported switches.

/quiet

Suppresses the display of status or error messages.

/norestart

When 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.

/promptrestart

When it is combined with /quiet, the installer prompts the user before it begins the restart.

/forcerestart

When 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:

Miscellaneous Changes in Windows 7

Verifying that the update was appliedBecause 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.


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

File Information

File name

SHA1 hash

SHA256 hash

Windows10.0-KB3194343-x64.msu (Windows Server 2016 TP5)

3F767A3CC52BCA67528063AEA60A50BB761822DB

575292C62B257FE9A5AFBBF4916D293E7673046423B6347699A0EEAE37399039

Windows10.0-KB3194343-x86.msu (Windows 10 Version 1607)

BA9C6C780D74D806D2602060245829DA86BB559F

4ECD8F4615A2D274B9D9B68653403709A1005CEAF62B7123E6DD4EE5D3E1C869

Windows10.0-KB3194343-x64.msu (Windows 10 Version 1607)

140AC14C717811CAA35C6130A8663D371028799C

D3C3B5556588DDA484D7D761E20CFB5DABF6F59060E20C7373DC1D57DA7F4C51

Windows10.0-KB3194343-x86.msu Windows 10 Version 1511

D0EAC95D56D630F8746A09DDEF50B7230018E020

DC34382EA6566272D7BDE0CDB3C333486F9B900C90393F8EDE150287B62E0B53

Windows10.0-KB3194343-x64.msu Windows 10 Version 1511

6E556F55BF94324BBE435DDF129B53DFE7CE5401

1C96F6EB8F8428CB563085301F0EA6795F1D32068AFBF9264592331FEE6F7C19

Windows10.0-KB3194343-x86.msu

5DEAB91CD3DCDB8F5E8C1CD7D317A409BB06A6FC

AE22E2E7B5ED8FA2E2A4A194F23A8DB603DE7B9EC82198BB28ACD889E48DEAD4

Windows10.0-KB3194343-x64.msu

A751756BB2BE040273F9D1B1B61A7634610993BF

6F32153F20A588BF600044CB3DE392DDF6348568F0CD179157B78C43420E74D7

Windows8.1-KB3194343-arm.msu

F3E939417F1D00031AB6E3947599D7F5D9E9EBD9

3A66E1E78BB54B528BB3D8C201682B9678BFD5E968E38008F9D65FA46ED4D196

Windows8.1-KB3194343-x86.msu

3B3CA0DD5318E000DDAF6BDF1A1CF45491B02690

EC858394381BD1A84967F38D840BF7146873AE84D12609B3AFBB27A7ED8D388F

Windows8.1-KB3194343-x64.msu

D3566481791EF6A5B0F9EF734456328E4A156D91

C2646B5023C586FCACD80C18CD4E685D4DC44963A4372D603BE329BCA65241EC


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

Windows Server 2016 TP5 file information

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,494

03-Oct-2016

20:09

Not applicable

Flash.ocx

23.0.0.185

28,198,392

03-Oct-2016

20:09

x64

Flashutil_activex.dll

23.0.0.185

689,144

03-Oct-2016

20:09

x64

Flashutil_activex.exe

23.0.0.185

934,392

03-Oct-2016

20:09

x64

Activex.vch

Not applicable

736,486

03-Oct-2016

20:09

Not applicable

Flash.ocx

23.0.0.185

21,787,640

03-Oct-2016

20:09

x86

Flashplayerapp.exe

23.0.0.185

828,408

03-Oct-2016

20:09

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

03-Oct-2016

20:09

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

03-Oct-2016

20:09

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

03-Oct-2016

20:09

x86

Windows 10 Version 1607 file information

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,486

03-Oct-2016

20:09

Not applicable

Flash.ocx

23.0.0.185

21,787,640

03-Oct-2016

20:09

x86

Flashplayerapp.exe

23.0.0.185

828,408

03-Oct-2016

20:09

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

03-Oct-2016

20:09

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

03-Oct-2016

20:09

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

03-Oct-2016

20:09

x86

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,494

03-Oct-2016

20:09

Not applicable

Flash.ocx

23.0.0.185

28,198,392

03-Oct-2016

20:09

x64

Flashutil_activex.dll

23.0.0.185

689,144

03-Oct-2016

20:09

x64

Flashutil_activex.exe

23.0.0.185

934,392

03-Oct-2016

20:09

x64

Activex.vch

Not applicable

736,486

03-Oct-2016

20:09

Not applicable

Flash.ocx

23.0.0.185

21,787,640

03-Oct-2016

20:09

x86

Flashplayerapp.exe

23.0.0.185

828,408

03-Oct-2016

20:09

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

03-Oct-2016

20:09

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

03-Oct-2016

20:09

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

03-Oct-2016

20:09

x86

Windows 10 Version 1511 file information

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,486

01-Oct-2016

00:23

Not applicable

Flash.ocx

23.0.0.185

21,787,640

01-Oct-2016

00:23

x86

Flashplayerapp.exe

23.0.0.185

828,408

01-Oct-2016

00:23

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

01-Oct-2016

00:23

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

01-Oct-2016

00:23

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

01-Oct-2016

00:23

x86

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,494

01-Oct-2016

00:23

Not applicable

Flash.ocx

23.0.0.185

28,198,392

01-Oct-2016

00:23

x64

Flashutil_activex.dll

23.0.0.185

689,144

01-Oct-2016

00:23

x64

Flashutil_activex.exe

23.0.0.185

934,392

01-Oct-2016

00:23

x64

Activex.vch

Not applicable

736,486

01-Oct-2016

00:23

Not applicable

Flash.ocx

23.0.0.185

21,787,640

01-Oct-2016

00:23

x86

Flashplayerapp.exe

23.0.0.185

828,408

01-Oct-2016

00:23

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

01-Oct-2016

00:23

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

01-Oct-2016

00:23

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

01-Oct-2016

00:23

x86

Windows 10 file information

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,486

01-Oct-2016

00:18

Not applicable

Flash.ocx

23.0.0.185

21,787,640

01-Oct-2016

00:18

x86

Flashplayerapp.exe

23.0.0.185

828,408

01-Oct-2016

00:18

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

01-Oct-2016

00:18

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

01-Oct-2016

00:18

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

01-Oct-2016

00:18

x86

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,494

01-Oct-2016

00:18

Not applicable

Flash.ocx

23.0.0.185

28,198,392

01-Oct-2016

00:18

x64

Flashutil_activex.dll

23.0.0.185

689,144

01-Oct-2016

00:18

x64

Flashutil_activex.exe

23.0.0.185

934,392

01-Oct-2016

00:18

x64

Activex.vch

Not applicable

736,486

01-Oct-2016

00:18

Not applicable

Flash.ocx

23.0.0.185

21,787,640

01-Oct-2016

00:18

x86

Flashplayerapp.exe

23.0.0.185

828,408

01-Oct-2016

00:18

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

01-Oct-2016

00:18

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

01-Oct-2016

00:18

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

01-Oct-2016

00:18

x86

Windows 8.1, Windows RT 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:

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.16 xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

    6.3.960 0.17 xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

    6.3.960 0.18 xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

  • 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 ARM-based versions

File name

File version

File size

Date

Time

Platform

Flash.ocx

23.0.0.185

18,763,256

01-Oct-2016

00:16

Not applicable

Flashplayerapp.exe

23.0.0.185

809,464

01-Oct-2016

00:16

Not applicable

Flashplayercplapp.cpl

23.0.0.185

162,296

01-Oct-2016

00:16

Not applicable

Flashutil_activex.dll

23.0.0.185

538,616

01-Oct-2016

00:16

Not applicable

Flashutil_activex.exe

23.0.0.185

803,320

01-Oct-2016

00:16

Not applicable

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,486

01-Oct-2016

00:15

Not applicable

Flash.ocx

23.0.0.185

21,787,640

01-Oct-2016

00:15

x86

Flashplayerapp.exe

23.0.0.185

828,408

01-Oct-2016

00:15

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

01-Oct-2016

00:15

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

01-Oct-2016

00:16

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

01-Oct-2016

00:16

x86

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,494

01-Oct-2016

00:16

Not applicable

Flash.ocx

23.0.0.185

28,198,392

01-Oct-2016

00:16

x64

Flashutil_activex.dll

23.0.0.185

689,144

01-Oct-2016

00:16

x64

Flashutil_activex.exe

23.0.0.185

934,392

01-Oct-2016

00:16

x64

Activex.vch

Not applicable

736,486

01-Oct-2016

00:15

Not applicable

Flash.ocx

23.0.0.185

21,787,640

01-Oct-2016

00:15

x86

Flashplayerapp.exe

23.0.0.185

828,408

01-Oct-2016

00:15

x86

Flashplayercplapp.cpl

23.0.0.185

176,632

01-Oct-2016

00:15

Not applicable

Flashutil_activex.dll

23.0.0.185

608,248

01-Oct-2016

00:16

x86

Flashutil_activex.exe

23.0.0.185

1,296,888

01-Oct-2016

00:16

x86


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×