This project has moved and is read-only. For the latest updates, please go here.

Installed updates continue to want to be installed

Topics: Publishing Issue
Jul 9, 2014 at 7:05 PM
I currently set up packages for Adobe Flash Player 14 and Java 7u60. The packages are installing properly but if you check for updates again it wants to install them both again.

I have verified that both programs are installed properly on the multiple machines but cannot figure out what setting I'm missing that recognizes a package is already installed.

I also restarted the computers after applying an update.
Jul 9, 2014 at 8:12 PM
What do you have set as "IsInstallable" and "Isinstalled" Rules ?
Jul 9, 2014 at 9:34 PM
Where would that be located?

I used the Installing Java 7u21 without Java Auto Updater .pdf on the documentation tab to reference how I create my updates.
Jul 9, 2014 at 10:18 PM
Page 7,8 for "IsInstalled" rule.
Page 10 for "IsInstallable" rule.
Jul 9, 2014 at 10:25 PM
Edited Jul 9, 2014 at 10:25 PM
I am confused as to where this is. When I look under the Rule Type drop down I do not see windows with those titles. Per the instructions I add the MSI Product Installed product code on the steps of 7,8 and Delete Rules at Package Level and add it again for the steps of 10 and check reverse rule and Delete Rules at Package Level.
Jul 10, 2014 at 5:35 AM
This mean, you are using the MSI product code for Java 7U21. You need to use the code for Java 7U60.
Jul 10, 2014 at 1:39 PM
Edited Jul 10, 2014 at 1:54 PM
I extracted the MSI product code from the 7u60 install. I'm using the documentation to remind me what steps I need to do to create the update. Things requiring changing being the MSI product code and path to file. Correct me if I'm wrong.
Jul 10, 2014 at 5:30 PM
So, what do you have set as "IsInstallable" and "Isinstalled" Rules ?
Jul 10, 2014 at 6:03 PM
Edited Jul 10, 2014 at 6:04 PM
Like I said before, I do not know where this is. You referred me to pages 7,8 and 10 and I see no text that says "isinstallable" or "isinstalled" on the page or the dropdowns. Do you have any more specifics as to where this information is located other than update creation wizard pages from the documentation?
Jul 10, 2014 at 7:07 PM
When you create an update, on top of the window, there is a text that explain what this window is for.
When you see :
Indicate here the rule or rules that allow clients computer to determine if the update is already installed.
You are in the window where you can define "IsInstalled" rules.

When you see :
Indicate here the rule or rules that allow clients computer to determine if the update is installable.
You are in the window where you can define "IsInstallable" rules.

Tell me what you have define as rules.
Jul 10, 2014 at 8:16 PM
isinstalled:

<msiar:MsiProductInstalled ProductCode="{57bda5c6-443c-4d65-b233-2823932170ff}"/>

isinstallable:

<lar:Not>
<msiar:MsiProductInstalled ProductCode="{57bda5c6-443c-4d65-b233-2823932170ff}"/>
</lar:Not>
Jul 10, 2014 at 9:39 PM
You have used the UpgradeCode instead of the product code.
The productCode for Java 7 update 60 is : {26A24AE4-039D-4CA4-87B4-2F03217060FF} for 32bit and {26A24AE4-039D-4CA4-87B4-2F06417060FF} for 64bit
Jul 10, 2014 at 9:58 PM
I have made the change and will try the install again. I am also having this issue with my Adobe Flash package. I double checked my product code to verify I wasn't using the update code and it has the product code.
Jul 11, 2014 at 6:24 AM
You don't need to install again. Clients computer will detect the change into metadata of the udpate and therefore, re-evaluate these package based on the new rules.

What rules do you have include into Adobe package ?
Jul 11, 2014 at 1:40 PM
isinstalled:

<msiar:MsiProductInstalled ProductCode="{1f5e5f2e-5e61-431d-b796-58ccc6b68e28}"/>

isinstallable:

<lar:Not>
<msiar:MsiProductInstalled ProductCode="{1f5e5f2e-5e61-431d-b796-58ccc6b68e28}"/>
</lar:Not>
Jul 11, 2014 at 6:31 PM
what is the exact version of Flash player (14.0.0.xxx) and, is it the ActiveX or the Plugin ?
Jul 11, 2014 at 6:41 PM
14.0.0.125 ActiveX
Jul 11, 2014 at 7:50 PM
Edited Jul 12, 2014 at 4:07 PM
Rules looks ok. Most likely, something went wrong during the installation of the activeX of Flash player 14.0.0.125. On a computer, uninstall flash player, and let WU-Agent to install again Flash. Then see if the problem occur again.
Jul 11, 2014 at 8:38 PM
I now receive Error Code 6BA. Am I right in assuming this has to do with the isintalled and isinstallable rules? Is there a way to make the update package recognize if the machine has the application the package is trying to install already and not install, but also install on computers that may not have adobe flash installed yet?
Jul 12, 2014 at 4:28 PM
Psolberg wrote:
I now receive Error Code 6BA. Am I right in assuming this has to do with the isintalled and isinstallable rules? Is there a way to make the update package recognize if the machine has the application the package is trying to install already and not install, but also install on computers that may not have adobe flash installed yet?
Are you trying on a W8.x Client? If yes, W8.x will get Flash Player from Windows Update (Microsoft) directly.
Jul 12, 2014 at 4:39 PM
IsInstalled and IsInstallable rules are ok, assuming you are trying to install Flash Player 14.0.0.125 ActiveX.
I think the installation of Adobe Flash Player has been tampered with.
Try to use Uninstaller of Flash Player: http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-windows.html
And then reinstall with WU-Agent.
Jul 14, 2014 at 2:25 PM
They are Windows 7 machines. I will recreate the package with Adobe Flash 14.0.0.145 ActiveX.
Jul 14, 2014 at 4:15 PM
For Adobe Flash Player 14.0.0.145, you will need to use another MSI Product-Code.
Aug 6, 2014 at 5:14 PM
Edited Aug 6, 2014 at 5:19 PM
For Flashplayer I added a program to be executed first the uninstaller. the command line is: "uninstall_flash_player.exe -uninstall" without quotation marks, then the installation was done successffully on all the previous was failed.
Marked as answer by DCourtel on 8/13/2014 at 3:15 AM
Oct 15, 2014 at 8:32 PM
Is this the proper Is Installed rule to check that the version of this package has already been installed and to NOT install again (adobe flash player):

<bar:FileExists Path="C:\Windows\SysWOW64\Macromed\Flash"/>
Oct 15, 2014 at 8:47 PM
You are using a "File Exists" rule but the path refers to a folder !
Does "C:\Windows\SysWOW64\Macromed\Flash" will exists on 32 bit computers ?

You should use the MSI product code for this release.
Oct 15, 2014 at 8:54 PM
Edited Oct 15, 2014 at 8:54 PM
I am using the product code. But noticed on some machines the flash package would try and install upon a restart (when the package was already installed) and users were waiting upwards of 30 minutes for the install (which had to be canceled so they could get on their machines to work).

This was using the MSI product code. We're running 64-bit machines.
Oct 17, 2014 at 3:33 PM
Edited Oct 17, 2014 at 6:16 PM
Has anyone else run into an issue with their Adobe Flash player package taking an unreasonable amount of time to install on shutdown?

I recreated my Adobe Flash Player ActiveX 15.0.0.189 package like every other one that's gone through successfully and the computer took 15 hours to go from "installing package 1 of 1" to saying shutting down. This process I left for another 4 hours before having to do a hard shutdown.

Any suggestions are appreciated.