Hi, I am running IS2019 and am working with an InstallScript project. My test OS is Server 2019. I am currently using the IS-provided PRQ to install vcredist 2019 (x86). The problem is that it asks for a reboot when it is done, for no apparent reason. At least on Server 2019 anyway. If I run the vcredist installer manually on Server 2019, it completes fine without asking for reboot. This is my baseline test to determine if a reboot is required. I have also written some code to install it from script, and it also returns 0 which I assume means no reboot needed. As expected. So, I'd like to know if anyone knows why the PRQ asks for a reboot here. And I'd also like to know if the vcredist installer actually returns a non-zero value if a reboot is required, since I am looking at getting away from this apparently defective PRQ. Thanks! ... View more

Hi, I am running IS2019 and am working with an InstallScript project. My test OS is Server 2019. I am reluctantly (see my other post) utilizing the IS-provided prerequisites to assist in installing some prerequisites, but I am trying to move away from it, and go back to installing my prereqs in script so I have more control over the number of reboots. My ultimate goal is to detect reboots if needed for all prereqs, hold off all reboots until the end of the install and also no longer use PRQ's. I am seeing a problem with .NET 4.8. If I run the 4.8 installer manually on Server 2019, it always wants to reboot. I don't know why, but it does. That is not the issue (though I'd like to know). But this is my baseline test to determine if a reboot is required. The PRQ installer also detects that 4.8 needs to reboot, and asks to reboot before my main install starts. All ok. But when I do it via script, it always returns with a return code of 0, meaning no reboot needed, which I believe is incorrect at this point. How can I install .NET 4.8 from script if I cannot determine if a reboot is required? I tried "extracting" the .NET framework from its EXE prison and running THAT, but MS will not allow that setup.exe to be run. It throws an error. Thanks! Code below. SdShowMsg("Installing .net 4.8...", TRUE); result = LaunchAppAndWait(SRCDIR ^ "prereqs" ^ "ndp48-x86-x64-allos-enu.exe", "/norestart /passive", LAAW_OPTION_WAIT); NumToStr(strResult, result); MessageBox ("Return value from .net 4.8: " + strResult, INFORMATION); // Return codes: https://docs.microsoft.com/en-us/dotnet/framework/deployment/deployment-guide-for-developers#return-codes if (result == 1602) then     MessageBox ("User cancelled. Aborting install", INFORMATION);     abort; elseif (result == 1603) then     MessageBox ("Fatal error during .net installation, aborting.", INFORMATION);     abort; elseif (result == 5100) then     MessageBox ("Computer does not meet system requirements, aborting.", INFORMATION);     abort; elseif (result == 1641 || result == 3010) then     MessageBox ("Restart required, saving for end of install. Continuing install.", INFORMATION);     BATCH_INSTALL = 1; endif; ... View more

I am working with a pure Installscript project. I am trying to include a PRQ that installs .NET 4.7.2, that I created and modelled after the earlier .NET PRQs that Installshield provides. I am finding that there is no ideal "behavior" setting for what to do when a reboot is indicated by the PRQ. For .NET 4.7.2, it usually does not require a reboot on most OSes, however on Server 2016, it does. This is true even if you manually run its setup.exe directly in Windows. This disparity is important. Most of the settings are useless. I found 2 candidates but neither works as needed. - If I choose "Note it, fail to resume if the machine is rebooted, and reboot after the installation" -- On Windows Server 2016 - it never reboots after main installation is over. -- On other OSes - works fine as no reboot is needed - If I choose "Prompt the user to reboot the machine even if nothing is detected, and resume on reboot" -- On Windows Server 2016 - reboots and works correctly -- On other OSes - reboots even though it is not required - very annoying.   I don't really understand why these reboot options are so wordy and full of things people would never want. I mean why would I want to reboot if NO REBOOT is indicated?? It makes no sense. I think I'm back to installing these prereqs in code. But if anyone has any suggestions to get this right I'd love to hear them. Thanks, Dave ... View more

InstallShield version 2018 SP1. After running into this problem I created a new Installscript build with only one change. I added the prerequisite .NET Framework 4.7.1. Everything else is defaults and I created the build. Upon installation on Windows Server 2008 R2, the prereq is installed and it asks for a reboot, I say yes. After the reboot the setup tries to continue. But the only thing that shows up is this error. See attached photo. I believe this may occur with any prereq that requires a mid-install reboot, but haven't had enough time to test that theory. I HAVE, however, tried different .NET prereqs, all with the same error after reboot. Any ideas? Thanks. ... View more

I am writing an InstallScript build, and trying to utilize the built-in prerequisites feature. The problem as you all know is that the prerequisites install themselves before any custom code can be run (even before OnBegin - I just think this is horrible... but here we are.) I would like to check that I am on a 64-bit OS before my prereqs install. This is because my build is 64-bit only. But not all my prereqs are 64-bit only, so what happens is that some of the prereqs install, then we get to the main code and I tell them "sorry - 64 bit only" so it ends up wasting time and installing things they don't need/cannot use. I cannot (more accurately do not want to) put conditions on the prereqs themselves because things like .NET 4.5.1 prereq are meant to install to either 32- or 64-bit Windows. I am left with the idea of creating my own prereq, that runs before all the others, to check for 64-bit OS, and then fail the installation if this check fails. Has anyone done this? If so, how did you do it? I suppose I could create a custom executable in C# that checks this and returns a return code. However it just seems there ought to be an easier way, perhaps using built-in features of the prereq editor? I might just go back to not using the prereq editor and running these installs myself. Seems more straightforward. Thanks. Dave. ... View more

Currently we use a spreadsheet to communicate what files need to go in the installer, where to put them, what registry entries are needed, shortcuts, etc etc. Once the spreadsheet is complete, it is given to the build person and there is a manual process of creating the installer by reading the spreadsheet and creating the IS project by hand. For subsequent builds, changes are highlighted on the spreadsheet and again a manual process to update the IS project. Essentially, the requirements for the build are listed in two places (and need to be maintained in two places) and there is room for human error when translating one to the other. Ultimately I'd like to have enough automation in the process to avoid stupid human mistakes. To have only one place where build details are stored, and have those details be accessible to people who do not have an InstallShield license. I noticed WiX does something like this where the install details are actually part of a Visual Studio project and are directly read in to create a build. Thats pretty sweet but learning WiX is a whole new battle. Does anyone have any suggestions in this regard? Thanks, Dave ... View more

I have an Installshield 2012 (installscript) build that seems to uninstall successfully, but does not get removed from "Programs and Features". I am suspecting this is related to 64-bit OSes specifically since the problem does not occur on 32 bit Win7 but does occur on Server 2008 R2. I am working on getting a 64-bit Win7 to verify. The build is created on Server 2008 R2 using Installshield 2012. I even stripped down the build to minimal script, so its not any crazy code that I am running. Has anyone seen this behavior? Is there ANY fat chance that moving to the Spring edition would help? Thanks! ... View more

I have a bunch of files that I manually register with the Global Assembly Cache, the problem is that if I do this 20 times in a row I see 20 cmd windows pop up and disappear, and while I am watching this I might briefly see one of them fail (I just happen to see FAIL in the cmd window before it goes away). I know I could comment out one at a time, but I am never sure if I am seeing the error every time I run, since it goes by so fast. The visual clue is intermittent. Is there any way to slow down, or log, the contents of a cmd window from a process that is launched with LaunchAppAndWait? Thanks ... View more

Hi I am trying to install Oracle ODP.NET drivers during my Installscript installation, on Windows Server 2008 R2. The oracle drivers come in the form of a series of BAT files, a bunch of subdirectories and helper executables (xcopy install). One of the Oracle provided batch files that gets called does something like this to create some registry entries: [CODE]REM setup registry entries for ODP.NET 4 echo Windows Registry Editor Version 5.00 > "%BAT_DIR%"\odp.net.reg echo [HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\ODP.NET] >> "%BAT_DIR%"\odp.net.reg echo [HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\ODP.NET\4.112.2.0] >> "%BAT_DIR%"\odp.net.reg echo "DllPath"="%REG_DIR%bin" >> "%BAT_DIR%"\odp.net.reg echo "PromotableTransaction"="promotable" >> "%BAT_DIR%"\odp.net.reg echo "StatementCacheWithUdts"="1" >> "%BAT_DIR%"\odp.net.reg echo "TraceFileName"="c:\\odpnet4.trc" >> "%BAT_DIR%"\odp.net.reg echo "TraceLevel"="0" >> "%BAT_DIR%"\odp.net.reg echo "TraceOption"="0" >> "%BAT_DIR%"\odp.net.reg echo "PerformanceCounters"="0" >> "%BAT_DIR%"\odp.net.reg echo "UdtCacheSize"="4096" >> "%BAT_DIR%"\odp.net.reg echo "DemandOraclePermission"="0" >> "%BAT_DIR%"\odp.net.reg echo "SelfTuning"="1" >> "%BAT_DIR%"\odp.net.reg echo "MaxStatementCacheSize"="100" >> "%BAT_DIR%"\odp.net.reg regedit /s "%BAT_DIR%\odp.net.reg" del /q "%BAT_DIR%\odp.net.reg"[/CODE] Note the registry keys specified. We know from working with 32 and 64 bit OSes that if you run this as a 32 bit process the registry items would get redirected to a \Wow6432Node subkey. Here is what I don't get. When I run the batch file myself from a command prompt, these reg entries get created in the correct 64 bit registry location. However, when I call the batch file from my install script (using LaunchAppAndWait) the registry keys are redirected under \Wow6432Node. I get that the installer is probably a 32 bit EXE... however then I don't understand why I am able to then (in InstallScript) copy the registry keys to the proper 64 bit location using RegCopyKeys. So I found my "solution" by copying the keys over... but I would really like to know the technical reason this is occurring. If anyone has insight I would appreciate it! ... View more

I am attempting to author an InstallScript installer that has 2 Release configurations. Configuration A contains Feature A, and Configuration B contains Features A and B. Basically, the B configuration includes a Security component that costs extra. - Is it possible at runtime, to determine which release configuration is being run? - Is it possible to assign different splash screens and displayed product names, etc. based on the Release configuration, (at design time would be fine for this one)? Or am I better off authoring a 2nd installer? Thanks ... View more