INTRODUCTION
Microsoft has released a Microsoft security advisory about this issue for IT professionals. The security advisory contains additional security-related information. To view the security advisory, go to the following Microsoft website:
More Information
Known issues with this security update
-
Windows Update will not offer this security update to Windows RT-based computers until update 2808380 is installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2808380 Windows RT-based device cannot download software updates or Windows Store apps
Resolution
The following files are available for download from the Microsoft Download Center:
Update for Internet Explorer Flash Player for Windows 8.1 (KB3035034)
Update for Internet Explorer Flash Player for Windows 8.1 x64-based systems (KB3035034)
Update for Internet Explorer Flash Player for Windows 8 (KB3035034)
Update for Internet Explorer Flash Player for Windows 8 x64-based systems (KB3035034)
Update for Internet Explorer Flash Player for Windows Server 2012 (KB3035034)
Update for Internet Explorer Flash Player for Windows Server 2012 R2 (KB3035034)
Release Date: January 27, 2015
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Note Windows Technical Preview and Windows Server Technical Preview are affected. Customers who are running these operating systems are encouraged to apply the update from Windows Update.
Update 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
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 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.
The following table provides the MBSA detection summary for this security update.
|
Software |
MBSA |
|---|---|
|
Windows 8 and Windows 8.1 for 32-bit systems |
No |
|
Windows 8 and Windows 8.1 for 64-bit systems |
No |
|
Windows Server 2012 and Windows Server 2012 R2 |
No |
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 article:
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 and Windows 8.1 for 32-bit systems |
No |
Yes |
|
Windows 8 and 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 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 validating of Windows updates against installed applications by using the
Update Compatibility Evaluator components that are included in 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.
Windows 8 and 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 |
|---|---|
|
Installing without requiring user intervention |
For Adobe Flash Player in Internet Explorer 10 on all supported 32-bit editions of Windows 8: |
|
For Adobe Flash Player in Internet Explorer 10 on all supported x64-based editions of Windows 8: |
|
|
For Adobe Flash Player in Internet Explorer 11 on all supported 32-bit editions of Windows 8.1: |
|
|
For Adobe Flash Player in Internet Explorer 11 on all supported x64-based editions of Windows 8.1: |
|
|
Installing without restarting |
For Adobe Flash Player in Internet Explorer 10 on all supported 32-bit editions of Windows 8: |
|
For Adobe Flash Player in Internet Explorer 10 on all supported xx64-based editions of Windows 8: |
|
|
For Adobe Flash Player in Internet Explorer 11 on all supported 32-bit editions of Windows 8.1: |
|
|
For Adobe Flash Player in Internet Explorer 11 on all supported x64-based editions of Windows 8.1: |
|
|
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 |
|
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 s 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
-
Click Start, and then type an update file name in the Search box.
-
When the file appears under Programs, right-click the file name, and then click Properties.
-
On the General tab, compare the file size with the file information tables that are provided in the Microsoft Knowledge Base article.
Note Depending on the edition of the operating system or the programs that are installed on your system, some files that are listed in the file information table may not be installed. -
You can also click the Details tab and compare information, such as file version and date changed, with 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. -
Finally, you can also click the Previous Versions tab and 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: |
|
For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2: |
|
|
Installing without restarting |
For Adobe Flash Player in Internet Explorer 10 on all supported editions of Windows Server 2012: |
|
For Adobe Flash Player in Internet Explorer 11 on all supported editions of Windows Server 2012 R2: |
|
|
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 |
|
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 |
|
|
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 article:
Miscellaneous Changes in Windows 7
Verifying that the update was appliedBecause there are several editions of Windows, the following steps may be different in your system. If they are different, see your product documentation to complete these steps.
Verifying the file version
-
Click Start, and then type an update file name in the Start Search box.
-
When the file appears under Programs, right-click the file name, and then click Properties.
-
On the General tab, compare the file size with the file information tables 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. -
You can also click the Details tab to compare information, such as file version and date changed, with 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. -
Finally, you can also click the Previous Versions tab, and then compare file information for the earlier version of the file with the file information for the new or updated version of the file.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.
For Internet Explorer Flash Player for x86-based versions of Windows 8.1 (KB3035034)
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Activex.vch |
Not applicable |
587,066 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
18,621,920 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayerapp.exe |
16.0.0.296 |
714,720 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayercplapp.cpl |
16.0.0.296 |
106,976 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flashutil_activex.dll |
16.0.0.296 |
582,112 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashutil_activex.exe |
16.0.0.296 |
984,544 |
24-Jan-2015 |
20:20 |
x86 |
For Internet Explorer Flash Player for x64-based versions of Windows 8.1 and Windows Server 2012 R2 (KB3035034)
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Activex.vch |
Not applicable |
139,782 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
23,882,720 |
24-Jan-2015 |
20:20 |
x64 |
|
Flashutil_activex.dll |
16.0.0.296 |
648,672 |
24-Jan-2015 |
20:20 |
x64 |
|
Flashutil_activex.exe |
16.0.0.296 |
637,920 |
24-Jan-2015 |
20:20 |
x64 |
|
Activex.vch |
Not applicable |
587,066 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
18,621,920 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayerapp.exe |
16.0.0.296 |
714,720 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayercplapp.cpl |
16.0.0.296 |
106,976 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flashutil_activex.dll |
16.0.0.296 |
582,112 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashutil_activex.exe |
16.0.0.296 |
984,544 |
24-Jan-2015 |
20:20 |
x86 |
For Internet Explorer Flash Player for x86-based versions of Windows 8 (KB3035034)
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Activex.vch |
Not applicable |
587,066 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
18,621,376 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayerapp.exe |
16.0.0.296 |
714,176 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayercplapp.cpl |
16.0.0.296 |
106,432 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flashutil_activex.dll |
16.0.0.296 |
581,568 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashutil_activex.exe |
16.0.0.296 |
984,000 |
24-Jan-2015 |
20:20 |
x86 |
|
Activex.vch |
Not applicable |
587,066 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
18,621,376 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayerapp.exe |
16.0.0.296 |
714,176 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayercplapp.cpl |
16.0.0.296 |
106,432 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flashutil_activex.dll |
16.0.0.296 |
581,568 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashutil_activex.exe |
16.0.0.296 |
984,000 |
24-Jan-2015 |
20:20 |
x86 |
For Internet Explorer Flash Player for x64-based versions of Windows 8 and Windows Server 2012 (KB3035034)
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Activex.vch |
Not applicable |
139,782 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
23,882,176 |
24-Jan-2015 |
20:20 |
x64 |
|
Flashutil_activex.dll |
16.0.0.296 |
648,128 |
24-Jan-2015 |
20:20 |
x64 |
|
Flashutil_activex.exe |
16.0.0.296 |
637,376 |
24-Jan-2015 |
20:20 |
x64 |
|
Activex.vch |
Not applicable |
139,782 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
23,882,176 |
24-Jan-2015 |
20:20 |
x64 |
|
Flashutil_activex.dll |
16.0.0.296 |
648,128 |
24-Jan-2015 |
20:20 |
x64 |
|
Flashutil_activex.exe |
16.0.0.296 |
637,376 |
24-Jan-2015 |
20:20 |
x64 |
|
Activex.vch |
Not applicable |
587,066 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
18,621,376 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayerapp.exe |
16.0.0.296 |
714,176 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayercplapp.cpl |
16.0.0.296 |
106,432 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flashutil_activex.dll |
16.0.0.296 |
581,568 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashutil_activex.exe |
16.0.0.296 |
984,000 |
24-Jan-2015 |
20:20 |
x86 |
|
Activex.vch |
Not applicable |
587,066 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flash.ocx |
16.0.0.296 |
18,621,376 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayerapp.exe |
16.0.0.296 |
714,176 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashplayercplapp.cpl |
16.0.0.296 |
106,432 |
24-Jan-2015 |
20:20 |
Not applicable |
|
Flashutil_activex.dll |
16.0.0.296 |
581,568 |
24-Jan-2015 |
20:20 |
x86 |
|
Flashutil_activex.exe |
16.0.0.296 |
984,000 |
24-Jan-2015 |
20:20 |
x86 |
File hash information
|
Windows8-RT-KB3035034-x64.msu |
9D7D3D0896315994D9E13DAAC12D1A6394E0F8AC |
5A7CAC4E695D524A01A95365FB65D7BD809B5E0E10973804EAC989654F3DECBD |
|
Windows8-RT-KB3035034-x86.msu |
5FCBEA1E4C86799D76D35BFE8AB0AAC77F75616C |
D73584468CABA5CF294DDF3EB8271A75EA6B5155868514B84547E0665BFE8A52 |
|
Windows8.1-KB3035034-x64.msu |
4B36F7ACB9FBD6CD30304DD64DB68E7E762A246D |
49194F49561DEE1A4000F8B3DB68CD8D15D73301EB4E7691C7429911303B431A |
|
Windows8.1-KB3035034-x86.msu |
D1285805D8AAC70803DC59C3660FBAA6EF0EF9E2 |
1E10466D427C3F8C341A71C8A8C27423D975089AB57C9D02C71CA1A674705EBA |
