Failed to access the Windows Installer Installer service - how to fix. Errors when installing programs from the Windows Installer package ".msi cannot remove the MSI installer

Letter from the reader:

Not deleted program from a computer Through the menu, installing and deleting programs and in general in any ways, deleted all folders related to the program, used all kinds of utilities cleaning registry from unnecessary keys, useless. The fact is that I want to establish it again, it is licensed and purchased for money, but recently worked with errors. The installer says: the application is already installed and on it all ends. The forum suggested that you need to look in the bushes (in the registry). This is a joke? Help.
Edward

Letter from another reader:

Not deleted game from a computer Call of Duty 4: Modern Warfare, I want to reinstall it, but it turns out a mistake, deleted just a folder with the game, and I could not delete the installation and delete program menu, maybe you know how to delete and reinstall, please tell me.
Basil

Not deleted program from a computer

And of course a program or a game cannot be established again, because the Unlocker utilities, CCleaner, Revo Uninstaller and the like can be useless. On one site I read as using one of these programs, you can remove the anti-virus program, I laughed for a long time, in fact everything will be wrong, sometimes the principles of operation of these programs are ineffective. Let's think that we will do if all the aforementioned programs did not help us.

Information in our article is applicable to Windows 7 and Windows 8. 1.

Note: Friends if this article does not help you, try

Many in case of failure with remove the program from a computer Even reinstall the operating system if it comes to their favorite game. Believe me, in most cases it is not necessary. By the way, it is also in the accumulation of garbage in Windows, because the remnants of the program are somewhere and of course occupy a place on a hard disk, all this is rather not pleasant and of course I want to know where the remaining program files are located. This is such a trouble due to the violated, for some reason the connection between the program and its keys in the registry. The reasons for these many, starting from the wrong actions of the user and the errors of the program itself, will not stop at this. To solve such problems, we will need to manually make changes to the registry and our program will be completely removed. How to do it?

The program you want to delete is no longer used? If the process is known to you, it also needs to be completed in the device manager.

For good, you need to disable the program service in the computer management.

Now delete all files related to the program from your computer, start with your personal folder in Program Files, then reboot if the program has not been deleted and it cannot be installed again, you will have to delete its records in the registry.

It is advisable to view the entire distribution or branch of HKEY_LOCAL_MACHINE (contains information about iron and software) and HKEY_CURRENT_USER \\ Software, where all information about installed applications is located.

What else can you do when problems with the removal of programs?

Try to visit the program manufacturer's website, the high probability is available to download the uninstallator, for example, on the Nero program site, which is not so easy to remove, there is such a utility.
If you delete a non-successful game or program, the uninstaller can be installed on the disk, it is necessary to start it and you will see the item Delete if you do not have the disk, read on.
In particularly difficult cases, you will have to go to your operating system in safe mode, only in it will be able to disable the service and delete all the remaining files and registry keys.
Sometimes you will not be able to delete the program files even in safe mode, but you will be able to rename them and after rebooting to delete.
It is worth trying to re-install the program, and then it will successfully delete.

For clarity, try to reinstall the game Call of Duty 4: Modern Warfarewhich a few days in a row can not reinstall the comrade for the arms of my son.

Goal msi.dll

Ailer MSI.DLL is required to install Microsoft Installer packets (MSI). If this file is deleted, Windows Installer will not work.

In this article, we will discuss an MSI.DLL error instance on a computer with a Windows system and its solution.

MSI.DLL Error in Windows

When you try to install any Windows Installer program on a Windows computer, you can get an error message similar to what is presented here:

"Msiexec.exe file is associated with missing MSI.DLL: 222 exports."

After pressing the button OK.The other error message appears similar to that mentioned below:

"I can not run C: \\ Windows \\ System \\ Msiexec.exe device connected to a system that does not work."

Cause of error

This problem occurs if Windows Installer files on the computer will try to update the Windows file installer.

Resolution

When the problem described above occurs, the first thing you need to do is restart the computer and try to install the Windows Office program again. If Windows Installer raised files, or files are not copied to the correct location. Instead, they first copied to a temporary folder. Only when you restart your computer files are copied to the appropriate folder. To solve this error message, follow these steps.

Task 1 - Download Installer Windows Update

Click the link button and click Download located near Instmsia.exe..
Save File on your desktop.

Task 2 - Rename Windows Installer files

Go to the menu Start and select Turn off computer.
Next, click Restart the computer in MS-DOS modeand then click OK. .
Enter the following commands on the command prompt and press the Enter key after each command to execute them. cD System
ren Msi.dll MSI.old.
ren msihnd.dll msihnd.old.
ren msiexec.exe msiexec.old.
eXIT
Restart Windows.

Task 3 - Run Windows in Safe Mode

Press the button Start and select Turn off computer.
Next, click Reboot and click OK..
Press and hold the button Shift.When the window is rebooted.

Task 4 - Installing Installer Windows Update for Windows

Double-click on the file Instmsia.exe.saved on the desktop.
Next, follow the instructions on the screen to complete the installation process.
Finally, restart the computer.

If the registry sets questions the reason for which DLL errors, such as msi.dll errors?

Yes, he do it because the registry is actually spoiled or damaged, it is often the cause of a common DLL error. Records related to DLL files are stored in the registry. You can receive repetitive DLL errors if the records related to DLL files are damaged or disappeared. Corrections of DLL errors, such as MSI.DLL errors, as a result of which the registry issues issues. Scan the registry using an effective registry cleaning program such as Reggenie. This is a powerful tool that allows you to perform a custom registry scan to correct DLL errors.

MSI.DLL is a security file?

Yes, True MSI.dll is a security file from Microsoft. However, several instances of malicious programs use the file named MSI.dll. To determine MSI.dll on your computer, this is not a threat system, scan the entire computer with the Windows system using reliable and efficient security tools.

To call the installation procedure or delete, you can use the MSIEXEC command with command line parameters. In the MSIEXEC command parameters, information is transmitted, which are usually indicated during an interactive installation using wEBSPHERE MQ Installation Panel. To do this, enter the following command in the command prompt with the necessary parameters: MSIEXEC [Parameters]

When working with WebSphere MQ in Windows ® Vista or Windows Server 2008 with the user-based user management (UAC), installation or deletion of messages must be launched from the command line with increased user access rights. To do this, right-click to launch the command line and select item. Run on the name of the administrator. When you try to start the non-interactive installation or deletion without enhanced user access rights, an AMQ4353 error message will appear in the installation protocol.

The MSIEXEC command supports two types of command line parameters:

First, specify the command prompt parameters in the MSIEXEC command, and then the Couples property \u003d value.

If the parameter is also specified on the command prompt, and in the response file, the value in the command line has a greater priority.

Msiexec command use example: MSIEXEC / I "" "/ L * V C: \\ install.log / m file-mif transforms \u003d" 1033.mst "agreetolicense \u003d" yes "addlocal \u003d" Server "where: / i " Path \\ MSI \\ IBM WebSphere MQ.MSI" Installing the product using the specified .msi file. / L * V C: \\ install.log Creating an Install.log protocol file containing installation. / M file-MIF Creating a Microsoft® System Management Server status file (SMS), .mif: file-MIF. Transforms \u003d "1033.mst" indicates that the installation is performed in English (USA). For more information about other languages, see Using Transformations for the Msiexec command. Agreetolicense \u003d "Yes" Take license terms. ADDLOCAL \u003d "SERVER" Installing the server component locally.

Table. 1. Msiexec command line parameters

Parameter	Options	Description
/ A.	Package	Administrative installation of the product over the network, i.e. Installing the source image of an application similar to the image on a CD.
/ I.	package\|product code	Installing or configuring a product using the specified file.msi. WebSphere MQ Windows installation package: IBM WebSphere MQ.MSi.
/ j.	Package \| Package / T. Transformlist.\| Package / G. LanguageID.	Product alert. This option ignores all the properties specified on the command line. u Alert Current User M Alert All Users of this System G Language ID T Applying Conversion to Package
/ L.	file-protocol	Specifies the path to the protocol file, as well as flags that indicate information for enhancing in the protocol. i state status W Disposable warnings e All error messages A Running actions R Actions Us U Custom Requests C Source User Interface Settings M Memory Lack Information or Fancy Output O Messages About Laptop Place on Disk P Terminal Properties V Detailed output + Information Added to an existing file! Each line is unloaded into the protocol * All information is entered into the protocol, except for the V option. To register all information, including the V option, specify "/ L * V"
/ Q.	n \| B \| R \| F	The level of the user interface displayed during installation. q, Qn without user interface. Non-interactive installation without user interface. QB basic user interface. The built-in window dialog boxes are displayed. The abbreviated user interface is displayed, the modal dialog window is displayed at the end of the installation. QF Full User Interface, at the end of the installation displays a modal dialog box. Qn + without a user interface, at the end of the installation displays the modal dialog window. QB + The main user interface, at the end of the installation displays the modal dialog window. The modal window is not displayed if the user canceled the installation. QB is the main user interface without modal windows. Please note: the user interface level / QB + is not supported.
/ X.	package\|product code	Removing the product.
Do not use the / i, / x, / j and / a options at the same time. Options / T and / G can only be used together with / j. Options / L and / Q can be used together with / i, / x, / j and / a.

In the tables, the use of the responses file with the MSIEXEC command.

Saveini. way\file name During installation, a response file is created. The file contains the parameters selected for this installation that the user can set during the interactive installation. Onlyini. 1 | YES | "" 1, YES or any other different value from zero: complete the installation before updating the target system, but after creating the response file (if specified).

"". Continue the installation and update the target system (default).

Transforms. way\file name Specifies the conversion files (.mst) to apply to the product. For example: File "1033.mst" indicates a transformation file for English Locali (USA).

Tutorial

Good day, hubr! I want to imagine an interesting, in my opinion, the way to create MSI installers for any software and, as a result, deploying it with GPO. It is emphasized that the described method does not imply the creation of "blinds" of the system, and uses native software installers, and only free products are used to create MSIs.

Introduction, couple links and disclaimer

Each normal software installer has the ability to automatically install with default or default parameters. The essence of my method is simple and is to pack the native installer into the "container" MSI and run it with the necessary command line parameters. In the network a bunch of information on the automatic installation of a particular application, and I will not sharpen attention on this. Our goal, I repeat, is the installation by means of group policies. By the way, some of you may argue that the installation can be made via ZAW, but, unfortunately, this method is applicable only to install with the rights of the current user and cannot be used for centralized automatic application installation.

Interesting cycle of articles on the installation of software through the GP. For beginners, I recommend reading everything to not ask if the type of installation "appointed" from "Public" is different.

Necessary software. EXE to MSI Converter Freeware and the first one is needed to create MSI from EXE, and the second is to get the resulting MSI-Nick to establish through group policies.

The method does not apply for complete uniqueness and in some places there may be excesses that could be avoided, but this is due to the lack of desire and the need to understand too deep into the parameters of the MSI packets. The initial purpose was raised to quickly find a free method of creating MSI and after several hours spent in reading foreign forums and endless reboots of the virtual machine, the method was found. Also, an article is not an overview of the program interface, and the screenshots you will not see.

Creation and preparation of the package

An example of the installation will be produced for Mozilla Firefox, since this is a widely known product that does not have an MSI installer from the developers.

Run EXE to MSI and specify the path to the EXE installer Firefox. According to the information previously found in the network it becomes clear that it is possible to install the fire chain in quiet -MSS -Ira.. They indicate them in the second field of the 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 in the article could be put point. Unfortunately, not everything is so simple. The current installation package is not suitable for deployment via GPO and when loading a computer you will receive absolutely nothing explaining errors in the logs "There was an incorrigible error ..." And the thing is that the EXE to MSI developers also want to eat and their free product generates MSI "not according to the rules".
Well, we take an orc and open our Emsyinik 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 should be unique to each product, and our EXE TO MSI generates always the same. Well, not trouble, click in the top menu View -\u003e Summary Information, we find the field Packagecode. and Zhmem. New Guid.. The resulting result is copied to the clipboard and insert into Productcode.. We repeat for Upgradecode. And finally for the very Packagecode.. Immediately B. Summary Information Rules Field Title On Mozilla Firefox, the rest is optional. This is, in fact, does not affect anything.
Again in the table Property. me ProductName on Mozilla Firefox (I'm still changing to heap Arpcontact. and Manufacturer.). You can also put the correct value for ProductVersion..
It seems to be GUID and other Ida changed, but as practice shows, this is not enough. Click to ORCA Tools -\u003e Validate, remove the bird Show Info Messages. And press Go..
As you can see, a bunch of errors for the presence / absence of some tables and values \u200b\u200bcame out. I did not bother and simply took the first (7zip x64 9.20) small MSI and copied 4 missing tables from there (via Export-Import, of course): _Validation, AdminexecuteSequence, AdminuiseQuence and AdvtexecuteSequence. In fact, I am sure that you can create a "right" MSI installer, without too much garbage, but do not forget, our goal is just running the native setup of the application in the quiet.
After adding tables, we pass again Tools -\u003e Validate (By the way, the first time check can not be done at all and immediately import tables). If you also took the MSI from 7zip as the basis, then the result will be six errors that need to be eliminated. Press Close., remove extra fields marked with red.
At the end, you can once again check the validation and make sure that there are only no disturbing varnings. Save MSI.
Here in principle, and everything, it remains to add MSI to the GP and assign the necessary properties.

Nuances

When installing the method described above, you will have two copies of software. The first is the actual appointment, and the second is the original MSI-Nick, because we as it were for it. In principle, it does not affect anything, except for displaying in "Installing and Deleting Programs", and that, only in Windows XP (if you did not change anything other than the one specified by me). The disadvantage may be the appearance of unnecessary programs with automatic software inventory if you use it.
Automatically delete the application by the same deployment tools. It will turn out to be more accurate, but not the necessary MSI container will be removed. Well, you can tinker with the properties of the MSI when it is created, so that it captures the application installed earlier, as twich. I did not put such a task.
When installing updates, you want to specify in the properties of the application of the application so that it replaces the previous one, that is, it was necessarily previously removed old. It guarantees that you will not have the most nobody surrendered left duplicate applications in the "Installation and Delete Programs".
To install an application that has a distribution from multiple files, you will have to first pack it in EXE, which when started it will unpack and give a command to a quiet installation. I recommend creating SFX archives to the means of the same 7-zip.
Nothing prevents it from putting through the startup scripts. Moreover, this method is more flexible, and I have long used it through my scripts. That's just the use of native treaties of GP, it turns out much faster, since the simple creation of MSI from EXE takes a couple of minutes.
Windows 7 for some reason does not write "Installing the managed application ...", and simply says "Please wait." When you first deploy the whole pile of software at once or when installing a heavy application, it can combine the user to call the admin either or pressing the totter button.

It seems to be everything, I hope it was interesting, share your experience.

Errors When installing applications from files with extension. MSI is one of the manifestations of the Windows Installer service (in the Russian-language version - Windows Installer). Such a phenomenon face users of all versions of this OS, with the exception of the earliest. Until now, the problem with the installer is one of the frequent reasons for which users are solved on reinstalling the system. Let's try to figure out how to avoid it. The reason for Windows Installer does not work, maybe the following:

viral infection, and the removal of the virus does not always solve the problem;
incorrect installation of Windows updates;
the protection software fails when, instead of blocking one suspicious MSI file, the installation service is blocked entirely;
changes in security policies on a computer;
damage to system files or registry for reasons not related to viruses (removal of installer components, unqualified registry editing, "Curve" software, hard disk malfunction, etc.).

Check the integrity of the Windows Installer structure

Windows installer is represented by the following components:

c: \\ Windows \\ System32 \\ Msiexec.exe file - directly by the installer appointment;
c: \\ Windows \\ System32 \\ MSI.DLL file - Windows Installer library;
the MSISERVER service, the parameters of which are stored in the Registry section.

Before diagnostics, it is important to make sure that there are both of these files in the system, which in the registry has the above section and its parameters have normal values \u200b\u200b(values \u200b\u200bcan be viewed in the registry of a similar, working system). Also open the list of services (click Windows + R and enter the "Open" line to "Run" the Services.msc command). Find the Windows Installer and make sure it starts.

In the absence of files, copy them from another system of the same version or from the installation disk. If there is no registry key or damaged - also transfer it from the working system. To do this, on a good computer, run the registry editor (C: \\ Windows \\ regedt.exe) and find the above section.

Expand the MSISERVER folder context menu and click Export. Save the file in format.Reg and transfer it to a problem machine.

Click twice this file and confirm your consent to add data to the registry. Restart the computer.

If the MSISERVER service is still not started, check if the RPC service works (remote procedure call) from which it depends.

You can re-establish the installer files and restart the service using a set of special commands, on the command prompt. For convenience, you can create a command file: Insert a set of actions in a notebook and save both with the extension.Bat. To start the file, just double click on it. To make changes to act, click on the desktop and press F5.

Check the security settings and access rights

Windows Installer may not work and due to the fact that it blocks the protective software or the operating system does not have the necessary rights. To begin with, we will deal with the software. If you have installed antivirus - temporarily disconnect it. Methods for disconnecting each product, but most often this is done through the antivirus icon context menu in the system tray. Now we will deal with rights. Open the msiexec.exe context menu and expand its properties.

Check the list of groups and users on the Safety tab. Among them, there must be a "system" and the "TrustedInstaller" service, and the last one must have full access to the file and be its owner. The system must have the rights to read and read and execute.

The TrustedInstaller service first appeared in Windows Vista, so in Windows XP full access must be provided with the system. Everything that is written below relate to versions released later than XP. To check who owner Msiexec.exe, click the "Advanced" button on the same tab.

In the next window, discover the "Owner" tab. Make the owner of the TrustedInstaller service if something else is specified as it. If you do not have it in the "Change Owner to" list, click the "Change" button, and next - "Other users and groups".

Enter TrustedInstaller in the field "Enter the names ...", click "Check Names" and OK. Return to the previous window. On the "Existing Permissions" tab, assign TrustedInstaller and the system necessary rights.

Exactly the same security settings must be at the MSI.dll library. Now check if there are no restrictions for the user "System" to access the following:

system disk (usually drive C);
temporary folders (this is C: \\ Windows \\ TEMP and C: \\ Users \\ Current user \\ APPDATA \\ TEMP);
c: \\ Config.msi folder;
the folder where the MSI file is located from which you are trying to install the program.

All these objects system must provide full access. It is also done as we disassembled above. After these operations, in most cases, the problem with the installer is successfully solved. If our tips did not help you, the reason for the failure lies in something else and experts should already be dealing with it.

Not rarely when trying to delete the program, users face that the program is not deleted. When you try to start deleting a program through the "Control Panel", the user receives an error that interrupts the removal process. After that, the program remains on the computer.

If you also do not know how to delete a program that is not deleted, then this article should help you. Here we will look at three simple and effective ways to solve this problem.

Method number 1. Stop all the processes related to the program.

If the program is not deleted, then, most likely, it is currently working. To stop the operation of the program, open "" (for example, using the CTRL + SHIFT + ESC key combination) and go to the list of processes. In the list of processes, you need to find those processes that are associated with the program and stop them.

If you have Windows 8 or Windows 10, then you need to click right-click on the process you want to complete, and in the menu that appears to select "Remove the task". In Windows 7 and older versions of Windows, the menu item you need will be called "Complete Process".

After all the processes associated with the program are stopped, you need to repeat the program to delete the program. If this method did not help delete the program, then try to restart the computer and try again. You may have hung something and thus blocked the removal of the program.

Method No. 2. Use a special program to remove programs.

If the program is not deleted and after rebooting, you can try to delete it using a special program. The most popular program of this kind is. This program allows you to delete any other programs. In this case, the removal is possible even in cases where the uninstaller does not work or the program is not displayed in the control panel.

Use Revo Uninstaller is quite simple. First you need to start this program and wait until it scans the computer and displays all installed programs. After that you need to click the right mouse button on the program you want to delete and select "Delete" item.

After that, a window will appear in which you want to select a method for removing the program. In most cases, the option "moderate" is suitable.

Here you can click on the "Select All" button and confirm the removal by clicking on the "Next" button.

Method # 3. Delete the program through a safe mode.

If nothing of the above does not help remove the program, you need to download the computer to and try again.

In safe mode, only the main components of the operating system are loaded, other programs that can block deletion are not loaded. Therefore, in safe mode, the removal must pass without problems.

When installing programs and components of Windows, distributed in the form of an installer with extension.msi You may encounter an error "Failed to access the Windows Installer Installer service." You can encounter a problem in Windows 10, 8 and Windows 7.

In this manual, it is detailed how to fix the error "failed to access the Windows Installer Installer service" is presented several ways, starting with simpler and often more efficient and ending with more complex.

Sometimes system tweaks and changing the Windows installer policies can lead to an error in question.

If you have Windows 10, 8 or Windows 7 professional (or corporate), you can check whether the Windows installer policies have been changed as follows:

If your computer has a home edition of Windows, the path will be as follows:

Go to the registry editor (Win + R - regedit.).
Go to HKEY_LOCAL_MACHINE \\ Software \\ Policies \\ Microsoft \\ Windows \\ and check if it has a subsection named Installer. If there is - delete it (right click on the "folder" Installer - delete).
Check for a similar section in HKEY_CURRENT_USER \\ SOFTWARE \\ POLICIES \\ Microsoft \\ Windows \\

If the specified methods did not help, try to restore the Windows Installer service manually - 2nd method in a separate instruction