About flotek72

flotek72 · ‎Jun 26, 2014

I'm not sure why, but for some reason InstallShield was pulling a prerequisite with different conditions during the build. I've checked Tools -> Options-> Prereq tab and it had the correct path there. When I fixed the prereq in another location everything worked fine. So I guess the issue is resolved now.

flotek72 · ‎Jun 25, 2014

Under the Behavior tab in the prerequisite there is a drop down box at the bottom with the text above it that says "If the prerequisite appears to need a reboot:". This should be set to Reboot the machine and resume on reboot.

flotek72 · ‎Jun 25, 2014

I have a Basic MSI Project that has several prereqs. I set the launch conditions for the MSI to be Win Vista SP2, Win 7 SP1, Win 8+ and their corresponding Server OSs. Now, when running the installer on Win XP, the launch condition fails and I get a pop up message. That's great, however I was finding that I had some prereqs that were popping up before that point and would need to be installed before realizing that I can't even install the program on the OS. So, to fix this problem I went through each prereq and set the OSs that the prereq would run under to the same as the launch conditions. This worked for every prereq except one. I can't seem to figure out why this one prereq is still showing up on XP. Listed below is the prereq in question and it's conditions tab contents. Microsoft .NET Framework 4.0 Full (Web Download).prq Conditions: Registry has certain value - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full User is running a particular OS - Windows Vista/Windows Server2008 (Any) (Service Packs=2 - ) User is running a particular OS - Windows 7/Windows Server 2008 R2 (Any) (Service Packs=1 - ) User is running a particular OS - Windows 8/Windows Server 2012 (Any)

flotek72 · ‎May 27, 2014

I'm using a Basic MSI installer and created my own .NET 4.5.1 prerequisite. When this prerequisite runs and installs, it says it requires a reboot. If I install the prerequisite by itself without involving InstallShield, it does not require a reboot. .NET Framework 4.0 prerequisite does not seem to require a reboot when triggered from the InstallShield installer. My prerequisites for 4.0 and 4.5.1 both have command line parameters of /q /norestart. What would be causing this in the prerequisite bootstrapper? Also, why does it have this problem with .NET 4.5.1 and not .NET 4.0?

flotek72 · ‎Nov 13, 2013

When I click on the Repair button in Add/Remove Programs to repair a program, it fails. The reason being is that I am not running as Administrator and something during the repair process needs elevation. That brings me to the conclusion that I should run repair as elevated. The only problem with this is that I don't know what command is being called when I click the Repair button. Also, I don't know where the command is located that is being called. I know where UninstallString and ModifyPath are in the registry, but of course there is no RepairString. Any ideas as to where that Repair button is getting the command to call?

flotek72 · ‎Oct 08, 2013

Learned a few more things while testing some more. It appears like the WindowsInsaller DWORD key needs to be added. Also, The new registry entry that is created as a custom action will have to have the same name as the GUID that was used for the original entry. This will essentially overwrite the original entry and function as if it was created by the installer itself.

flotek72 · ‎Oct 08, 2013

Is it possible that because the registry key under the Uninstall path was created by a Custom Action rather than InstallShield itself, that the Repair button is not showing? Could this be a bug? Update: Just did some testing with some other company's product on my computer and I'm really thinking this is a bug. Probably Microsoft related. To test, I exported a GUID key from the Uninstall path, then changed the GUID slightly and reimported the old GUID. I added the SystemComponent DWORD key with a value of 1 to the old GUID. Then I added a NoRepair DWORD set to 0 in the new GUID and under Add/Remove Programs it shows the product twice (which is expected). But one of them has the Repair button and one doesn't. This only happens for the Repair button. Modify button and Uninstall button can be shown or unshown based on the NoModify and NoRemove keys.

flotek72 · ‎Oct 07, 2013

I have a Basic MSI Project that when Installed, I only see Uninstall and Change in Add/Remove Programs. I've looked at many posts on this forum and on Google but have not found a working solution on how to enable the Repair button. Here is a list of things I have tried: There is no ARPNOREPAIR property in my property manager. I created a NoRepair DWORD key with the value of 0 and a NoModify DWORD key with the value of 1 in the Uninstall registry key for my company's product. I tried every combination of values for these 2 keys and nothing worked. Disable No Repair is set to No in General Information in InstallShield. I found no InstallScripts or Custom Actions set up that would disable that Repair button. Any ideas on how to get this Repair button to show? Update: After a little more digging, it looks like the registry key for my company's product was disabled using SystemComponent DWORD set to 1. A new registry key was created with a custom action which is the entry that shows in Add/Remove Programs. I have still tried everything above on this CA registry key with no luck in getting the Repair button to show.

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Pulling prereq from another location

Behavior tab

Prerequisite showing on OS that was not specified

.NET Framework 4.5.1 requiring a restart when set as prerequisite.

What happens behind the scenes when clicking Repair button in Add/Remove Programs?

Solution

Re: How to enable Repair button in Add/Remove Programs (Programs and Featues)

How to enable Repair button in Add/Remove Programs (Programs and Featues)