Sometimes msi.dll and other system errors DLL errors may be related to problems in the Windows registry. Several programs may use the msi.dll file, but when these programs are removed or changed, "orphaned" (erroneous) entries are sometimes left registry DLL.
Basically, this means that while the actual path to the file may have been changed, its incorrect former location is still recorded in the Windows registry. When Windows tries to look up this incorrect file reference (file location on your computer), msi.dll errors can occur. In addition, malware infection may have corrupted registry entries associated with Windows 10. operating system. Thus, these corrupted DLL registry entries need to be repaired in order to fix the root of the problem.
Manually editing the Windows registry to remove invalid msi.dll keys is not recommended unless you are PC service professional. Mistakes made while editing the registry can render your PC unusable and cause irreparable damage to your operating system. In fact, even a single comma in the wrong place can prevent your computer from booting up!
Because of this risk, we highly recommend using a trusted registry cleaner such as WinThruster (Developed by Microsoft Gold Certified Partner) to scan and repair any msi.dll-related registry problems. Using a registry cleaner, you can automate the search process damaged records registry, links to missing files (for example, causing an error msi.dll) and broken links inside the registry. Before each scan, an automatically created backup copy, which allows you to undo any changes with one click and protects you from possible damage computer. The best part is that fixing registry errors can drastically improve system speed and performance.
Warning: If you are not experienced user PC, we do NOT recommend editing the Windows registry manually. Incorrect use of the Registry Editor can lead to serious problems and require reinstalling windows. We do not guarantee that problems resulting from misuse of Registry Editor can be resolved. You use the Registry Editor at your own risk.
Before manually restoring Windows registry, you need to create a backup by exporting a part of the registry related to msi.dll (eg. Windows 10 Operating System):
- Click on the button To begin.
- Enter " command" in search bar... DO NOT PRESS YET ENTER!
- Holding keys CTRL-Shift on the keyboard, press ENTER.
- An access dialog will be displayed.
- Click Yes.
- The black box opens with a blinking cursor.
- Enter " regedit" and press ENTER.
- In the Registry Editor, select the msi.dll-related key (eg. Windows 10 Operating System) you want to back up.
- On the menu File select Export.
- Listed Save to select the folder where you want to save the backup Windows key 10 Operating System.
- In field File name enter a name for the backup file, such as "Windows 10 Operating System Backup".
- Make sure the field Export Range value selected Selected branch.
- Click Save.
- The file will be saved with .reg extension.
- You now have a backup of your msi.dll-related registry entry.
Next steps for manual editing registry will not be described in this article, as they are likely to damage your system. If you want to receive more information about editing the registry manually, please see the links below.
What are these files that have the msi extension?
This is the installation package file that installs the software and uses the Windows Installer service. Its name is an extension msi taken from "Microsoft Installer » , as the Windows Installer version used to be called. This file contains the complete installation script. software product, auxiliary components, libraries and, in most cases, all installation files compressed into cab archives. You can discuss all the advantages and disadvantages of work for a long time Windows Installer, but we will still have to accept it "as is", and we will competently and adequately respond to some malfunctions in the work. Errors can occur both in the operation of the service and due to the msi files.
This is what sometimes happens: and then the system prompts me to make sure that there really was an installer file that I ran. At first it sounds at least strange. But, reading further the message of the system, I understand that I am offered to make sure not only the existence of the file itself, but also my rights to access it. As it turned out, it's not me, but Windows Installer was deprived of access to the file, hence the problem.
This issue is not resolved at all. in a complicated way. Let's first make sure the system has access to the file full access, for which in the "Properties" of the file we go to the "Security" tab and find the user "System (System)".
I’m more than sure that you won’t find it there, so add it yourself - click on “Change”, then on “Add” and enter the name: “System” (or System, in the case English version systems),
then click on "Check Names" (the line becomes underlined).
We confirm - OK and put a mark in the checkbox "Full access", again we confirm.
Click on "Advanced", then - "Change permissions" - "Add permissions »,
inherited from parent objects and confirm everything three times.
Thus, we got rid of this installer error, and it will not bother us anymore during the installation process. Although it would be more reasonable and prudent to add full system access rights to the entire folder with the contents, from which the installation usually takes place software(as in my case the "Install" folder).
If your computer has an operating Windows system XP, and in the "Folder Options" enabled "simple general access to files", you will not see the "Security" tab in the file's properties. In this case, you should go to "Folder Options" and uncheck the "Use simple file sharing" checkbox. Also, you run the risk of not finding this tab in different “assemblies” and “light versions” of both Windows XP and Windows 7. To still go to this tab, you will have to boot into safe mode (safe mode) and enter under account administrator.
Another problem with the Windows Installer can be avoided by running the installation of applications with the antivirus program disabled, with administrator rights, and also in compatibility mode (the "Compatibility" tab in the properties of the msi file, check the corresponding checkbox).
Also, there may be problems when trying to install the program from removable media, a flash drive, for example (a ban on such actions can be done in the settings operating system) - just copy the installation file to a convenient location on your hard drive. Another solution to the problem is to create new folder under any name you like and copy into it installation package, from there and run the installation - it can be useful for errors number 1603, 214 728 7035, 2203 and 1723.
Be sure to ensure that the system has access to directories temporary files. Open "System Properties" (Win + Pause or in the context menu by right-clicking on the My Computer icon, select the Properties line), in " Additional options systems",
On the Advanced tab, click the Environment Variables button.
We find folders of temporary variables (they have the words TEMP, TMP in their names), check if the system has access to them (according to the algorithm already described above). I hope you remember, to find out the address of such a folder, you need to double-click on the variable
and, copying the specified path, paste the contents of the clipboard into the explorer line and navigate to the folder. And at the same time, you can do a useful thing - clear all temporary folders from their contents.
will also right decision check for access rights those directories into which you plan to install applications and a directory with the name config.
Msi fundamentally system partition. Encryption must be disabled for all the directories indicated above, since the Windows Installer in this case does not have access to them, unlike the user.
Well, of course, an installation error can occur due to a broken installation file (the so-called “broken” file, with a mismatch checksums), in such a situation it is necessary to get hold of obviously "working" normal setup file. Most likely, it will make sense to download it from another source or from another mirror.
Cause of Windows Installer Error
Now it is worth considering the situation when the installation of the application is impossible due to errors in the Windows Installer itself. If the installation process does not start, no matter what application you try to install, then most likely the problem is in the installer service itself. May appear system messages about errors that contain relevant phrases, such as: Installer package or Windows error Installer Error. This may be due to errors in system registry, and virus attack. Let's start by checking the status of the Windows Installer service and its startup type. To this end, in the Run line (Win + R) we enter the command services. msc, and in the console that opens, we find the desired item - “Windows Installer (Windows Installer)”.
We look to see if it works and what type of startup it has (should be set to Manual) If the service is not running and has a different startup type, then launch it (click "Start", you can - "Restart") it, and change the startup type in the properties to "Manual". If the service starts, check the situation and enter the command in the "Run" line msiexec- if everything is OK, then instead of an error you will see a window with the launch options of the Windows Installer and its version number.
I see a further elimination of the problem in fixing the damaged system files operating system. To implement this, in the "Run" line, execute the command sfc/ scan now(prepare in advance the disk from which your operating system was installed, it may be required in this process) and then restart the computer. The problem is supposed to disappear.
Also this problem rises on the Microsoft website with a solution. Follow this link and run the "native" FixIt utility. Follow the instructions in the accompaniment, this should help in fixing the problem.
Another option to eliminate this scourge may be to try to restore the registry settings for the Windows Installer, in which everything works fine. Run the registry editor file from the archive here and confirm the import of new settings (do not forget before changing the settings in the registry
Errors when installing applications from files with the .msi extension are one of the manifestations of problems in the operation of 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, face a similar phenomenon. So far, the problem with the installer is one of common causes, according to which users decide to reinstall the system. Let's try to figure out how to avoid this. The reason why the Windows Installer is not working may be the following:
- virus infection, and removing the virus does not always solve the problem;
- incorrect installation Windows updates;
- Anti-malware crashes when instead of blocking one suspicious msi file, the installation service is blocked entirely;
- changes in security policies on the computer;
- damage to system files or the registry for reasons not related to viruses (removal of installer components, unqualified editing of the registry, "crooked" software, malfunction hard drive etc.).
Checking the integrity of the Windows Installer structure
The Windows Installer is represented by the following components:- file C:\Windows\System32\Msiexec.exe - directly by the installer itself;
- file C:\Windows\System32\msi.dll - Windows library installer;
- by the Msiserver service, whose settings are stored in the registry key .
If the files are missing, copy them from another system of the same version or from the installation disk. If the registry key is missing or damaged, also transfer it from working system. To do this, on a working computer, run the registry editor (C:\Windows\Regedt.exe) and find the above section. 
Right-click to expand the context menu of the msiserver folder and click "Export". Save the file in .reg format and transfer it to the problem machine. 
Double-click this file and confirm your consent to add data to the registry. Restart your computer. 
If the Msiserver service still does not start, check if the RPC (Remote Procedure Call) service on which it depends is running. 
You can re-register the installer files and restart the service using the set special teams, on the command line. For convenience, you can create batch file: Paste the action set into Notepad and save as with .bat extension. To run a file, simply double-click on it. For the changes to take effect, click on the desktop and press F5. Checking security settings and permissions
Windows Installer may not work due to the fact that it is blocked by security software or the operating system does not have the necessary rights. First, let's deal with the software. If you have an antivirus installed, disable it temporarily. Each product has its own ways to disable it, but most often it is done through the context menu of the antivirus icon in the system tray. Now let's take a look at 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, there 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 first appeared in Windows Vista, so in Windows XP, full control must be granted to the system. Everything written below refers to versions released after 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. If it doesn't appear in the "Change Owner To" list, click the "Change" button, followed by "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 must 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.
When installing any program with the .msi extension, it writes about a problem with the Windiws Installer service, and when this service starts, it writes: Failed to start the service on local computer... Error 2: Unable to find specified file. Or in the list this service missing.
Follow these guidelines to restore the Windows Installer service.
How to repair Windows Installer
Check your computer for viruses
The first thing to do is to make sure that the computer is not infected with viruses. To do this, we recommend checking the computer antivirus program installed in the system. And also download the cure utility from dr.web (dr.web cureit!®) and run the scan again with this utility.
Check the startup type of the Windows Installer service
To do this, open Control Panel - Administrative Tools - Services. Find the Windows Installer service in the central part. Right click on it and select context menu Properties. See what startup type is set. Change it to automatic, restart your computer and check if the problem repeats or not.
If the service is not in the list, or the problem persists, read below.
Does the windows installer itself start
If the problem recurs or the startup type was already set to automatic, then check if it starts itself windows program installer. To do this, click Start - Run - Type msiexec and press enter. This should open a window in which it will be written windows version installer and available commands.
The files required for the Windows Installer may be corrupted
To check system files for integrity, open command line as administrator (click Start - All Programs - Accessories - Right click click on Command Prompt - Run as administrator) and at the command prompt run the command
Sfc /scannow
Restart your computer and check if the error persists or not.
If this does not help, open a command prompt as an administrator and enter the following commands in sequence, pressing enter after each of them:
Msiexec /unreg msiexec /regserver net stop msiserver regsvr32 /u /s %windir%\System32\msi.dll regsvr32 /u /s %windir%\System32\msihnd.dll regsvr32 /u /s %windir%\System32\msisip. dll regsvr32 /s %windir%\System32\msi.dll regsvr32 /s %windir%\System32\msihnd.dll regsvr32 /s %windir%\System32\msisip.dll net start msiserver
Restart your computer and check Windows work installer.
If the problem persists, then compare the contents of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver registry branch with the same branch on another computer and, if necessary, correct the values on the problem computer.
