InnoSetup not asking for destination folder [duplicate] - inno-setup

I create my application with py2exe and package it into an installer exe using Inno Setup on Windows 7. The installer created this way can then be installed on both Windows 7 and Windows 10 systems. When it works, the installer shows following screens in sequence:
Welcome screen
EULA screen
default (or previous install) location, allowing user to select new install location,
Confirming install location, and
usual install screens.
This is the behavior I get with Inno Setup 5.5.5 or lower.
With Inno Setup 5.5.7 and higher (did not try 5.5.6), the installer is created normally and can be setup as above on Windows 7. However, the same installer fails to show screens 1 and 3 from above list during setup on Windows 10: setup directly starts with EULA screen and then jumps to confirm install location. The confirm screen doesn't even show which directory the installation will be done.
Continuing allows the installation to happen in the default location and the application works normally. Not knowing the install location is highly annoying and undesirable.
The .iss file that I use (see below) is identical across the different Inno Setup versions that I have tried. In the file, the DefaultDirName is set explicitly (based on the version of the application).
[Setup]
AppName=MyApp
AppVersion=2.0.1
AppVerName=MyApp 2.0.1
DefaultDirName=C:\MyApp_v2.0.1
[Files]
Source: "MyApp_main.exe"; DestDir: "{app}\"; Flags: ignoreversion
I also tried packaging the installer with Inno Setup (5.5.7 and 5.5.9) on Windows 10, but it had the same behavior.
I was wondering it I need to set additional parameters for the installer to work correctly on Windows 10 also for newer versions of Inno Setup?

Quoting revision history for Inno Setup 5.5.7:
As recommended by Microsoft's desktop applications guideline, DisableWelcomePage now defaults to yes. Additionally DisableDirPage and DisableProgramGroupPage now default to auto. The defaults in all previous versions were no.
Conclusion:
The Welcome page is not shown anymore by default. To enable it, set the DisableWelcomePage:
DisableWelcomePage=no
I do not think you are right with your statement that the page shows on Windows 7.
The "Select Destination Location" page is shown for fresh installations only, not for "upgrades". So this has nothing to do with Windows 7 vs. Windows 10. The difference is probably that you have the application installed on Windows 10 system; and you do not have it installed on the Windows 7 system.
To show the page always, set the DisableDirPage:
DisableDirPage=no
Thought as mentioned in the quote above, the defaults are recommended, so you should follow them.

I found another parameters that affects it.
CreateAppDir=no
In CreateAppDir page says:
If this is set to no, no directory for the application will be created, the Select Destination Location wizard page will not be displayed, and the {app} directory constant is equivalent to the {win} directory constant. If the uninstall feature is enabled when CreateAppDir is no, the uninstall data files are created in the system's Windows directory.

here I used
[Setup]
DisableDirPage=No
by default this parameter is seted to auto.
If this is set to auto, at startup Setup will look in the registry to
see if the same application is already installed, and if so, it will
not show the Select Destination Location wizard page.
See more in https://jrsoftware.org/ishelp/index.php?topic=setup_disabledirpage

Related

How to make uninstallation work by right clicking app icon from start menu [duplicate]

I created an install file with Inno Setup 5.5.9 that I then ran on a Windows 10 machine. My only problem has to do with uninstalling the program. I can use the Control Panel just fine to uninstall. But in the Start menu, when I right click on the shortcut that launches my program, there is no option in the context menu to Uninstall. Other programs do have this option.
Is this a Windows 10 thing that I can't get around?
Does the program need to be installed under Program Files or Program Files (x86)?
Or is there a change I can make to my Inno script to have the uninstall option show up?
I'm a standard user on the Windows 10 machine, and therefore installed the program without administrative privileges. Does that have anything to do with it?
Only "Windows apps" (aka Universal Windows Platform [UWP] apps, Windows Store apps and Metro-style apps) have working "Uninstall" command.
Classic "Desktop apps", like those installed with Inno Setup, do not. Their Uninstall command only opens "Program and Features" Control Panel. Check other major desktop apps, like Microsoft Visual Studio or Google Chrome. Their "Uninstall" command behaves the same. And they are definitely not packaged by Inno Setup.
You would have to re-package your desktop app to turn it to "Windows app", instead of using Inno Setup.
I had the same problem.
In my case sometimes only the uninstall shortcut in windows start menu disappers.
I somehow fixed it.
Just use in Icons-section the command to create this shortcut twice. Their names need to differ.
For example:
Name: "{group}\{#Uninstall_Name} {#MyAppName}"; Filename: "{uninstallexe}";IconFilename: {app}\{#IconFileStartDesktop};
Name: "{group}\{#MyAppName} {#Uninstall_Name}"; Filename: "{uninstallexe}" ;IconFilename: {app}\{#IconFileStartDesktop};
If the first uninstall-shorcut does not show up, the second one enter code here will to it.

EXE created by ant build on execution directly getting installed in TEMP path [duplicate]

I create my application with py2exe and package it into an installer exe using Inno Setup on Windows 7. The installer created this way can then be installed on both Windows 7 and Windows 10 systems. When it works, the installer shows following screens in sequence:
Welcome screen
EULA screen
default (or previous install) location, allowing user to select new install location,
Confirming install location, and
usual install screens.
This is the behavior I get with Inno Setup 5.5.5 or lower.
With Inno Setup 5.5.7 and higher (did not try 5.5.6), the installer is created normally and can be setup as above on Windows 7. However, the same installer fails to show screens 1 and 3 from above list during setup on Windows 10: setup directly starts with EULA screen and then jumps to confirm install location. The confirm screen doesn't even show which directory the installation will be done.
Continuing allows the installation to happen in the default location and the application works normally. Not knowing the install location is highly annoying and undesirable.
The .iss file that I use (see below) is identical across the different Inno Setup versions that I have tried. In the file, the DefaultDirName is set explicitly (based on the version of the application).
[Setup]
AppName=MyApp
AppVersion=2.0.1
AppVerName=MyApp 2.0.1
DefaultDirName=C:\MyApp_v2.0.1
[Files]
Source: "MyApp_main.exe"; DestDir: "{app}\"; Flags: ignoreversion
I also tried packaging the installer with Inno Setup (5.5.7 and 5.5.9) on Windows 10, but it had the same behavior.
I was wondering it I need to set additional parameters for the installer to work correctly on Windows 10 also for newer versions of Inno Setup?
Quoting revision history for Inno Setup 5.5.7:
As recommended by Microsoft's desktop applications guideline, DisableWelcomePage now defaults to yes. Additionally DisableDirPage and DisableProgramGroupPage now default to auto. The defaults in all previous versions were no.
Conclusion:
The Welcome page is not shown anymore by default. To enable it, set the DisableWelcomePage:
DisableWelcomePage=no
I do not think you are right with your statement that the page shows on Windows 7.
The "Select Destination Location" page is shown for fresh installations only, not for "upgrades". So this has nothing to do with Windows 7 vs. Windows 10. The difference is probably that you have the application installed on Windows 10 system; and you do not have it installed on the Windows 7 system.
To show the page always, set the DisableDirPage:
DisableDirPage=no
Thought as mentioned in the quote above, the defaults are recommended, so you should follow them.
I found another parameters that affects it.
CreateAppDir=no
In CreateAppDir page says:
If this is set to no, no directory for the application will be created, the Select Destination Location wizard page will not be displayed, and the {app} directory constant is equivalent to the {win} directory constant. If the uninstall feature is enabled when CreateAppDir is no, the uninstall data files are created in the system's Windows directory.
here I used
[Setup]
DisableDirPage=No
by default this parameter is seted to auto.
If this is set to auto, at startup Setup will look in the registry to
see if the same application is already installed, and if so, it will
not show the Select Destination Location wizard page.
See more in https://jrsoftware.org/ishelp/index.php?topic=setup_disabledirpage

InnoSetup no longer allows user to pick installation directory? [duplicate]

I create my application with py2exe and package it into an installer exe using Inno Setup on Windows 7. The installer created this way can then be installed on both Windows 7 and Windows 10 systems. When it works, the installer shows following screens in sequence:
Welcome screen
EULA screen
default (or previous install) location, allowing user to select new install location,
Confirming install location, and
usual install screens.
This is the behavior I get with Inno Setup 5.5.5 or lower.
With Inno Setup 5.5.7 and higher (did not try 5.5.6), the installer is created normally and can be setup as above on Windows 7. However, the same installer fails to show screens 1 and 3 from above list during setup on Windows 10: setup directly starts with EULA screen and then jumps to confirm install location. The confirm screen doesn't even show which directory the installation will be done.
Continuing allows the installation to happen in the default location and the application works normally. Not knowing the install location is highly annoying and undesirable.
The .iss file that I use (see below) is identical across the different Inno Setup versions that I have tried. In the file, the DefaultDirName is set explicitly (based on the version of the application).
[Setup]
AppName=MyApp
AppVersion=2.0.1
AppVerName=MyApp 2.0.1
DefaultDirName=C:\MyApp_v2.0.1
[Files]
Source: "MyApp_main.exe"; DestDir: "{app}\"; Flags: ignoreversion
I also tried packaging the installer with Inno Setup (5.5.7 and 5.5.9) on Windows 10, but it had the same behavior.
I was wondering it I need to set additional parameters for the installer to work correctly on Windows 10 also for newer versions of Inno Setup?
Quoting revision history for Inno Setup 5.5.7:
As recommended by Microsoft's desktop applications guideline, DisableWelcomePage now defaults to yes. Additionally DisableDirPage and DisableProgramGroupPage now default to auto. The defaults in all previous versions were no.
Conclusion:
The Welcome page is not shown anymore by default. To enable it, set the DisableWelcomePage:
DisableWelcomePage=no
I do not think you are right with your statement that the page shows on Windows 7.
The "Select Destination Location" page is shown for fresh installations only, not for "upgrades". So this has nothing to do with Windows 7 vs. Windows 10. The difference is probably that you have the application installed on Windows 10 system; and you do not have it installed on the Windows 7 system.
To show the page always, set the DisableDirPage:
DisableDirPage=no
Thought as mentioned in the quote above, the defaults are recommended, so you should follow them.
I found another parameters that affects it.
CreateAppDir=no
In CreateAppDir page says:
If this is set to no, no directory for the application will be created, the Select Destination Location wizard page will not be displayed, and the {app} directory constant is equivalent to the {win} directory constant. If the uninstall feature is enabled when CreateAppDir is no, the uninstall data files are created in the system's Windows directory.
here I used
[Setup]
DisableDirPage=No
by default this parameter is seted to auto.
If this is set to auto, at startup Setup will look in the registry to
see if the same application is already installed, and if so, it will
not show the Select Destination Location wizard page.
See more in https://jrsoftware.org/ishelp/index.php?topic=setup_disabledirpage

5.2 and Windows 10 compatibility release

I know this isnt a dev question per se, but is there a timeline on a 5.2 build that can be installed on Win 10?
I think the issue i am seeing is just with the installer so an in place upgrade to Win 10 might work fine, but a clean install fails as it doesnt acknowledge IIS 10 or whatever version comes with Win 10.
Thanks!
Official answer - Windows 10 is not yet supported by the currently available Acumatica ERP installers, however the issue has already been fixed internally (AC-56069 - fixed in 4.20.2262, 5.10.0785, 5.20.1012 and newer). Following workaround can be used in the meantime:
Download the Orca tool to edit the MSI file: http://adriank.org/wp-content/uploads/2015/01/Orca.zip
Open the
MSI file using this tool (might be able to right click on MSI and
open with Orca)
Go to the LaunchCondition table
Drop/delete the IIS version condition (inside MSI, the LaunchCondition entry is IISVERSION >="#7"; system does a string comparison and "10" is
smaller than "7")
Save and close Orca
Run the setup
I can't give you an "official" answer but I can give you a work around.
If you download a utility called LessMSI you can extract the installation files. They will come out in a folder called "SourceDir". Simply take these and replace the files in your default installation folder or run them from another location.
Then you can proceed as normal.
The installer only checks if pre-reqs are installed and then copy's the files to the output location. If you have IIS already setup with dotnet support then the rest will be fine.
I do this frequently if I have to install a site with a specific version in order to upgrade or test a client's snapshot.
I have 4.1,4.2,5.1,5.2 running on my Windows 10 workstation as I type

Install errors in InstallShield 2008 Premier Edition

I have a setup which has been created using InstallScript MSI project type. This problem is encountered by our client and he wants a quick solution.
Let's assume I have initiated the installation from a path like
C:\Setup_V_1.0.0931.1
Inside this folder I have Setup.exe through which I will install the product. After installation or after some days pass I will change the path to:
C:\New\Setup_V_1.0.0931.1
and this time I want to modify the setup. Actually we are supporting 3 features: Server, Client and Service.
This time I want only Client and not Server. So I will click on the Setup.exe or click on Uninstallation Icon in the Startup Menu which will lead to Maintenance Mode there you have an option to Modify, Repair or Remove. I choose Modify and select the feature, but as the installation progresses, this error message will pop up:
Setup could not find a file on the specified path or Disk. Please check
that the proper disk is inserted or specify a new path. Unable to
locate file c:\New\Setup_V_1.0.0931.1\setup.msi
Then, another popup will be shown saying:
Error: 1706. No Valid Source could be found for product. The Windows
Installer cannot continue.
The next error message is:
Error: 1603. Fatal error during installation. Consult Windows Installer
Help (Msi.chm) or MSDN for more information.
But if I change the path to its original location, it works fine.
How can I solve this?
I event checked in this registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\{Product-Key}
This key contains a lot of information inside InstallProperties. There is a key called InstallSource and its value is C:\Setup_V_1.0.3909.1\. Even after changing this value installshiled is still showing errors.
I found the same registry information for Uninstallation Information:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Product-Key}
In your properties change ReinstallMode (or maybe Reinstall I forget which) from omus to vomus
the v means cache your install, so it will put your .msi file in c:\windows\installer so it can be used later.
When installing a MSI, Windows Installer saves the original MSI path in registry (the InstallSource entry you mentioned). When running the MSI in maintenance mode, Windows Installer will use this path to find the installation data (CAB files).
When you move the MSI, the path stored in registry is no longer valid, so Windows Installer cannot find the installation data.
A possible solution is to use "Add or Remove Programs" or "Programs and Features" in Control Panel to modify the installation. This way the cached MSI is used.

Resources