Copy link to clipboard
Copied
Hello,
The latest Flash upgrade 17.0.0.188 fails to install on about 80% of systems in our environment using SolarWinds for 3rd party patches to WSUS.
The error on the windows side is:
Result Code: 0x411 (Unknown error (0x411)) HRESULT: 0x80070643 (Fatal error during installation)
The error on the Adobe side is actually a fail with the only code being:
0001
I have been distributing Flash Player in our environment for years and never had a failure to this extent before.
The last upgrade from 17.0.0.134 to 17.0.0.169 was ok as recorded in the provided log file below...but there is nothing but 0001
I have seen some discussions about IE needing to be closed, but this was not the case previously and why now if that is what it is?
I installed this upgrade manually (on a machine that failed through the WSUS process) and it was ok...don't remember if IE was open or closed at the time.
I did notice that the digital signature timestamp seemed old when I first downloaded the .exe installer from the distribution page. The next day I downloaded an updated .exe installer that had a more recent digital timestamp and it failed as well.
I notice there are several discussions regarding this (Update Needed: Flash Player 17.0.0.188 Setup Files are 17.0.0.169 for the MSI Setup Files). Could it be this is an installer issue?
Can any Adobe staff comment?
Can any community member that uses a similar software deployment method to mine comment on a successful upgrade?
=O====== M/17.0.0.134 2015-03-17+07-00-11.517 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
0002 00000011 1
0003 00000020 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0004 00000013
0005 00000015 C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_17_0_0_134_ActiveX.exe
0006 00000016 C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_17_0_0_134_ActiveX.dll
0007 00000023 C:\Windows\SysWOW64\Macromed\Flash\activex.vch
0008 00000019 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0009
0010
0011 00000021 C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe
0012
0013
0014
=X====== M/17.0.0.134 2015-03-17+07-00-18.038 ========
=O====== M/17.0.0.169 2015-04-17+07-00-15.928 ========
0000 00000010 "C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_17_0_0_169_ActiveX.exe" -refreshIEElevationPolicies
=X====== M/17.0.0.169 2015-04-17+07-00-15.959 ========
=O====== M/17.0.0.169 2015-04-17+07-00-11.656 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001 00000011 1
0002 00000020 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0003
0004 00000018
0005
0006 00000013
0007 00000015 C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_17_0_0_169_ActiveX.exe
0008 00000016 C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_17_0_0_169_ActiveX.dll
0009 00000023 C:\Windows\SysWOW64\Macromed\Flash\activex.vch
0010 00000019 C:\Windows\SysWOW64\FlashPlayerCPLApp.cpl
0011
0012
0013 00000021 C:\Windows\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe
0014
0015
0016
=X====== M/17.0.0.169 2015-04-17+07-00-18.657 ========
=O====== M/17.0.0.169 2015-05-14+07-00-11.713 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
=X====== M/17.0.0.169 2015-05-14+07-00-12.281 ========
=O====== M/17.0.0.169 2015-05-15+07-00-12.518 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
=X====== M/17.0.0.169 2015-05-15+07-00-13.128 ========
=O====== M/17.0.0.169 2015-05-16+07-00-11.628 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
=X====== M/17.0.0.169 2015-05-16+07-00-12.138 ========
=O====== M/17.0.0.169 2015-05-17+07-00-11.439 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
=X====== M/17.0.0.169 2015-05-17+07-00-11.949 ========
=O====== M/17.0.0.169 2015-05-18+07-00-12.288 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
=X====== M/17.0.0.169 2015-05-18+07-00-12.798 ========
=O====== M/17.0.0.169 2015-05-19+07-00-13.302 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
=X====== M/17.0.0.169 2015-05-19+07-00-13.822 ========
=O====== M/17.0.0.169 2015-05-20+07-00-17.857 ========
0000 00000010 "C:\Windows\SoftwareDistribution\Download\Install\install_flash_player_17_active_x.exe" -install
0001
=X====== M/17.0.0.169 2015-05-20+07-00-18.435 ========\
Thank you in advance for any ideas on why this fails.
Message was edited by: Sean Brown
Copy link to clipboard
Copied
Hi Foofighter,
Error 1041 means an application (e.g. browser) that uses Flash Player is open and must be closed for Flash Player installation to continue, however, this does not apply to an upgrade of the ActiveX control used by IE. According to the log file, the version being installed is 17.0.0.169 (April's release), not 17.0.0.188 (May's release). The version number is logged at the beginning and end of the install attempt. If 17.0.0.169 is already installed on the system error 1041 will be returned when attempting to install the same version and IE is open.
The requirement to close applications that use Flash Player before installation proceeds is being removed, for most installation workflows, in a future release of Flash Player.
--
Maria
Copy link to clipboard
Copied
Thank you m_vargas for the response.
Just so I understand...this was not an issue before and so this browser closed requirement was included in just this upgrade (17.0.0.188) release and will be removed in the next release?
Copy link to clipboard
Copied
Hi Foofighter,
Sorry, I submitted my comment to soon. I've since edited it to clarify the most likely reason why error 1041 is being returned in this situation.
--
Maria
Copy link to clipboard
Copied
Thank you m_vargas for the response...I thought sure the log was showing 17.0.0.188, but since it isn't the overwrite of the correct 17.0.0.188 file from Adobe distribution was not successful in WSUS. I have since updated the file in WSUS and will check tomorrow to see if it is successful or not.
Thanks for your help m_vargas!
Copy link to clipboard
Copied
Hi m_vargas,
My installation using what I think is 17.0.0.188 failed again last night. I am seeing in the log that it is trying to install version 17.0.0.169.
Can you verify if the digital signature date on the 17.0.0.188 file should ‎Saturday, ‎April ‎25, ‎2015 12:57:22 PM?
I have cleared my browser cache and I still receive the same file with the same digital signature.
TIA
Copy link to clipboard
Copied
Hi Foofighter,
Here is a screenshot of the details and digital signature Properties tabs for 17.0.0.188 ActiveX installer:
And the hash values for the EXE and MSI installer (not sure which one you're using):
Size: 17583280 bytes
File Version: 17,0,0,188
MD5: 5C2E3F81996E84D6BD6209160C4C6048
SHA1: 99CB4F6951842FC19530EF5669B4CD6457D40162
Size: 18719744 bytes
MD5: 3AF2AC73B116A38926D27EB35CECFB8D
SHA1: C82369D8833B56D06468C4E0BC5B6042A138E82C
--
Maria