- Msi Wrapper Microsoft Download
- Msi Wrapper Download
- Msi Wrapper Install Arguments
- Msi Wrapper Microsoft Word
FREE DOWNLOAD MSI Wrapper EXE to MSI converter. Convert executable installers to MSI packages. It's fast, easy and free, Get it now! This indicates that the exe you were given by the vendor is simply a wrapper for an MSI - a wrapper that's doing a poor job of extracting its files. You can use procmon to see what's going on and they may help.
When investigating an issue with your Microsoft Office applications, you may need to determine whether you have the Windows Installer (MSI) based version of Office or the Click-to-Run (C2R) version of Office. These versions are based on different installation methods.
The MSI based version of Office uses Windows Installer technology, which is a traditional method of installing and updating Office. If you install Office by using MSI, you have to wait until the whole Office product is installed before you can open and start to use the product. The C2R based version of Office uses Click-to-Run, which is a Microsoft streaming and virtualization technology that allows you to open and start to use the product before the whole product is installed. Click-to-Run is the technology used to install Office 365 subscription products, while the MSI is used mainly to install the volume license editions of Office.
To find out whether your installation is MSI or C2R, in the Microsoft Office application, such as Word or Excel, go to File > Account. If you see an Office Updates section, the installation is C2R:
If there is no Office Updates section, then it is an MSI installation:
Active4 months ago
After way too many experiments, I've come to the conclusion that Windows Installer is simply bad technology. But the customers want MSI files.
So, how can I create an MSI file that extracts an EXE file to a temporary directory and runs it with options same or similar as were passed to the EXE file?
Options to an MSI are explained in Msiexec (command-line options) (low level 'run' of an MSI is msiexec option package.msi).
EDIT: mjmarsh's WiX solution looks like it works. I just haven't had a chance to try it yet (crunch time). If it works, I'll be accepting it.
EDIT: it does not work. Missing piece: attended/unattended does not seem to be available.
Anyway, the only to make this work at all would be for the custom action to kill its parent process!
EDIT: So somebody posted as a further answer wrapping the whole thing as a post-install custom action. Theoretically possible but since a reboot may be required (thanks MS for .NET 4 requiring a reboot sometimes) we have to do further hackery. So from the matrix of advantages:
No point.
Stein Åsmul25.6k1515 gold badges6161 silver badges129129 bronze badges
JoshuaJoshua27.1k55 gold badges5151 silver badges108108 bronze badges
Msi Wrapper Microsoft Download
12 Answers
Well, there is the free way and the $$$ way. I cannot document everything here, but this should get you started.
On a side note, yes, Windows Installer is a maddening technology. There are many times where I think a task will be straightforward, but it actually becomes complicated. You definitely have to immerse yourself to understand it.
In any case, here goes:
Free: WiX (here)
This is a free tool to generate MSI files from a set of XML configuration files. I'll leave you to find tutorials online, but here is the crux:
You can compress your EXE into the installer by using the following tag in the WXS file:
Then you can create a custom action which launches your EXE file:
Then you insert your custom action into the
InstallExecuteSequence
in the appropriate spot (I almost always run mine somewhere between InstallInitialize
and InstallFinalize
)$$$: Get InstallShield (HERE)
First create a 'Basic MSI' project and make sure you say you want no setup.exe generated. You set this in the Release settings.
Then you essentially do the same thing as with WiX, but you have a UI for it.
- You can specify your helper EXE file by using the Direct Editor and putting your EXE file in the 'Binary' table
- You can create a custom action to launch that EXE file from the 'Custom Actions' Node in the tree on the left
- You can insert the custom action by selecting 'Install Sequences' and putting it in the
InstallExecuteSequence
somewhere betweenInstallInitialize
andInstallFinalize
as I said before.
Sorry, I could not be more detailed, but this should be a good start.
Elliott21511 gold badge33 silver badges1313 bronze badges
Mike MarshallMike Marshall7,00133 gold badges3131 silver badges5959 bronze badges
I think the easiest way to create a .MSI file is to use WiX.
Lesson 1 from the WiX tutorial is all you need to create a simple install.
Peter Mortensen14.5k1919 gold badges8989 silver badges118118 bronze badges
GvSGvS45.7k1515 gold badges8989 silver badges130130 bronze badges
Joshua, I understand your frustration very well. MSI is quirky to say the least - a completely new way to think of deployment. Still, applied correctly MSI offers the best possible deployment, especially for corporate customers.
What operations does your installer EXE perform? Is it largely file copy, some COM registration and some registry writes, or does it run complex installation logic, setting up databases etc..? The reason I ask is because it probably would be very quick to create a well functioning WIX MSI for you so you can abandon the EXE approach.
It is indeed possible to run an EXE from inside an MSI, but it requires proper sequencing, and it is guaranteed to cause you more blues than a simple MSI. If the app is small, and not doing anything crazy during installation, I would be happy to provide you with a basic WIX conversion.
Community♦
Stein ÅsmulStein Åsmul25.6k1515 gold badges6161 silver badges129129 bronze badges
No solution. We went NSIS as corporate MSI install is going to be broken anyway due to MSI nesting problem (just try installing EXE wrapping MSI from inside MSI someday).
JoshuaJoshua27.1k55 gold badges5151 silver badges108108 bronze badges
There is also a free version of the MSI Wrapper. It also supports uninstall and upgrades. Also, it only creates one entry in the Add or Remove programs.
J. RasmussenJ. Rasmussen
Adding to
weir's
answer, change the custom action attribute
like below:Msi Wrapper Download
Setting
Return=asyncNoWai
does not wait for the exe
to return. The installer does it's job and closes normally. Meanwhile, the exe
continous its execution.Usb to ethernet driver windows 10. This driver offers Network Interface Controller with Windows 10 support for Realtek 10/100/1000M Gigabit Ethernet and 10/100M Fast Ethernet chips.
-Madhuresh
now he who must not be named.now he who must not be named.4,9911616 gold badges5858 silver badges105105 bronze badges
If you don't want to manage MSI, but only execute EXE, try Exe to MSI Converter Free. You just put in the path to the EXE and get an MSI.
Andrew Lee1,77022 gold badges1515 silver badges2626 bronze badges
pawelekpawelek
try this:
Uloz.to is the largest czech cloud storage. Upload, share, search and download for free. Credit allows you to download with unlimited speed. Warhammer 40k tau codex 8th edition pdf download.
In MSI package, there is a behaviour call 'Launch an application after installation', that means your exe file will be executed after the MSI installation(the MSI is closed).
Try to execute your exe there, so when your exe invoke other MSI packages, it won't conflict with the first one.
James YangJames Yang
Wix can do it. Here is my sample code for wix 3.5:
Stein Åsmul25.6k1515 gold badges6161 silver badges129129 bronze badges
weirweir
I was having the same problem (wrap EXE, call other MSI from the EXE including .net setup, etc.), and here is my solution:
I build the setup exe using InstallAware.It has its own MSI Wrapper that wraps the generated EXE with MSI.
Msi Wrapper Install Arguments
It works OK, the EXE can call other MSIs without any problem (including .net setup, other 3rd party setups), but that is because the launching MSI ends ('returns') rights after it launches the setup EXE file, and that way they avoid the MSI limitation of recursive MSI calls.
BUT - some customers (companies) that uses MSI deployment tools, requires the MSI (msiexec) to return (end) only after the setup process ends, and that is a problem with the above solution.
So - to solve this:
There is another MSI Wrapper (exemsi.com) that generates MSI that returns only after the EXE setup ends, but for using that you must use another unique option of InstallAware:
InstallAware has the option to generate the EXE setup using their own native engine, and not based on Windows Installer engine, to avoid MSI recursive limitation.Combine those both, and you have the perfect solution.
Hope this will help someone, although many years passed since this question was first posted.
OrenOren
user2684935user2684935
Nah man, just use Inno Setup's wizard. It makes an setup EXE but not an MSI. It's like 5 mins and you'll have a windows installer.
Simply download it, install it, point it to your EXE, and follow the on-screen prompts
JonathanJonathan3,20922 gold badges3030 silver badges4747 bronze badges