Flash Player 21.0.0.213 - ActiveX, NPAPI, and PPAPI failed MSI installs via SCCM solutions for error 1603?

[nicolasw85907126]

My company's environment has 50,000 target machines (non-servers), all of which must be updated to the latest Flash iteration, 21.0.0.213.

After deploying via SCCM, using the MSI installers for ActiveX/NPAPI/PPAPI, we are seeing a consistent 13% failure rate, nearly all of which are MSI Error 1603.

Revising our installation script, we incorporated the following steps:

1. Install MSI
   1. if Success Code 0
      1. Verify ProductID in registry, success.
   1. If Fail:
      1. Run "uninstall_flash_player.exe -uninstall"
      2. Search registry for "Adobe Flash Player" entries and delete keys/subkeys from HKCR\Installer\Products, per Adobe KB Flash Player ActiveX msi installation fails using SCCM
      3. Retry Install MSI

After running through all those steps, we still have over 4,000 machines failing to install a simple MSI because of error 1603. Can anyone suggest solutions or tweaks?

[nicolasw85907126]

Syswow64\macromedia\flash\flashinstall.log:

=X====== M/21.0.0.182 2016-04-19+06-25-52.827 ========

=O====== M/21.0.0.213 2016-04-19+06-26-41.352 ========

0000 00000010 "C:\WINDOWS\SoftwareDistribution\Download\Install\install_flash_player_21_plugin.exe" -install

0001 00000011 1

0002 00000020 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

0003 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player NPAPI/ 2

0004 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player Plugin/ 2

0005 00001036 Software\Mozilla\Firefox\extensions/Plugins 2

0006 00001036 Software\Opera Software/Last CommandLine 2

0007 00001036 Software\Opera Software/Last CommandLine 2

0008 00001036 Software\Opera Software/Plugin Path 2

0009 00001036 Software\Opera Software/Plugin Path 2

0010 00000014

0011 00000015 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashUtil32_21_0_0_213_Plugin.exe

0012 00000024 C:\WINDOWS\SysWOW64\Macromed\Flash\plugin.vch

0013 00000017 C:\WINDOWS\SysWOW64\Macromed\Flash

0014 00000022 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerPlugin_21_0_0_213.exe

0015 00000019 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

0016 00001024 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl 183

0017 00001024 C:\WINDOWS\SysWOW64\FlashPlayerApp.exe 183

0018 00000021 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe

0019 00001106

0020 00001106

0021 00001024 C:\WINDOWS\SysWOW64\Macromed\Flash\FlashPlayerUpdateService.exe 183

=X====== M/21.0.0.213 2016-04-19+06-26-52.523 ========

System32\macromedia\flash\flashinstall.log:

=X====== M/21.0.0.213 2016-04-18+15-40-19.471 ========

=O====== M/21.0.0.213 2016-04-19+06-26-45.225 ========

0000 00000010 "C:\WINDOWS\TEMP\{58C2E15F-1BE7-48C8-BA7A-D4E285468E00}\InstallFlashPlayer.exe" -install -skipARPEntry -iv 1 -au 4294967295

0001 00000020 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

0002 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player NPAPI/ 2

0003 00001037 SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Adobe Flash Player Plugin/ 2

0004 00001036 Software\Opera Software/Last CommandLine 2

0005 00001036 Software\Opera Software/Last CommandLine 2

0006 00001036 Software\Opera Software/Plugin Path 2

0007 00001036 Software\Opera Software/Plugin Path 2

0008 00000014

0009 00000015 C:\WINDOWS\system32\Macromed\Flash\FlashUtil64_21_0_0_213_Plugin.exe

0010 00000024 C:\WINDOWS\system32\Macromed\Flash\plugin.vch

0011 00000019 C:\WINDOWS\SysWOW64\FlashPlayerCPLApp.cpl

=X====== M/21.0.0.213 2016-04-19+06-26-48.132 ========

Verbose MSIexec log (partial, only entries with "error" shown):

MSI (s) (1C:A0) [11:24:31:844]: Note: 1: 2228 2:  3: ServiceInstall 4: SELECT `ServiceInstall`,`Name`,`DisplayName`,`ServiceType`,`StartType`,`ErrorControl`,`LoadOrderGroup`,`Dependencies`,`StartName`,`Password`,`ComponentId`,`Directory_`,`FileName`,`Arguments` FROM `ServiceInstall`, `Component`, `File` WHERE `ServiceInstall`.`Component_` = `Component`.`Component` AND (`Component`.`KeyPath` = `File`.`File`) AND (`Action` = 1 OR `Action` = 2)

CustomAction NewCustomAction1 returned actual error code 1025 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (1C:A0) [11:24:41:220]: Product: Adobe Flash Player 21 ActiveX -- Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\WINDOWS\TEMP\InstallAX_21_0_0_213.exe, command: -install -msi -prev 0

Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action NewCustomAction1, location: C:\WINDOWS\TEMP\InstallAX_21_0_0_213.exe, command: -install -msi -prev 0

MSI (s) (1C:A0) [11:24:41:329]: Error in rollback skipped. Return: 5

Property(S): ErrorDialog = SetupError

MSI (s) (1C:A0) [11:24:41:423]: Windows Installer installed the product. Product Name: Adobe Flash Player 21 ActiveX. Product Version: 21.0.0.213. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Installation success or error status: 1603.

[ridhij42083560]

Hi,

Error status 1603 is a Microsoft error which you receive when you try to install .msi package.

Please go through the link: https://support.microsoft.com/en-in/kb/834484 and see if it resolves your issue.

Regards,

Ridhi

[nicolasw85907126]

Of course I've gone through Microsoft's error listings and KB articles (I can use Google, too). They are of no help, as this 1603 failure is rampant throughout the history of Adobe Flash Player MSI installations, specifically the ActiveX version.

As you can see from my post, I've utilized tips from several sources in an attempt to mitigate the failures, to no avail. Hence my posting here, hoping for a suggestion I haven't already come across.

[_maria_]

Hi,

What is the operating system, including version, of the impacted systems?

I'm not seeing any obvious errors in the FlashInstall.log file.  Please upload the entire MSI verbose log file to cloud.acrobat.com/send using the instructions at How do I share a file? .  Please include the corresponding FlashInstall.log file, in its entirety, from both locations (system32 and syswow64) for the same installation attempt.

Thank you.

--

Maria

[ashokk89308763]

Hi,

We're also facing same issue in ourorganisation. Operating system is Windows 7 64 bit....failing with error 1603 and when we run manually it isasking for older version source location. If we delete all old versions source locations under hklm\classes\installer\products, it installs fine. Experienced same for Shockwave, flash activex and flash NPAPI but other applications like Microsoft Silverlight is not giving any issue. Only issues with Adobe products. Please help.

Thanks,

Ashok

[markc54951597]

Ashok,

Have you tried the Flash Player Uninstaller?  I didn't have much luck running it through SCCM, but people swear that it works.

If I were you, I would go as far as finding the installers for those versions and copying the requested file to whatever location it's searching.  If you have to, install them and uninstall them again to make sure the paths are re-written and cleaned up with its own installer.

You'll have to move it with some sort of script on the failed machines, but I think that's an easier fix than making Windows do what you want.  Script a simple XCOPY command from your own machine to put the files there before the installer looks for them.

[ashokk89308763]

Thanks Mark for quick response....

You are suggesting to do 2 steps via sccm? In first uninstall using Uninstaller and then install latest msi? Please confirm.

Regarding your second suggestion to copy old install files. I feel it is easier to create a script to delete all left over product codes for flash under hklm\classes\Installer\products and then install msi as it is installing successfully if we delete old entries. For this I need to find all left over old versions product codes under hklm\classes\Installer\products by checking in some machines randomly and then add in the script. Let me know if this is a good option.

As I mentioned in my previous reply, this issue is present only in Flash products. Please could you pass information about this issue to the team who creates msi.

Thanks,

Ashok

[_maria_]

Hi,

What is the exact error you are seeing?  Please provide the FlashInstall.log file and complete verbose MSI install log file from an impacted system.  The FlashInstall.log file is saved at C:\Windows\System32\Macromed\Flash.  If this is a 64-bit OS, there's another FlashInstall.log file saved at C:\Windows\SysWOW64\Macromed\Flash.  Both files are required from a 64-bit OS.  Upload the files to cloud.acrobat.com/send using the instructions at How to share a document​.  Post the link to the uploaded files in your reply.

We post a list of all MSI GUIDs here: GUID list for Flash Player versions 11, 10, and 9

--

Maria

[ashokk89308763]

Hi Vargas,

Please find link below for log files.

Shared Files - Acrobat.com

Product code which gets created under hklm\Software\Classes\Installer\Products is not similar to the one which gets created under uninstall string.

Thanks,

Ashok

[_maria_]

Several questions for you:

• What version was installed on the system when attempting to upgrade to 21.0.0.242?
• What ProductCode is created under hklm\Software\Classes\Installer\Products?
• What ProductCode is created under the uninstall string entry?
• Are users logged on, and potentially viewing Flash content, when you deploy the update, or is it deployed at a time when user's are not likely to be logged on?

--

Maria

[meneshh10561209]

Hi, We are deploying 22 and getting he same. Pervious version is 21. How can we remove this error via SCCM

[markc54951597]

What OS's are you deploying to?

The ActiveX version is obsolete for Windows 8/8.1/10 and the baked-in component will be updated through Windows update.  If you push the ActiveX installer to these machines, it will fail saying that it's unnecessary.  Seems like something that could produce the general  1603 error.

Have you tried to manually launch the installer on one of these clients?