If setup is installed on machine and if I try to install it again on the same machine than it exits installation with the message "Already installed". In this case, what I want is that if application is already installed then the installer will repair it.
How can we do this?
If the installation is actually broken (like a file is missing) then when you re-run the installer it should give you the repair option. Otherwise, if it thinks the installation is normal then it will say it's already installed.
I think there's always a repair option in the add/remove program entry. However, that won't work if your install files were in a temp location and are now gone.
Related
Once I access add or remove programs I was not able to locate my desired program to uninstall. After this, I decided to to try and use IObit uninstaller to try and find it, but that couldn't either. The program can still be found in my Program File directory and it acknowledges that I have it installed when I try to reinstall it. A system restore was no help either. Netbeans is the program.
The below is a custom installer / uninstaller approach for NetBeans - a package in a proprietary format (non-MSI). For normal uninstall of Windows Installer packages see this "reference answer" instead: Uninstalling an MSI file from the command line without using msiexec.
I see NetBeans in the Add / Remove applet just fine - just right-click and select "Uninstall".
I suppose the entry could be missing on your system. If this is the case you can try this:
Go to the NetBeans installation folder and double click Uninstall.exe.
On my system the installation path is: C:\Program Files\NetBeans 8.2.
You should get an uninstall dialog with a couple of options, set options as appropriate and click Uninstall.
I'll throw in the uninstall dialog so people can see the options - I suppose it could be helpful for someone at some point. I didn't run the actual uninstall, please update this answer with any extra steps necessary once you do run it:
I am using install4j 6.1.3 to create installer.
There is Uninstall previous installation action as the first action of gthe Installation action set.
But when doing upgrade, I always get the error message
could not delete {installedDir}\.install4j
during Uninstall previous installation action on Windows platform.
I've tried to set the Uninstallation policy to If created, but not for update, but it still not work.
Does anyone know what's the problem here?
How to avoid install4j deleting .install4j directory when doing upgrade?
This means that some process that uses a JAR file of the install4j runtime is still running, likely a launcher.
You cannot avoid deleting the runtime files during an uninstallation, you would have to make sure that no launchers are running. The "Check for running processes" action will help you to do that.
Whenever I try to install the Visual Studio SDK I get the following error:
Windows Program Compatibility mode is on. Turn it off and then try Setup again.
I have checked and Compatibility mode is not turned on. From what I've read, renaming the installer to vssdk_full.exe should help. That hasn't had any impact.
I got the installer from Microsoft's website.
What do I need to do to get this to install?
Are you installing on Windows 10? If so, then I have the same problem and it seems as though the current SDK setup is checking the Windows version and 10 isn't currently supported. See https://social.technet.microsoft.com/Forums/en-US/77c61be0-1303-4040-a587-62843d321159/visual-studio-2013-sdk?forum=WinPreview2014General for more info
I have managed to get it to install on windows 10, download the sdk, it will download vssdk_full.exe, run this with /layout path which will extract the actual setup file.
Then set compatibility on the new file to win 8 and it will install just fine.
You might not need to do the/layout thing but that is what I did.
ed
I had the same problem. I downloaded .iso file with install package form the internet. Then I mounted it using PowerISO and tried to start it from virtual CD drive. It ended up in the same message as above.
I looked it up and thought that in Properties of .exe install file, it's enough to uncheck some boxes compability section. But nothing was checked.
Soon afterwards I unzipped the package to a temporary directory with PowerISO and installed Visual from there. Worked without problems.
I had this problem, I renamed the instalation file to "vssdk_full.exe" and it installed without problems.
I need to access some source code stored on SourceForge using CVS.
I used (many computers ago) to use WinCVS, so I downloaded it from SourceForge and installed it on this machine, which runs Windows XP 64-bit (latest SP).
However, during the second part of the install, when it tries to install CVSNT, the install asks all the usual questions, and hangs during the actual install.
I have traced the install using ProcMon, and the installer starts up, creates a temporary file in my temp directory (which is on drive E:), and then executes it.
I can't see any particular reason why the install hangs - there is no obvious loop. Both the original installer, and the temporary file create 2 threads, and one thread exits. So I guess the other thread is waiting for something which never happens.
Any idea how to proceed from here?
The issue is that the installer doesn't like the default installation path of c:\Program files (x86)\cvsnt — if you use c:\cvsnt the installer will proceed.
Update: this appears correct. If you still would like it in the default location under C:\Program Files (x86)..., use the 8.3 name (you can find it with dir /x), usually C:\PROGRA~2. As you can see in the screenshot, the last step appears correctly now. With a path with a space in it, it would hang forever.
Second part of wincvs --> cvsnt.exe get hangs with windows 7 due to incompatible, So you may try tortoiseCVS. It has the portable version and also working fine
SOLUTION FOR Windows 8 64-bit:
On Windows 8 64-bit I was unable to install CVSNT (even to c:\cvsnt), but I solved the problem by simple copy the whole CVTNT directory from my old pc.
I copied to C:\Program Files (x86)\cvsnt (exact location where wincvs expected to find cvsnt).
We had a similar problem on a machine at work (the difference being it was Windows 7 64-bit in our case). Even though the user had admin privileges, we were only able to resolve the issue by logging on directly as the admin before installing cvsnt.
Do not install the version of CVSNT that comes with WinCVS. It's an old, outdated, buggy version. Install a later release (at least 2.5.0.4).
I have an InstallShield 2009 Basic MSI project that I've modified to load the 3.5 SP1 redistributable for the .NET framework. It loads fine but as soon as it finishes it displays a prompt saying the system has to reboot, and you can either say yes and it will reboot, or no and it will stop the install.
I then went in and edited the .NET Framework 3.5 Service Pack 1 (Web Download) redistributable using InstallShield's prerequisite editor. I changed the behavior if it needs a reboot to 'Note it, fail to resume if the machine is rebooted, and reboot after the installation'. I interpreted that as meaning the reboot prompt would not be shown until the end of the install, but it still showed up in the same place.
Is there a way to suppress the prompt until the end of the install? Do I need to pick a different option from that drop-down in the pre-req editor?
Bonus question: if I need to run my install unattended, is there a way to automatically have it reboot after the entire install is finished if one is needed?
EDIT:
The command switches mentioned below would probably work, but in the case of running the install unattended it will be launched from another program, and I really don't want to modify that app just for this one case. Here's a better question: is a reboot really required after installing .NET 3.5 SP1, or is it one of those things where a reboot would be good but is not absolutely needed for programs to start using the 3.5 framework?
If you type msiexec /? in the Start -> Run box, you'll get a screen with command line options for the MSI runtime, including the following:
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
You can suppress the reboot prompt entirely by adding the following to the MSI's setup command line:
REBOOT=ReallySuppress
But then it won't prompt at the end of your complete install, as it sounds like you were hoping for; you're just stopping the prompting altogether.
As for your additional question, you can force a reboot with the following switch:
REBOOT=Force REBOOTPROMPT=Supress
Here you're telling the Windows Installer to prompt for a reboot always, and then suppressing the prompt so it just happens.