Noticed something strange while testing. If I install Adobe Flash Player 10.0.32.18 (Windows XP environment, Office 2003 SP3), which is the current version, everything's fine. If for any reason I uninstall it, and then attempt to reinstall it, I get a dialog that says "The version of Adobe Flash Player ActiveX that you are trying to install is not the most current version".

I get this error if I attempt the reinstall from my wrapper exe, which is just some Wise code that installs a few different apps, and also get the error if I attempt the reinstall direct from the Adobe MSI.

I haven't found anything obvious in the registry or the Adobe MSI, and the only other clue I have is in an install.log file that gets written to C:\Windows\system32\Macromed\Flash during the install. Here's the contents of that file:

Start Main Section - Date=12/08/2009 (Wednesday)
Time=9:19:33
CreateDirectory: "C:\WINDOWS\system32\Macromed\Flash" (1)
Call: 445
Safety Check
Call: 116
Call: 1228
File: overwriteflag=1, allowskipfilesflag=2, name="C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll"
File: wrote 4096 to "C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll"
CheckAdminPermissions Name = rwortz
Call: 1228
File: overwriteflag=1, allowskipfilesflag=2, name="C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll"
File: skipped: "C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll" (overwriteflag=1)
CheckAdminPermissions Account Type = Admin
Jump: 148
Call: 148
Call: 74
Jump: 111
GetWindowsVersion -

CheckSupportedPlatform - OS=XP

Call: 451
CheckFPPermissions
Call: 74
Jump: 111
GetWindowsVersion - XP

Call: 1228
File: overwriteflag=1, allowskipfilesflag=2, name="C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\fpinstall.dll"
File: wrote 8704 to "C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\fpinstall.dll"
ObjectExistsAndIsOwnedBySomeoneElse = 0
Jump: 494
MessageBox: 12582960,"The version of Adobe® Flash® Player ActiveX that you are trying to install is not the most current version.
Please visit http://www.adobe.com/go/getflashplayer to obtain the latest, most secure version."


The other strange thing is that after I click OK in the dialog, the install completes successfully, and when I recheck the install.log file, the chunk of text referencing the message box about the version not being current is gone.

Any ideas what I can try to fix this?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
My route would be to run ProcMon as the re-install executes, to determine how the installer is determining the version status.
Answered 08/12/2009 by: VBScab
Red Belt

Please log in to comment
0
Yes. Also, why are you uninstalling Flash? The new versions install over-top. You might be going through this effort for no reason.
Answered 08/12/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
Turbs, in most environments I've worked in, you have to prove uninstall works before deployment, irrespective of whether apps are ever uninstalled in that environment.
Answered 08/12/2009 by: VBScab
Red Belt

Please log in to comment
0
Yep. Always that pesky backout plan. Especially important when SIT has not been properly done & you find out that the new Adobe reader breaks the bank teller application when they try & pull up past statements... :-)
Answered 08/12/2009 by: kiptek
Second Degree Green Belt

Please log in to comment
0
Guys it's flash... I understand back-out plans, but come on. Any other app, I'd say "figure it out".
Answered 08/12/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
You didn't say how you were uninstalling it. Have you tried running the uninstaller that gets put down when you install it?
For ActviveX, try running this: C:\WINDOWS\system32\Macromed\Flash\uninstall_activeX.exe
For the plug-in, try running this: C:\WINDOWS\system32\Macromed\Flash\uninstall_plugin.exe
Answered 08/12/2009 by: bearden3
Purple Belt

Please log in to comment
0
ORIGINAL: RonW

Noticed something strange while testing. If I install Adobe Flash Player 10.0.32.18 (Windows XP environment, Office 2003 SP3), which is the current version, everything's fine. If for any reason I uninstall it, and then attempt to reinstall it, I get a dialog that says "The version of Adobe Flash Player ActiveX that you are trying to install is not the most current version".

I get this error if I attempt the reinstall from my wrapper exe, which is just some Wise code that installs a few different apps, and also get the error if I attempt the reinstall direct from the Adobe MSI.

I haven't found anything obvious in the registry or the Adobe MSI, and the only other clue I have is in an install.log file that gets written to C:\Windows\system32\Macromed\Flash during the install. Here's the contents of that file:

Start Main Section - Date=12/08/2009 (Wednesday)
Time=9:19:33
CreateDirectory: "C:\WINDOWS\system32\Macromed\Flash" (1)
Call: 445
Safety Check
Call: 116
Call: 1228
File: overwriteflag=1, allowskipfilesflag=2, name="C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll"
File: wrote 4096 to "C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll"
CheckAdminPermissions Name = rwortz
Call: 1228
File: overwriteflag=1, allowskipfilesflag=2, name="C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll"
File: skipped: "C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\UserInfo.dll" (overwriteflag=1)
CheckAdminPermissions Account Type = Admin
Jump: 148
Call: 148
Call: 74
Jump: 111
GetWindowsVersion -

CheckSupportedPlatform - OS=XP

Call: 451
CheckFPPermissions
Call: 74
Jump: 111
GetWindowsVersion - XP

Call: 1228
File: overwriteflag=1, allowskipfilesflag=2, name="C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\fpinstall.dll"
File: wrote 8704 to "C:\DOCUME~1\rwortz\LOCALS~1\Temp\nse15E.tmp\fpinstall.dll"
ObjectExistsAndIsOwnedBySomeoneElse = 0
Jump: 494
MessageBox: 12582960,"The version of Adobe® Flash® Player ActiveX that you are trying to install is not the most current version.
Please visit http://www.adobe.com/go/getflashplayer to obtain the latest, most secure version."


The other strange thing is that after I click OK in the dialog, the install completes successfully, and when I recheck the install.log file, the chunk of text referencing the message box about the version not being current is gone.

Any ideas what I can try to fix this?


Ron, this is because Adobe has gotten "clever" and wrapped the entire product into one file. If you'll notice, the entire installation is one file fx_* someting.exe which expands and runs the install. So, like Sun JRE, if you want to overcome their nonstandard install you'll need to disable CA's or create your own CA's to counteract them.
Answered 08/12/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
VBScab was right: ProcMon was the way to go. Turns out it was a registry key I never would've guessed that was causing the "this isn't the current version" dialog.

And in answer to a couple other questions: I'm not uninstalling previous versions. I uninstalled the same version. What I'm doing is changing the way some of our company installs work. In the past they were from physical media only; now I'm caching them to a protected folder on the PC and wanted to make sure my code ran not only from the physical media, but also from the cached version on the PC.
Answered 08/13/2009 by: RonW
Green Belt

Please log in to comment
0
So what registry key was it? I'm getting the same dialog.
Answered 08/28/2009 by: cblake
Red Belt

Please log in to comment
1
Hi, cblake. The reg key was HKLM\Software\Macromedia\FlashPlayer\SafeVersions.

I deleted that key prior to the Flash Player install, and that solved the problem.

The installation then rebuilds that key with the exact same info in it (at least it did for me). If the key existed, I got the complaint dialog that my version wasn't current. Deleted the key pre-install, and no more complaint dialog.
Answered 08/31/2009 by: RonW
Green Belt

Please log in to comment
0
Yeah, glad that worked for you. I didn't notice on your original post, but 10.0.32.18 IS the most recent version (duh) so that is kind of a brain dead message. I saw it on older versions once 10.0.32.18 was released. Personally I would have (and did) delete the custom actions CheckForProductUpdatesOnReboot and CheckForProductUpdates rather than relying on procmon. Since I don't know exactly what [ISUpdateServiceFolder]FlashUtil.exe "/au[ProductCode] /EndOfInstall"
is doing (did you leave these CAs in? is it still doing the call home? how do you know that simply deleting the registry value will stop it from doing that? you don't. Procmon's a great tool but only a tool. )

Observe: there is only one file (FP_AX_MSI_INSTALLER.exe) in the entire installation, and THAT pretty much controls the whole shebang. Kinda scary. And I thought Sun Java was bad....LOL. [:@]
Answered 08/31/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity