Thanks anyway. Shame that we have to tell people they need .NET Framework just for the installer but not the product itself now. Bit difficult to explain, but anyhow.  Our installers are so massive we don't have the time or money to rewrite them into something else so I guess we're stuck with this until we can move away from InstallShield completely. We're still on IS 2012 cause it hasn't really improved in 11 years and it wasn't very good in the first place, but it was good for it's time (20+ years ago). 😉 ... View more

Did you ever get a solution to this? Thanks in advance. ... View more

Did you ever find a fix for this as I have the same problem with .NET dlls having converted from .NET 4.8? Thanks in advance. ... View more

Ok thanks. Makes sense. Unfortunately we have no choice but to run RDP as it's installed on a VM. ... View more

I also have this problem it's almost unusable. Did you ever get to the bottom of this? I'm using InstallShield 2012, but the text editor is so slow it's almost unusable. ... View more

This was a very helpful post, thanks. Could I ask that this kind of information is added to the online help (if it hasn't been already) so developers know how to use these parameters. Examples are always the most useful part of online help. ... View more

Any update on this? We don't have the .NET Core installer PRQ at all. Where can I download it from? ... View more

Yes, including the following conditions seems to work well. Tested on Windows 2012, Windows 10 old, Windows 10 new and it appeared to do everything it was supposed to do. <conditions> <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" FileName="Release" ReturnValue="528049"/> <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" FileName="Release" ReturnValue="528040"/> </conditions> I will add that .NET Framework installer for 4.8 is incredibly slow. There's a bit where it sits at about 15-20% done for a long long time and then suddenly completes the rest. Not much happening on the CPU or disk, so no idea what it is thinking about all that time.  ... View more

Is it just a case of adding another condition line to include the second release version? <conditions> <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" FileName="Release" ReturnValue="528049"/> <condition Type="2" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" FileName="Release" ReturnValue="528040"/> </conditions> ... View more

Sorry I got the numbers the wrong way around, it works for 528049, but since then MS have changed the Release version to 528040, so the pre-requisite doesn't realise the .NET 4.8 is already installed when it is, tries to install it and then fails. ... View more

Thanks, this works for Windows prior to May 2019 Update, where the Release number is 528040 instead of 528049. See this articles... https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed#ps_a Any idea how to make the pre-requisite check different release values on different OS versions? ... View more

I have the exact same problem with an Installation I've just updated. I have a number of components that install the same files but to different places and am now getting the feature transfer error the system cannot find the file specified with the file name being an .rra one. Did you ever get this resolved? ... View more

I had this problem too. I wrote a c# assembly to do all the things that InstallShield was useless at, including deleting a web application, for which here is the code (which I call from InstallScript)... [CODE] [ComVisible(true)] public bool DeleteWebApplication(string webSite, string webApplication, ref string errorMsg) { // The result. bool result = false; try { // Get the server manager. ServerManager sm = new ServerManager(); // Find the virtual directory. Site site = sm.Sites[webSite]; // "Default Web Site" Application app = site.Applications[string.Format("/{0}", webApplication)]; // "iManager" if (app != null) { // It does exist, let's delete it. site.Applications.Remove(app); sm.CommitChanges(); } // Success. result = true; } catch (Exception ex) { // Failure to get property, fill in the error message. errorMsg = ex.Message; } return result; }[/CODE] ... View more

The fix for Windows 10 is that on the machine you are building your setups you again need updated SetupExe.X.manifest files in your InstallShield installation folder, e.g. The 3 SetupExe.*.manifest files from C:\Program Files (x86)\InstallShield\2012 SAB\Support\. Edit the compatibility section in all 3 files so it looks like this... Then rebuild the setups and magically InstallShield will recognised Windows 10 as major OS version 10. ... View more

It is of course broken for Windows 10, which should report the version as 10, but InstallShield reports it as 6.2 instead. 😞 ... View more