/build/static/layout/Breadcrumb_cap_w.png

Adobe flash 11.6.602.180 won't install

This version of Adobe flash: 11.6.602.180

from here:

http://www.adobe.com/products/flashplayer/distribution3.edu.html

Won't install (at least on Windows 7), unlike all previous revisions.

I get this error:

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: ....\AppData\Local\Temp\InstallPlugin_11_6_602_180exe.

command: -install -msi

[This latter command, is something it must generate internally.  I install the msi download like so:

msiexec /i <Pathtodownloads>/install_flash_player_11_plugin.msi   /quiet /passive /qb /norestart /l+* %systemdrive%\log\flash.log

 

There doesn't seem to be a way to contact Adobe itself about this product problem.

Since these updates are usually security fixes, it seems like a bad thing to roll back.


0 Comments   [ + ] Show comments

Answers (3)

Posted by: rileyz 11 years ago
Red Belt
0

Try this,

msiexec /i flashname.msi /qb /l*v %systemroot%\logs\flash.log

Just noticed your "logs" is a "log", it has a "s", probaly bombing out on that (;
Also noticed your %systemdrive% will resolve to your user account folder (C:\users..). You really should use %systemroot% for logging, or somewhere common.

Also It needs to write to a folder that exists: it my case %systemroot%\logs\flash.log = C:\windows\logs\flash.log

If all else falls, fall back to a basic install command like "msiexec /i flash.msi /qb" and start from there.

Good luck, remember to mark it as answered if it helps as it will help others (:

Riley

 


Comments:
  • > Just noticed your "logs" is a "log", it has a "s", probaly bombing out on that (;
    No, C:\log exists, it's a folder my standard installer scripts check/create

    > Also noticed your %systemdrive% will resolve to your user account folder (C:\users..).
    On the systems I have, %systemroot% resolves to C:\Windows (don't have anything that
    uses alternate disk right now), & %systemdrive% to C:. I want the latter.
    I'm looking at Windows 7 at the moment; XP is the other target once I make
    sure this install works properly - nasruddin 11 years ago
Posted by: vjaneczko 11 years ago
9th Degree Black Belt
0

Best to use the MSI instead of the EXE as it provides better control.  Funny thing about the EXE for Flash, it comes as an EXE which is nothing more than a wrapper for the MSI - which in turn is nothing more than a wrapper for an EXE.  One day I hope they'll figure it out. . . but I digress.

Make sure you wrap the <Pathtodownloads>/install_flash_player_11_plugin.msi in quotes if there's any spaces in the path to the downloads.

You can also trim down your switches; you should be able to use "/QB-" in place of "/quiet /passive /qb"


Comments:
  • > Best to use the MSI instead of the EXE as it provides better control. Funny thing about the EXE for Flash, it

    What better control? Pretty used to MSI's, and don't happen to know the command line
    switches needed. I have often had trouble getting the right ones passed into the internal
    scripts/installers/msi's. - nasruddin 11 years ago
    • To be clear, I avoided the .exe form because I didn't know what its switches were, but I did know how to work the .msi. Before this, anyway :^) - nasruddin 11 years ago
Posted by: vjaneczko 11 years ago
9th Degree Black Belt
0

Use of the MSI allows greater control.  Maybe you misread my comment - or I didn't make it clear enough  :)

For the Flash package, I create a transform so I can include the CFG file to turn off auto-updates, add a signature key and set a few properties.  Can't do that with the EXE.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ