The most common problem that users cannot open this file is an incorrectly assigned program. To fix this in Windows, you need to right-click on the file, in the context menu, point the mouse to the "Open with" item, and select the "Select program ..." item in the drop-down menu. As a result, you will see a list of installed programs on your computer, and you can choose the appropriate one. We also recommend checking the box next to "Use this application for all MSI files".
Another problem that our users also encounter quite often is that the MSI file is corrupted. This situation can arise in many cases. For example: the file was downloaded incompletely as a result of a server error, the file was damaged initially, etc. To fix this problem, use one of the recommendations:
- Try to find the desired file in another source on the Internet. You may be lucky enough to find a more suitable version. An example of a Google search: "File filetype: MSI". Just replace the word "file" with the name you want;
- Ask to send you the original file again, it may have been damaged in transit;
If there is a computer installed antivirus software can scan all files on the computer, as well as each file separately... You can scan any file by right-clicking on the file and selecting the appropriate option to scan the file for viruses.
For example, in this figure, my-file.msi file, then you need to right-click on this file, and select the option from the file menu "Scan with AVG"... Selecting this option will open AVG Antivirus, which will scan this file for viruses.
Sometimes an error can result from incorrect software installation, which may be due to a problem encountered during the installation process. It may interfere with your operating system associate your MSI file with the correct application softwareinfluencing the so-called "File extension associations".
Sometimes simple reinstalling 7-Zip might solve your problem by linking MSI with 7-Zip correctly. In other cases, problems with file associations can result from bad software programming developer, and you may need to contact the developer for further assistance.
Advice: Try updating 7-Zip to the latest version to make sure the latest patches and updates are installed.
It may seem too obvious, but often the MSI file itself may be causing the problem... If you received a file via an email attachment or downloaded it from a website and the download process was interrupted (for example, a power outage or other reason), the file may be damaged... If possible, try to get a fresh copy of the MSI file and try opening it again.
Caution: A damaged file can cause collateral damage to previous or pre-existing malware on your PC, so it is very important that you have an updated antivirus running on your PC at all times.
If your MSI file related to the hardware on your computerto open the file you may need update device driversrelated to this equipment.
This problem usually associated with types of media filesthat depend on the successful opening of hardware inside the computer, for example sound card or video card... For example, if you are trying to open an audio file but cannot open it, you may need to update sound card drivers.
Advice: If when you try to open the MSI file you get sYS file related error message, the problem could probably be related to corrupted or outdated device driversthat need to be updated. This process can be facilitated by using driver update software such as DriverDoc.
If the steps did not solve the problemand you are still having problems opening MSI files, it could be due to lack of available system resources... Some versions of MSI files may require a significant amount of resources (e.g. memory / RAM, processing power) to open properly on your computer. This problem occurs quite often if you are using fairly old computer hardware and at the same time a much newer operating system.
This issue can occur when the computer has a hard time completing a job, as the operating system (and other services running in the background) can consume too many resources to open the MSI file... Try closing all applications on your PC before opening the Windows Installer Package. By freeing up all the available resources on your computer, you will provide a better environment for trying to open the MSI file.
If you completed all the steps aboveand your MSI file still won't open, you might need to run equipment upgrade... In most cases, even with older hardware versions, the processing power may still be more than adequate for most custom applications (unless you're doing a lot of CPU-intensive work like 3D rendering, financial / scientific modeling, or heavy multimedia work) ... Thus, it is likely that your computer does not have enough memory(more commonly called "RAM", or random access memory) to perform the task of opening a file.
Good day, Habr! I want to present an interesting, in my opinion, way of creating msi-installers for any software and, as a result, deploying it using GPO tools. I would like to emphasize that the described method does not imply the creation of "snapshots" of the system, but uses native software installers, and only free for commercial use products are used to create msi.
Introduction, couple of links and disclaimer
Every normal software installer has the ability to automatically install with certain or default parameters. The essence of my method is simple and consists in packing the native installer into an msi "container" and launching it with the necessary command line parameters. There is a lot of information on the net on the automatic installation of this or that application, and I will not dwell on this. Again, our goal is to install software using group policies. By the way, some of you may argue that the installation can be done through ZAW, but, unfortunately, this method is applicable only for installation with the rights of the current user and cannot be used for centralized automatic installation of applications.An interesting series of articles on installing software via GP. For beginners, I recommend that you read everything, so as not to ask later what is the difference between the type of installation "assigned" from "public".
Necessary software. Exe to MSI Converter freeware and the well-known orca The first one is needed in order to create msi from exe, and the second - so that the resulting msi-nickname can be installed through group policies.
The method does not claim to be completely unique and in some places there may be excesses that could have been avoided, but this is due to the lack of desire and need to delve too deeply into the parameters of the msi package tables. The initial goal was to quickly find a free way to create msi, and after several hours spent reading foreign forums and endless reboots of the virtual machine, the method was found. Also, the article is not an overview of the program interface, and you will not see screenshots.
Package creation and preparation
An example installation will be made for Mozilla Firefox, since this is a well-known product that does not have an msi installer from the developers.- Run exe to msi and specify the path to the firefox exe-installer in it. According to the information previously found on the network, it becomes clear that it is possible to quietly install firelis with parameters -ms -ira... We indicate them in the second field exe to msi and click "Build MSI".
- It would seem that the msi package is ready. Indeed, by running the resulting result, we will get the firefox installed in the system and we could put a full stop in the article. Unfortunately, not everything is so simple. The current installation package is not suitable for deployment via GPO, and when you boot your computer, you will receive absolutely nothing explaining errors in the logs "an unrecoverable error has occurred ..." msi "not by the rules".
- Well, let's take an orc and open our MC in it.
- First of all, we find the table in the left list Property and pay attention to two fields - ProductCode and UpgradeCode... These two fields must be unique for each product, and our exe to msi always generates the same. Well, it doesn't matter, click on the top menu View -\u003e Summary Information, we find the field PackageCode and click New GUID... Copy the resulting result to the clipboard and paste it into ProductCode... Repeat for UpgradeCode and finally for himself PackageCode... Right there in Summary Information rule the field Title on Mozilla Firefox, the rest is optional. This, in fact, does not affect anything.
- Again in the table Property me ProductName on Mozilla Firefox (I change the ARPCONTACT and Manufacturer). You can also set the correct value for ProductVersion.
- It seems that the GUID and other "IDs" have changed, but as practice shows, this is not enough. Click on orca Tools -\u003e Validate, take off the bird Show INFO Messages and press Go.
- As you can see, a bunch of errors have appeared for the presence / absence of some tables and values. I didn't bother and just took the first small msi that came across (7zip x64 9.20) and copied 4 missing tables from there (via Export-Import, of course): _Validation, AdminExecuteSequence, AdminUISequence and AdvtExecuteSequence... In fact, I'm sure that you can create a "correct" msi installer, without unnecessary garbage, but do not forget, our goal is just to run the native setup of the application in quiet.
- After adding tables, go through again Tools -\u003e Validate (by the way, the first time you don't need to check at all and just import tables). If you also took the msi from 7zip as a basis, then the result will be six errors that need to be eliminated. Click Close, remove unnecessary fields marked in red.
- At the end, you can check the validation again and make sure that only non-interfering warnings remain. Save msi.
- That's basically all, it remains to add msi to the GPU and assign the necessary properties.
Nuances
- When installing using the method described above, you will have two copies of the software. The first is the actual application you need, and the second is the original msi-nickname, because we kind of installed it. In principle, this does not affect anything, except for the display in the "Add or Remove Programs", and then only in Windows XP (if you have not changed anything except what I have specified). The downside may be the appearance of unnecessary programs during automatic software inventory, if you use it.
- You cannot automatically uninstall the application using the same deployment tools. More precisely, it will work, but only the already unnecessary msi container will be removed. Well, you can tinker with the properties of msi when you create it, so that it grabs the previously installed application with it, just as quietly. I did not set such a task.
- When installing software updates, the application must be specified in the properties of the GPU so that it replaces the previous one, that is, it must first delete the old one. This ensures that you will not have those same left-hand duplicate applications in the "installation and removal of programs" that did not give up to anyone.
- To install an application that has a distribution of several files, you will have to first package it into an exe, which, when launched, will unpack itself and give a command for a silent installation. I recommend creating sfx archives using the same 7-zip.
- Nothing prevents you from installing software through startup scripts. Moreover, this method is more flexible, and I have been using it for a long time through my scripts. However, using the native GPU tools is much faster, since a simple creation of an msi from an exe takes a couple of minutes.
- Windows 7 for some reason does not write "Installing a managed application ...", but simply says "please wait". When you first deploy the entire heap of software at once or when installing a heavy application, this may prompt the user to call the admin or press the reset button.
Introduction
Our installers for Windows contain a complete client-side installation (MSI) package (built on top of Windows Installer v2.0). The network installation instructions assume that the user is familiar with the basics of Windows Installer, specifically deploying MSI files. This package can be used with any Windows operating system that supports Windows Installer v2.0.
Installation on a network server
- Double click on the resulting file ( Yenka_Setup_ (MSI) .exe)
- Install this package to the shared folder for your programs.
- Attention : The program must be activated BEFORE deploying the package on the network. To do this, run "Yenka.exe" from the folder where you installed the program (<путь установки>\\ program files \\ Yenka \\ Software \\ Yenka.exe), and follow the activation instructions.
Installation
Installing an MSI package using the command line
- In the command box, enter the line:
msiexec / i "<путь к MSI файлу> \\ YK.msi "
Where:<путь к MSI файлу> this is the path to the Windows Installer package file. For example, a line might look like this: msiexec / i "C: \\ Program Files \\ Yenka \\ YK.msi" - Press the ENTER key
Attention: The Windows Installer service will allow you to install in "invisible" mode, using the "/ q" switch. For example: msiexec / i "C: \\ Program Files \\ Yenka \\ YK.msi" / q... To show the progress bar of the installation, you can use the " / qb".
Uninstalling an MSI Package Using the Command Line
- From the "Start" menu, select "Run ..."
- In the command box, enter the line:
msiexec / x "<путь к MSI файлу>\\ YK.msi "
Where:<путь к MSI файлу> this is the path to the Windows Installer package file - Press the ENTER key
The windows installer error is one of the most common pop-up issues encountered by users of the Windows operating system.
The error can appear regardless of your OS version.
Reasons for the error
You can scan the OS using the Sfc / scannow command. You need to enter it in the command line window.
You can also run the command line in two other ways:
- Start -\u003e All Programs -\u003e Accessories -\u003e Command Prompt.
- Start -\u003e Run and enter the program name cmd.exe
In a few minutes, you will be provided with detailed information about the OS disks, corrupted files, problems with services and other system programs.
The command line will not only find damaged and damaged files, but also replace them with workable ones.
After scanning, close Command Prompt and restart your personal computer or laptop. Try running the installation process of any executable file.
Also, Microsoft offers users an automatic utility that can solve the problem of the installer.
Go to the official website of the company https://support.microsoft.com/en-us/mats/program_install_and_uninstall
In the window that opens, click on the "Run now" button. The utility will restore the correct installer configuration.
It should be noted that the utility does not work with the eighth version of the operating system.
Configuring installer access to msi files
An installation problem may be caused by the installer not having access to the .msi files. The user can solve this problem on his own.
Follow the instructions below:
- Find your installation file and right-click on it;
- Select the properties window;
- Go to the security settings tab;
- In the group or user text box, check if there is a user named "system". If it is not there, you need to add the user manually;
- To add a new user, click the Edit button and then the Add button;
- In the text box for the name of the object to select, write the word "system" (without the quotes). If you are using an English version of the operating system, enter the word System;
- The entered word should instantly become underlined, as shown in the figure below;
- Check the box next to full access and now click on the OK button;
The installer will now be able to access the executable. The installation should complete without problems.
Note that in some cases antivirus software can block access to the installation file.
To solve this variant of the problem, you need to log into the operating system under an administrator account, turn off the antivirus and enable compatibility with other OS versions in the antivirus properties settings, as shown in the figure below.
Windows Installer Error - Solutions
