It would be nice if you told us what you were working with from the beginning. What a waste of my time. Chad ... View more

You should be able to use *.* in the RemoveFiles table. Have you tried that? I use it and it seems to do exactly what one would expect. Chad ... View more

Have you considered using the RemoveFiles table? I always try to use native MSI capabilities whenever possible, and only extend using Custom Actions if there is no other good way. I assume someone wrote this Delete function. It doesn't seem to be one that is built in to InstallScript language as far as I can tell. There is a DeleteFile built in that I can see. Even here, Flexera recommends using the RemoveFiles table if possible. Project: In a Basic MSI or InstallScript MSI project, this functionality might be better achieved by using the native Windows Installer RemoveFiles action. For more information, see the Windows Installer Help. http://helpnet.installshield.com/installshield22helplib/Subsystems/installshield22langref/helplibrary/LangrefDeleteFile.htm Chad ... View more

It sounds to me like the new EXE from Python includes an MSI nested inside of it. That's what is throwing the error is you have one MSI already running and when you run the EXE it sounds like it is unpacking an MSI and trying to run it. Can't have two MSI files in Execute mode at the same time in this fashion. Chad ... View more

More and more I try to take as few dependencies on IS specific things so I would tend to sway toward NOT REINSTALL since it is an MSI-centric concept available in all authoring tools. Just my .02 Chad ... View more

Ah, yes, you are using the old InstallScript-only project type. It is going to copy each package into their own folders from wherever it is picking them up from. I'd imaging copying that much data would take some time. Chad ... View more

When you click on each package in the Suite UI you should have choices "Copy From Source Media" "Extract From Setup.exe" "Download From The Web" The first choice (which seems to be the default for me) seems like the choice you would want. It will put each package into a subfolder of its own outside of the Setup.exe using a unique folder name to put them in so that Setup.exe knows what to look for. What I'm confused about though is your claimed sizes are vastly larger than the maximum sizes allowed for a single file as well as the size of a CAB file. Some good info at this web site. http://www.installsite.org/pages/en/msifaq/a/1043.htm Chad ... View more

An external UI is one that is written in some other language but tied into the MSI so you can have a completely custom user experience. You would know if you were using one I would think. In InstallSield, with your project open, go to the Direct Editor and choose the MsiEmbeddedUI table and see if you have any entries in there. If you did not in 2016, but you do after converting to SP2 that could be an issue. Chad ... View more

Are you attempting to use an external UI in your project or do you think that's a bogus message on this machine that is having the issue? Problem with asking on this board is we are all mostly a collection of other users. We have no control over the updates or what Flexera actually changes in their product, nor do we know what they did actually change, and debugging a product error like that is going to be related to some design consideration I suspect. Do you have a support contract with Flexera? If so I would report this as a bug, return the license temporarily, uninstall SP2 and reinstall 2016 if needed and then relicense it. That's what I would do, anyway. Chad ... View more

Not at my current company, but at a prior job I had a similar build. I set up all of the most common files that were not language specific into a merge module that I shared across the various installers. Those core files that did the meat of the work. It built the Merge Module once and it seemed to process the Merge Module faster as it incorporates it into each installer. Wouldn't work in every case, but it helped cut times by about 1/4 in this situation. Chad ... View more

If you go to the Tools menu and click on Options... there should be a Prerequisites tab that you can inspect to see the location(s) where it will be looking for the PRQ files to reside on a system. Since they are custom PRQ files - what I find easiest to do is to get them from another system that is able to currently build the project. Copy over the .PRQ and each folder that represents the files called out for in the .PRQ. Maybe a build server, or maybe a coworkers machine that shares them with me by putting them in a ZIP file, etc. As far as telling what the name is of each PRQ file - that should be in the error messages when you try to build. I've found that about the easiest way to tell the specific names it is looking for. I hope that helps some. Chad ... View more

This sounds like it would be related to User Account Control (UAC). If you read this page it might help explain some of it. Specifically, I think this relates to what you are describing. User accounts that are members of the local Administrators group run most applications as a standard user https://technet.microsoft.com/en-us/library/cc709691(v=ws.10).aspx Chad ... View more

Superfreak3 wrote: I would agree with that but it works for us. What is more Pennsyltucky is that Microsoft/Windows Installer just doesn't fully utilize the fourth segment of the version. Nah, those guys all came from North Florida. *chuckle* ... View more

Superfreak3 wrote: I know it may be strange to some. QUOTE] A bit Pennsyltucky I think. Chad ... View more

I don't believe that InstallShield 2014 has support for Windows 10. Since Windows 10 didn't ship until 2015 there was no chance for Flexera to develop 2014 with Windows 10 in mind. Read the first few lines here. http://helpnet.flexerasoftware.com/installshield22helplib/helplibrary/whats_newIS2015.htm Chad ... View more