There isn't an easy work around. Windows Installer enforces a 1 installation at a time rule through the use of a mutex. You need to create a bootstrapper / chainer to serialize the installation of your packages. Visual Studio Deployment Projects don't support this. I'd suggest looking at Windows Installer XML (WiX) and it's Burn boostrapper / chainer engine.
(To be more concrete in "Third party tools":) Buy InstallShield or Advanced Installer or InstallAware, this are the tools with ready GUIs to do such easy bootstrapping.I would recommend the second out of them. Starting another MSI are only two clicks. Similar with the other. But there are BIG differences between the three, especially InstallAware is special.
Use the InstallShield "Suite" project type, if you buy the Premium Edition of InstallShield. Costs big bucks, but has a friendly user interface. I was successful using it before some years, but I had to work around a handful of bugs as always with IS (but I guess you will discover bugs with most tools. Way it is.)
I want to create a Windows Installer, the 1st step I want it to call another installer (will install dependent components of my application), and the 2nd step I want to install my own application. I want to do all tasks in one installation process, and I have the dependent component installation package at hand (an exe file).
If you want to create a Windows Installer (MSI) package then take a look at Windows Installer XML (WiX). But you'll want to get your head around how MSI works first. WiX is really simple once you understand Windows Installer, but trying to learn both at once can be rather confusing.
I'm trying to start a different installer after the installation of the first one is done. Is this possible? What my idea was, was that I would build the installer that I want to execute at the end would be build first, and then I would include that in the first installer. The problem is that I don't know where to put the CustomAction.
The way forward here would be to use the Installshield Suite project.
This will allow you to wrap multiple installers into a single setup.exe and have them install one after the other.
More information on Suite installers can be found here:
The second option is to look at Chained MSI's - this will allow you to run a 2nd .msi file after the first completes.
Be aware that Chained MSI's can have issues if reboots are needed or during certain upgrade situations - so make sure you fully test this.
I'm wondering if anyone can help me figure out how to fix the Error code: 87 "Another Installer is already running". I've tried all of the suggestions I could find. I've stopped Windows Installer and I don't see any other installers/set-ups in my currently running processes. I've tried restarting my computer and going through the same process again several times. I've posted images of my currently running processes (only background ones, not windows ones, since I don't think the problem is there after looking through them, but maybe I'm wrong?). Maybe I'm just overlooking the other install process? I'm the only user and administrator. Windows 11. First time cc/illustrator install on this machine. Ideas? Thanks in advance.
Ok, we figured it out. For some reason installing creative cloud on a windows admin account results in permission issues, so we had to create a non-admin, organizer user (new admin users also had the same issue) which allowed for the installation of creative cloud for the machine. All adobe apps were then able to be installed via any account (admin or otherwise). Weird issue.
Illustrator. Yes, I've triple checked that there are no pending Windows updates (actually had to install a few, but the error persists post-updates and there are no others supposedly pending). I've tried redownloading the Illustrator set-up.exe and still have the issue.
Update for anyone who sees this issue and is having something similar happen: the support team is going to get back to me since they couldn't figure out what's causing the issue via remote access to my computer either. Will try to remember to give an update with the solution when it's figured out.
This is my personal computer (need to do stuff at home), so no, my school has never had access to it. Yes, I'm following those steps. The CC desktop app isn't installing either (I tried installing that individually without the coupled illustrator download and it had the same issue). I've rebooted my computer a couple of times and there don't appear to be any other updates unless my apps are keeping secrets (lol) or I'm missing them? Would a pending update in an an application that isn't running that doesn't show up in task manager stop the installation process? I can try combing through every application that's not running I guess?
Upon attempting to install Adobe Photoshop CS6 Extended edition, a pop up box appears which gives the message at the foot of the post, however no other installers are running. I've tried rebooting the PC and all my current software is up-to-date but this message appears every time I insert the disc and attempt to install the programme.
Ultimately, shortly after my failed attempts to install Photoshop, Microsoft Office 2010 caused a computer crash, which corrupted a number of Office files and in order to avoid further complications, Windows elected to revert to an earlier back-up of the system (pre Office installation).
Please check your task manager to see if you have any other instances of Setup.exe running. It is possible that another application you previously attempted to install is interferring with the install process.
I have now looked at the Task Manager and closed all open installers and am still faced with the same message. I have since attempted to install the programme on an older version of Windows (XP) as a trial on a different PC and found it to work fine, so assume it has something to do with installation on the Windows 8 Operating System specifically.
There are almost 40 Background Processes and 21 Windows Processes running by default in the task manager at the same time I try to install Photoshop, but do not want to start closing these down without knowing the result of doing so. I did close the Windows Installer which was running, but this made no difference to the message displayed by Photoshop.
An easier way of stopping Windows Installer is to open Task Manager in Windows 8 (Cntl-Alt-Delete), scroll down to Windows Installer, right click on it and choose End Task, and voila! If you are installing Photoshop Elements and Premiere Elements, you may need to stop Windows Installer more than once.
This has got to be an Adobe installer configuration problem. This happens to me on multiple Adobe products, some off Creative Cloud, and also Premiere Elements which I think is a separate installation process. I've tried disabling Installer, and all the other recommendations without any joy. The only think that seems to work is to reboot into Safe Mode and run the install which is incredibly annoying. All my other apps update fine, just Adobe which fails. I've reloaded my PC from scratch, and now have a new PC with the same problems. Similar configrs though - Windows 10 x64.
PS: I also use both because both viewers are unstable for multiple log ins at the same time with the only solution of deleting the settings in the Appsdata/Roaming folder. And Firestorm at least you can back up the settings data easily
I use the OS Grid of Firestorm for running my alts in and for OS Grid usage and use the official viewer for my main avatar.
I was trying to upgrade to the latest version of Firestorm and the installer wouldn't even run. I tried downloading with both Edge and firefox with the same result. I am afraid to try a clean install if the installer isn't even running. Anyone else having this issue or know of a solution?
I am using the OS Grid version of FS (not the latest but the previous) and have had no issues with alts in SL or Kitely. If the mesh uploader isn't happy (mostly complex buildings which I seldom make any longer) then I use the Linden viewer to upload. I have had NO ISSUES so I don't think it is a FS problem per se. Having two versions of FS running and being in both SL and OS has had issues in the past. I suggest you just use the OS grid version and log on people as needed. If that doesn't work then it is most likely something ELSE in your system.
c80f0f1006