Introduction
Our installers for Windows contain a complete client side installation package (MSI) (built on the basis of Windows Installer v2.0). The network installation instructions assume that the user is familiar with the basics of Windows Installer, particularly how to deploy 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 into your programs' shared folder.
- 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 field, enter the line:
msiexec /i"<путь к MSI файлу>\YK.msi"
Where:<путь к MSI файлу>this is the path to the Windows Installer package file. For example, the line might look like this: msiexec /i"C:\Program Files\Yenka\YK.msi" - Press ENTER
Attention: The Windows Installer service allows installation in “stealth” mode, using the “/q” switch. For example: msiexec /i"C:\Program Files\Yenka\YK.msi" /q. To show the installation progress indicator, you can use the key " /qb".
Uninstalling an MSI package using the command line
- From the Start menu, select "Run..."
- In the command field, enter the line:
msiexec /x"<путь к MSI файлу>\YK.msi"
Where:<путь к MSI файлу>this is the path to the Windows Installer package file - Press ENTER
Some programs and drivers in Windows should only be installed with administrator rights. In the case of EXE files, the option to install as administrator is present in the context menu, which is called up by right-clicking on the file. There is no such option for MSI packages, but you can add it through the registry editor.
Instructions
Open the Run dialog via the start menu or by pressing the Win+R key combination. In the window that opens, write regedit and press Enter. The Registry Editor will launch. Depending on your User Account Control settings, you may be asked to confirm that you want to launch the editor.
Go to the HKEY_CLASSES_ROOT\Msi.Package\shell branch. Right-click on “shell” and in the menu that opens, select the option to create a new partition.
A subsection will be added to the “shell” section. Rename it "runas" (no quotes needed).
In the window on the right, double-click on the “Default” key or once with the right mouse button and select “Change...” In the empty value field, enter “Run as Administrator”. Confirm the changes by pressing the OK button.
Now right-click on “runas” and select the create partition option again. Create a subkey named "command" (without the quotes).
Edit the "Default" key by entering the command "msiexec /i "%1"" in the value field (without the herringbone quotes, but with quotes for %1). Click OK.
If programs from .msi files do not start, this is a direct indication of a problem with the Windows Installer service. Any Windows 7 OS user may encounter a similar phenomenon. Therefore, if Windows Installer does not work for you, it is worth familiarizing yourself with some recommendations.
Reasons for Windows Installer failures
The reasons why Windows Installer does not work may be due to the following factors:
- Virus infection of system files. However, cleaning the OS does not always solve the problem.
- Incorrect installation of updates.
- Incorrect editing of the registry, removal of installer components.
- Blocking the .msi file by the antivirus
- Changing the PC security policy.
All of these factors can affect the operation of the Windows Installer service.
Checking the integrity and functionality of files
Windows Installer consists of the following components:
- The file msiexec.exe, which is located on the “C” drive in the “Windows” and “System32” folder.
- The file is msi.dll, which is nothing more than an installer library.
- The Msiserver service, whose parameters are located in the registry editor section at the addresses "HKEY_LOCAL_MACHINE", "SYSTEM", "CurrentControlSet", "services" and "msiserver".
First, go to the registry editor and look at the value of the msiserver service. Click “Win + R” and enter “regedit”.
We make sure there are no unnecessary values. The correct list is shown in the photo.
If there is no partition or some files are missing, you can copy the elements on the working system and right-click and select “Export”.
Select a location to save the files and enter a name similar to the original. Click “Save”.
Move the copied section or files to your PC.
Find “Windows Installer” and check if the service is running.
If necessary, double-click the file and click “Run”.
Checking access rights
Launch the registry editor, go to the address “HKEY_LOCAL_MACHINE”, “Software”, “Microsoft”, “Windows”, “CurrentVersion”, “Installer”. Right-click on the section name and select “Resolution...”.
In the “Groups and Users” section, click “System”. Next, we make sure that the user has full access to the service.
Errors when installing applications from files with the .msi extension are one of the manifestations of problems with the Windows Installer service (in the Russian version, the Windows Installer). Users of all versions of this OS, with the exception of the earliest ones, encounter a similar phenomenon. Until now, the problem with the installer is one of the common reasons why users decide to reinstall the system. Let's try to figure out how to avoid this. The reason that Windows Installer does not work may be the following:
- viral infection, and removing the virus does not always solve the problem;
- incorrect installation of Windows updates;
- a malfunction of the security software when, instead of blocking one suspicious msi file, the installation service is blocked entirely;
- changes in computer security policies;
- Damage to system files or the registry for reasons not related to viruses (removal of installer components, unqualified editing of the registry, crooked software, hard drive failure, etc.).
Checking the integrity of the Windows Installer structure
The Windows Installer consists of the following components:- file C:\Windows\System32\Msiexec.exe - directly by the installer application itself;
- file C:\Windows\System32\msi.dll - Windows Installer library;
- Msiserver service, whose settings are stored in the registry key.
Checking security settings and access rights
Windows Installer may not work because it is blocked by security software or the operating system does not have the necessary rights. First, let's look at the software. If you have an antivirus installed, temporarily disable it. Each product has its own methods of disabling, but most often this is done through the context menu of the antivirus icon in the system tray. Now let's take care of the rights. Open the context menu of Msiexec.exe and expand its properties. View the list of groups and users on the Security tab. Among them must be “System” and the “Trustedinstaller” service, and the latter must have full access to the file and be its owner. The system must have "read" and "read and execute" permissions. The Trustedinstaller service was first introduced in Windows Vista, so in Windows XP full access must be granted to the system. Everything written below applies to versions released later than XP. To check who owns Msiexec.exe, click the "Advanced" button on the same tab. In the next window, expand the "Owner" tab. Set the owner to the Trustedinstaller service if something else is specified as the owner. If it is not in the "Change owner to" list, click the "Change" button, and then click "Other users and groups." Enter Trustedinstaller in the "Enter names..." field, click "Check names" and OK. Return to the previous window. On the "Effective Permissions" tab, assign the necessary rights to Trustedinstaller and the system. The msi.dll library should have exactly the same security settings. Now let's check if there are any restrictions for the "System" user to access the following:- system drive (usually drive C);
- temporary folders (these are C:\Windows\Temp and C:\Users\Current_User\AppData\Temp);
- folder C:\Config.Msi;
- the folder where the msi file from which you are trying to install the program is located.
These instructions should help if you see one of the following error messages when installing a program on Windows 7, Windows 10 or 8.1:
- Windows 7 Installer service is not available
- The Windows Installer service could not be accessed. This can happen if the Windows Installer is installed incorrectly
- Failed to access Windows Installer service
- Windows Installer may not be installed
Another way to fix the Windows Installer service not available error is to re-register the Windows Installer service on the system.
To do this, run the command line as an administrator (in Windows 8, press Win + X and select the appropriate item, in Windows 7 - find the command line in standard programs, right-click on it, select “Run as Administrator”).
If you have a 32-bit version of Windows, then enter the following commands in order:
Msiexec /unregister msiexec /register
This will re-register the installer service on the system, after running the commands, reboot your computer.
If you have a 64-bit version of Windows, then run the following commands in order:
%windir%\system32\msiexec.exe /unregister %windir%\system32\msiexec.exe /regserver %windir%\syswow64\msiexec.exe /unregister %windir%\syswow64\msiexec.exe /regserver
And also restart your computer. The error should disappear. If the problem persists, try starting the service manually: open a command prompt as an administrator, and then enter the command net start MSIServer and press Enter.
3. Reset Windows Installer service settings in the registry
As a rule, the second method is sufficient to fix the Windows Installer error in question. However, if the problem still cannot be solved, I recommend that you familiarize yourself with the method of resetting service parameters in the registry, described on the Microsoft website: http://support.microsoft.com/kb/2642495/ru
Please note that the registry method may not be suitable for Windows 8 (I cannot give exact information on this matter.