Msiexec exe has generated errors

The first step should be creating an installation log to see what triggers the error. From the log you posted, it seems like your MSI tries to use a directory which is not in Directory table. Are you using any merge modules or special custom actions? If so, try to determine if they try to use a directory from your package.

Old question, I know - just wanted to add in some information that helped me with the Windows Installer project in Visual Studio , in case anyone comes across this topic.

I got the same error message, My issue was that I was including my source code into an "src" folder in the installation directory. When looking at the output files for the source, I noticed several files like this:. Yes, it included that extra slash after Release. Maybe someone else can explain why these temporary files were generated, all I know is that this fixed the issue. Hopefully this will help someone else looking for this topic. I know its a Old question, but like Riccaforte I was having some trouble to fix this in Visual Studio What I did was just delete all my Source Files inside my Aplication Folder, and I don't know why, but it did the trick.

If you remove a directory or directories from the Directory Table, This will cause an issue with other tables still using those directory variables. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Visual Studio Windows Installer using msiexec.

Asked 10 years, 5 months ago. Active 5 years, 1 month ago. Viewed 15k times. The Installer does not run. The Text is for search functions : The installer has encountered an unexpected error installing this package. Could someone guide me towards fixing this? Maybe there are some tips and tricks on the AppDB.

And the installation complete successfully. Now knowing the POL method work, but now I wish to know why the non POL wizard method not working, and I wish to understand what I had missed out or what has went wrong. You do not have the required permissions to view the files attached to this post. Could you try the following? Currently still running on Ubuntu Following is the result; Verifying Microsfot fonts Code: Select all sudo apt install ttf-mscorefonts-installer Reading package lists Done Building dependency tree Reading state information Done ttf-mscorefonts-installer is already the newest version 3.

You opted in, so reporting 'msls31 riched20 msxml6 ' to the winetricks maintainer so he knows which winetricks verbs get used and which don't. Use --optout to disable future reports. Download Advanced Installer now.

The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface.

Sometimes an installation overwrites files which are in use or needs to reboot the machine in order to finish it. The reboot policy used by the installation can be set through these options:. When debugging an installation package you can use multiple logging parameters in order to create a log. This log will contain different information for each parameter you use:.