Applies ToWindows Server 2016 Windows Server 2016 Essentials Windows Server 2016 Standard Windows Server 2016, all editions Windows 10 Windows 10, version 1511, all editions Windows 10, version 1607, all editions Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows 8.1 Enterprise Windows 8.1 Pro Windows 8.1 Windows RT 8.1 Windows Server 2012 Datacenter Windows Server 2012 Standard Windows Server 2012 Essentials Windows Server 2012 Foundation

Summary

This security update resolves vulnerabilities in Adobe Flash Player if it is installed on any supported edition of Windows Server 2012, Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 10, Windows 10 Version 1511, Windows 10 Version 1607, or Windows Server 2016. To learn more about the vulnerability, see Microsoft Security Bulletin MS16-141.

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

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. 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 to detect updates. For more information, see System Center. For more 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 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-KB3202790-x86.msu /quiet

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

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

For Adobe Flash Player in Internet Explorer 11 on all supported x64-based editions of Windows 8.1:Windows8.1-KB3202790-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, seeMicrosoft 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, such as "hotfix," that appears in this Knowledge Base article, 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 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 the "Windows Update Stand-alone Installer" section in the following 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 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 the size that is listed in the file information tables that are provided in this 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 such information as file version and date changed to the information that is listed 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 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 to 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-KB3202790-x64.msu /quiet

For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2:Windows8.1-KB3202790-x64.msu /quiet

Installing without restarting

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

For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2:Windows8.1-KB3202790-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, such as "hotfix," that appears in this Knowledge Base article, 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 the file size that is listed 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 such information as file version and date changed to the information that is listed 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 to the file information for the new or updated version of the file.

Help for installing updates: Support for Microsoft UpdateSecurity solutions for IT professionals: TechNet Security Troubleshooting and SupportHelp for protecting your Windows-based computer from viruses and malware: Virus Solution and Security CenterLocal support according to your country: International Support

File Information

File name

SHA1 hash

SHA256 hash

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

4CBA6AEF7A4CC6798DD0CFF2B6BA8D65BA9FD0A7

87D58EFA62256E94F24835E7B8CEE17586A1B63D9E9F77D6A8A5D57DB50C585F

Windows10.0-KB3202790-x64.msu (Windows 10 Version 1607 and Windows Server 2016)

C1E4507C7EBBE93DA3EB5D1E362E6A9F2A0333F8

4AE38E8F37677F789032F69662F85043846A37B3863ED2D610296A48E842E51F

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

522641B4A6CFA07086A4689D3504F9CE5692836E

97F09F86E56574EFE9B44A65EB89694705657394EC1EA1E71EBAC45B5254FEC8

Windows10.0-KB3202790-x64.msu (Windows 10 Version 1511)

DE9CB338C95B319B25AC87B27727329F32C1DD66

891F076614F79250CDE40AA6788948BDE3F6FFDD27900F5C686B79490802D09A

Windows10.0-KB3202790-x86.msu (Windows 10 Version 1511)

7A5462F9D8F20F7C5BD167C91324A17727396F18

F42C2D97C8589C179B715A2479B5060E1505CEE3D29D622E9E473AAD2C57AE0D

Windows10.0-KB3202790-x64.msu (Windows 10 RTM)

4AF46A5DFC33E027B6254EC06EB92B047CD55090

5D3533428ADED7A45B57B108198BB8B98EA27C8839ADA943479D4F45DFD832A0

Windows10.0-KB3202790-x86.msu (Windows 10 RTM)

96A49918EF109BE2B99DEF3C1C929736203C7FC0

556CCEC8F69EFFE7EA2F1569F4A797D98B5517909C0B2E6C341961833297C9F0

Windows8.1-KB3202790-x64.msu

7B1B81FB443FCC4ED5E06B8E66BB383CE0DCA3FD

F1D1B4D9ED9C74B0D1DF9C6FF1FDB17989F2115E88F91E599AD43121F6E85D33

Windows8.1-KB3202790-x86.msu

A159243AD26D50AF51E92486E800429CAB8333CF

240F259615ED647D0C70F30D6860779DFC0681D84C640EE654D667A48F6FAC8A

Windows8-RT-KB3202790-x64.msu

E565E01E68ACA4B61980ED3D01DFDF0CA09FA99E

D5CEAF0DDCC5E7652F509E08284B33DA32E1BE0BC667E49E5C60B3467CDFE368

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,534

28-Oct-2016

23:46

Not applicable

Flash.ocx

23.0.0.207

28,204,024

28-Oct-2016

23:46

x64

Flashutil_activex.dll

23.0.0.207

689,144

28-Oct-2016

23:46

x64

Flashutil_activex.exe

23.0.0.207

934,392

28-Oct-2016

23:46

x64

Activex.vch

Not applicable

736,750

28-Oct-2016

23:46

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

23:46

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

23:46

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

23:46

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

23:46

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

23:46

x86

Windows 10 Version 1607 and Windows Server 2016 file information

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,534

28-Oct-2016

23:56

Not applicable

Flash.ocx

23.0.0.207

28,204,024

28-Oct-2016

23:56

x64

Flashutil_activex.dll

23.0.0.207

689,144

28-Oct-2016

23:56

x64

Flashutil_activex.exe

23.0.0.207

934,392

28-Oct-2016

23:56

x64

Activex.vch

Not applicable

736,750

28-Oct-2016

23:56

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

23:56

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

23:56

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

23:56

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

23:56

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

23:56

x86

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,750

28-Oct-2016

23:56

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

23:56

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

23:56

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

23:56

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

23:56

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

23:56

x86

Windows 10 Version 1511 file information

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,534

28-Oct-2016

21:48

Not applicable

Flash.ocx

23.0.0.207

28,204,024

28-Oct-2016

21:48

x64

Flashutil_activex.dll

23.0.0.207

689,144

28-Oct-2016

21:48

x64

Flashutil_activex.exe

23.0.0.207

934,392

28-Oct-2016

21:48

x64

Activex.vch

Not applicable

736,750

28-Oct-2016

21:48

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

21:48

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

21:48

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

21:48

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

21:48

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

21:48

x86

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,750

28-Oct-2016

21:48

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

21:48

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

21:48

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

21:48

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

21:48

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

21:48

x86

Windows 10 RTM file information

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,534

28-Oct-2016

21:06

Not applicable

Flash.ocx

23.0.0.207

28,204,024

28-Oct-2016

21:06

x64

Flashutil_activex.dll

23.0.0.207

689,144

28-Oct-2016

21:06

x64

Flashutil_activex.exe

23.0.0.207

934,392

28-Oct-2016

21:06

x64

Activex.vch

Not applicable

736,750

28-Oct-2016

21:06

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

21:06

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

21:06

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

21:06

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

21:06

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

21:06

x86

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,750

28-Oct-2016

21:06

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

21:06

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

21:06

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

21:06

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

21:06

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

21:06

x86

Windows 8.1 and Windows Server 2012 R2 file information

Notes: The MANIFEST files (.manifest) and MUM files (.mum) that are installed are not listed.

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,534

28-Oct-2016

21:04

Not applicable

Flash.ocx

23.0.0.207

28,204,024

28-Oct-2016

21:04

x64

Flashutil_activex.dll

23.0.0.207

689,144

28-Oct-2016

21:04

x64

Flashutil_activex.exe

23.0.0.207

934,392

28-Oct-2016

21:04

x64

Activex.vch

Not applicable

736,750

28-Oct-2016

21:04

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

21:04

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

21:04

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

21:04

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

21:04

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

21:04

x86

For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

736,750

28-Oct-2016

21:04

Not applicable

Flash.ocx

23.0.0.207

21,793,784

28-Oct-2016

21:04

x86

Flashplayerapp.exe

23.0.0.207

828,408

28-Oct-2016

21:04

x86

Flashplayercplapp.cpl

23.0.0.207

176,632

28-Oct-2016

21:04

Not applicable

Flashutil_activex.dll

23.0.0.207

608,248

28-Oct-2016

21:04

x86

Flashutil_activex.exe

23.0.0.207

1,296,888

28-Oct-2016

21:04

x86

Windows Server 2012 file information

Notes: The MANIFEST files (.manifest) and MUM files (.mum) that are installed are not listed.

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

160,534

28-Oct-2016

21:02

Not applicable

Flash.ocx

23.0.0.207

28,203,488

28-Oct-2016

21:02

x64

Flashutil_activex.dll

23.0.0.207

688,600

28-Oct-2016

21:02

x64

Flashutil_activex.exe

23.0.0.207

933,848

28-Oct-2016

21:02

x64

Activex.vch

Not applicable

736,750

28-Oct-2016

21:02

Not applicable

Flash.ocx

23.0.0.207

21,793,248

28-Oct-2016

21:02

x86

Flashplayerapp.exe

23.0.0.207

827,872

28-Oct-2016

21:02

x86

Flashplayercplapp.cpl

23.0.0.207

176,096

28-Oct-2016

21:02

Not applicable

Flashutil_activex.dll

23.0.0.207

607,704

28-Oct-2016

21:02

x86

Flashutil_activex.exe

23.0.0.207

1,296,352

28-Oct-2016

21:02

x86

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.