Summary

This security update resolves vulnerabilities in Adobe Flash Player if Flash Player is installed on any supported edition of Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows 10, Windows 10 Version 1511, Windows 10 Version 1607, Windows 8.1, or Windows RT 8.1.

To learn more about the vulnerability, see Microsoft Security Bulletin MS17-005.

More Information

Important

  • All future security and nonsecurity updates for Windows Server 2012 R2, Windows 8.1, and Windows RT 8.1 require update 2919355 to be installed. We recommend that you install update 2919355 on your Windows Server 2012 R2-based, Windows 8.1-based, or Windows RT 8.1-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 get security updates automatically, see Windows Update: FAQ.

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, or Windows Server Update Services should see the "Legacy Product Support" section of Microsoft Baseline Security Analyzer. Here, you can 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 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 address 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-KB4010250-x86.msu /quiet

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

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

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

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

Windows8.1-KB4010250-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, 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-KB4010250-x64.msu /quiet

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

Windows8.1-KB4010250-x64.msu /quiet

Installing without restarting

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

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

Windows8.1-KB4010250-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 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 hash information

File name

SHA1 hash

SHA256 hash

Windows8-RT-KB4010250-x64.msu

A1C3DE6599809334D3EC807502A322E2B35F4C98

DBB5CB240D57742DABA4D044F709C9518C19D77659CA0EF28D1BC7577B247428



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

161,262

06-Feb-2017

19:38

Not applicable

Flash.ocx

24.0.0.221

28,320,728

06-Feb-2017

19:38

x64

Flashutil_activex.dll

24.0.0.221

696,800

06-Feb-2017

19:38

x64

Flashutil_activex.exe

24.0.0.221

964,056

06-Feb-2017

19:38

x64

Activex.vch

Not applicable

739,446

06-Feb-2017

19:38

Not applicable

Flash.ocx

24.0.0.221

21,877,720

06-Feb-2017

19:38

x86

Flashplayerapp.exe

24.0.0.221

835,040

06-Feb-2017

19:38

x86

Flashplayercplapp.cpl

24.0.0.221

177,120

06-Feb-2017

19:38

Not applicable

Flashutil_activex.dll

24.0.0.221

614,872

06-Feb-2017

19:38

x86

Flashutil_activex.exe

24.0.0.221

1,342,424

06-Feb-2017

19:38

x86



File hash information

File name

SHA1 hash

SHA256 hash

Windows8.1-KB4010250-x64.msu

BEBA270A049E3FBDC982E99C2D784D5B5F9BA70A

68602C49FBC9D3F00143F7606306FE3899576C8FF416BBA2CA0CF9F3D40A42F1

Windows8.1-KB4010250-x86.msu

2EA597ED6A305D58CA2657B43F5D8976F5797C91

BC196BA43B5234BC5AE86150CFB95F4B623989F19EAB0C98DED654A6880A52CB



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

161,262

06-Feb-2017

19:41

Not applicable

Flash.ocx

24.0.0.221

28,321,272

06-Feb-2017

19:41

x64

Flashutil_activex.dll

24.0.0.221

697,336

06-Feb-2017

19:41

x64

Flashutil_activex.exe

24.0.0.221

964,600

06-Feb-2017

19:41

x64

Activex.vch

Not applicable

739,446

06-Feb-2017

19:41

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:41

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:41

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:41

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:41

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:41

x86


For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

739,446

06-Feb-2017

19:41

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:41

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:41

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:41

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:41

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:41

x86



File hash information

File name

SHA1 hash

SHA256 hash

Windows10.0-KB4010250-x64.msu

F880A47AFF3922D0D1D4A8C261AA24FC3B2A632C

704E2378604674418F2317672EA7C92EAD1DD5CAD79758CB37D8215DEA0BF763

Windows10.0-KB4010250-x86.msu

0B0AEAC5BECF27EF355C97764AB09E907E6AC756

19B05BB1ECBA34E6FCC21CBA9780EFD9C53FEB081E0DE4B23D61096A3B70DDCD



For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

161,262

06-Feb-2017

19:43

Not applicable

Flash.ocx

24.0.0.221

28,321,272

06-Feb-2017

19:43

x64

Flashutil_activex.dll

24.0.0.221

697,336

06-Feb-2017

19:43

x64

Flashutil_activex.exe

24.0.0.221

964,600

06-Feb-2017

19:43

x64

Activex.vch

Not applicable

739,446

06-Feb-2017

19:43

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:43

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:43

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:43

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:43

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:43

x86


For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

739,446

06-Feb-2017

19:43

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:43

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:43

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:43

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:43

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:43

x86



File hash information

File name

SHA1 hash

SHA256 hash

Windows10.0-KB4010250-x64.msu

8EDF5A83A0B46D2F4F30A4B192D832A4B4B3C9B2

7FA7625D5E01EBC793862521A7718CF6EF2A5BCF21714E4AA6D65BF6D880627E

Windows10.0-KB4010250-x86.msu

A300B69EC1FE7AEA0101AC964A93E115B15E759E

9B467D80FA7849EC414B8D5A55483187936DACF13AFD67609C00CADD6FB72A1D


For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

161,262

06-Feb-2017

19:45

Not applicable

Flash.ocx

24.0.0.221

28,321,272

06-Feb-2017

19:45

x64

Flashutil_activex.dll

24.0.0.221

697,336

06-Feb-2017

19:45

x64

Flashutil_activex.exe

24.0.0.221

964,600

06-Feb-2017

19:45

x64

Activex.vch

Not applicable

739,446

06-Feb-2017

19:45

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:45

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:45

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:45

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:45

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:45

x86


For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

739,446

06-Feb-2017

19:45

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:45

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:45

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:45

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:45

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:45

x86



File hash information

File name

SHA1 hash

SHA256 hash

Windows10.0-KB4010250-x64.msu

FA7AD44BE8DD1C65B51F07EFBEE478B0FBF82F5C

4A665F3E91729EFE086D524F2436407057C667CCD094CD95DE4EA27B2D91E0FD

Windows10.0-KB4010250-x86.msu

8E6459131457BD164EEE5160D316D223BA599C2F

D61372ABDB2162A8CF086950D3113DEE6354DBDBEB6994F900B397BE1A3EFD2F

For all supported x64-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

161,262

06-Feb-2017

19:48

Not applicable

Flash.ocx

24.0.0.221

28,321,272

06-Feb-2017

19:48

x64

Flashutil_activex.dll

24.0.0.221

697,336

06-Feb-2017

19:48

x64

Flashutil_activex.exe

24.0.0.221

964,600

06-Feb-2017

19:48

x64

Activex.vch

Not applicable

739,446

06-Feb-2017

19:48

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:48

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:48

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:48

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:48

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:48

x86


For all supported x86-based versions

File name

File version

File size

Date

Time

Platform

Activex.vch

Not applicable

739,446

06-Feb-2017

19:48

Not applicable

Flash.ocx

24.0.0.221

21,878,264

06-Feb-2017

19:48

x86

Flashplayerapp.exe

24.0.0.221

835,576

06-Feb-2017

19:48

x86

Flashplayercplapp.cpl

24.0.0.221

177,656

06-Feb-2017

19:48

Not applicable

Flashutil_activex.dll

24.0.0.221

615,416

06-Feb-2017

19:48

x86

Flashutil_activex.exe

24.0.0.221

1,342,968

06-Feb-2017

19:48

x86



Need more help?

Expand your skills

EXPLORE TRAINING >

Get new features first

JOIN MICROSOFT INSIDERS >

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×