There is no Windows installer in local services. Failed to access Windows Installer service
Sometimes, during the installation of a program, an error code 1719 may appear on the screen, which indicates that the Windows Installer service is unavailable. There may be several reasons for this problem. Let's understand them and try to solve them.
Windows 7, 8, 10 installer service is unavailable or not responding
Scan system files
So, when you see a similar message on the screen, you should immediately scan your system files. To run the scanning tool, you must run the command prompt as an administrator, click Start on the desktop - enter cmd in the search, right-click on the corresponding command line icon and select - Run with administrator rights. In the command line window that opens, enter the task sfc/scannow and click Enter. Once the check is completed, your problem may be resolved.
Availability of windows installer
Open Start - Run. In the window that opens, enter the task services.msc.
In the new window, find the Windows Installer item.
Double click on the icon. In the window, find the Startup type parameter and make sure that Automatic or Manual is selected next to it. After that, select Run and click OK. Next, you need to restart your computer for the changes to take effect and try to reinstall the required program.
You can also run the installer via the Command Line. In it you need to write net start MSIServer and click Enter. After this, you will see a corresponding notification that the service is running.
Removing and re-registering a service
If after the above machinations the error still occurs, try re-registering the installer. This can be done in two ways: using the Command Line and using the Run service.
Let's consider the first option. Check which version of the operating system is installed on your computer, 32-bit or 64-bit. To do this, go to My Computer and right-click on an empty space. Select Properties. In the pop-up window you will find the required information.
Log in to the Command Prompt as an administrator (how to do this is described above). For a 32-bit system, type the command msiexec /unregister, which will deactivate the installer. Click Enter and then type msiexec /register which will log it back into the system.
If your system is 64-bit, then the commands will be as follows:
%windir%\system32\ msiexec.exe /unregister
%windir%\system32\ msiexec.exe /regserver
%windir%\system64\ msiexec.exe /unregister
%windir%\system64\ msiexec.exe /regserver
After this, reboot the machine.
The second option involves using the Run service, which can be opened through the Start menu. At the prompt, type msiexec /unregister and click OK. Then type msiexec /regserver. Don't worry if you don't see any changes on the screen. Your problem should, however, disappear after this.
Registry changes
A more radical method is to change settings in the registry. In the Run service, enter the command regedit. A Registry Editor window will open. In it you need to follow the branch:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver
Find ImagePath and make sure its value matches the following: %systemroot%\system32\msiexec.exe /V. If the indicator is different, double-click the left mouse button on the name of the item and enter the required parameters in the window that appears. After this, you need to start the services.msc service as described.
Hello. Today I want to raise a topic that has become sore. I don’t know about you, but lately at work I’ve been encountering Windows Installer problems quite often – errors msi. Moreover, this issue can be relevant both for the good old Windows XP and for the relatively “fresh” Windows 7 and Windows 8. Let’s look at this issue in detail, since the topic is very serious and if the problem arose once, then believe me, it will last a lifetime It will definitely complicate things.
What kind of files are these that have the msi extension?
This is the installation package file that installs the software and uses the Windows Installer service. Own extension name msi taken from "Microsoft Installer » , as the Windows Installer version used to be called. Such a file contains a complete installation script for the software product, auxiliary components, libraries and, in most cases, all installation files compressed into cab archives. We can discuss for a long time all the advantages and disadvantages of the Windows Installer, but we will still have to accept it “as is,” and we will respond competently and adequately to some problems in its operation. 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 verify whether there really was an installer file that I ran. At first it sounds at least strange. But, reading further the system message, I understand that I am being asked to verify not only the presence of the file itself, but also my rights to access it. As it turned out, it was not me, but Windows Installer was denied access to the file, hence the problem.
This issue is not resolved in a complicated way. Let's first make sure whether the system has full access to the file, for which in the “Properties” of the file, go to the “Security” tab and find the user “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 of the English version of the system),
then click on “Check names” (the line becomes underlined).
Confirm – OK and check the “Full access” checkbox, confirm again.
Click on “Advanced”, then – “Change permissions” – “Add permissions” »,
inherited from parent objects and we confirm everything three times.
Thus, we got rid of this installer error, and it will no longer bother us during the installation process. Although it would be more reasonable and prudent to add full system access rights to the entire content folder from which the software is usually installed (as in my case, the “Install” folder).
If your computer has a Windows XP operating system and "simple file sharing" is enabled in Folder Options, you will not see the Security tab in the file properties. In this case, you should go to “Folder Options” and uncheck the “Use simple file sharing” checkbox. Also, you risk not finding this tab in different “builds” and “lite versions” of both Windows XP and Windows 7. To access this tab, you will have to boot into Safe mode and log in under an administrator account.
Another problem with 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).
There may also be problems when trying to install the program from removable media, a flash drive, for example (such actions can be prohibited in the operating system settings) - just copy the installation file to a convenient location on your hard drive. Another option to solve the problem is to create a new folder under any name you like and copy the installation package into it, and from there 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 the temporary file directories. Open “System Properties” (Win+Pause or in the context menu by right-clicking on the My Computer icon, select the line Properties), in “Advanced system settings”,
On the "Advanced" tab, click on the "Environment Variables" button.
We find the folders of temporary variables (they have the words TEMP, TMP in their names), check whether the system has access to them (using 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, having copied 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 something useful - clear all temporary folders from their contents.
It would also be the right decision to check for access rights those directories in which you plan to install applications and a directory named Config.
Msi at the root of the 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 of checksums), in such a situation it is necessary to get hold of a known “working” normal installation file. Most likely, it will make sense to download it from another source or through another mirror.
Cause of Windows Installer Error
Now it’s worth considering a situation where installation of an 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. System error messages may appear containing phrases such as: Installer package error or Windows Installer Error. The reason for this could be errors in the system registry or a virus attack. Let's start by checking the status of the Windows Installer service and how it is started. For this purpose, in the Run line (Win + R) we enter the command services. msc, and in the console that opens we find the item we are looking for - “Windows Installer”.
We see if it works and what its Startup Type is (must be set to Manual). If the service does not work and has a different startup type, then we start it (click “Run”, you can click “Restart”), and change the Startup Type in the properties to "Manual". If the service is running, 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 Windows Installer launch parameters and its version number.
I see further elimination of the problem in correcting damaged system files of the operating system. To implement this, in the “Run” line, execute the command sfc/ scannow(prepare in advance the disk from which your operating system was installed, it may be needed in this process) and then reboot the computer. In theory, the problem should disappear.
If the “Status” column indicates that the installer is running, although this is not at all true, you can try to restart this service by clicking the corresponding item in the upper left corner. After this, all that remains is to restart the computer and test the functionality of the Windows Installer. If after such settings the program returns to normal, we can congratulate ourselves, the “torment” is over. Otherwise, you will have to “step” further.
Step #3: Re-registering the service via the command line
You can return the Windows installer on 7 to normal operation by re-registering such a service in the system. How do we act?
Go to the Start menu, enter cmd in the search box and press Enter. Next, enter the msiexec /unregister parameter into the console that appears, press Enter, and then after the command line responds, enter the msiexec /register value into it and press Enter again:
We repeat entering the commands if we are dealing with 64-bit Windows 7, and then reboot the computer. In principle, this is where all the difficulties with Windows Installer often end. However, if the working atmosphere for the Windows installer has not returned after this, before reinstalling it, you can try to revive it through the registry editor. What if?
Step #4: Debugging via Registry Editor
You can try to resurrect Windows Installer through the registry editor in this way:
and delete all existing parameters in them:
If there is no data in the destination folders, right-click on the Installer folder, and then click “Permissions” in the list that appears. Next, in the window that opens, click System, check the “Full Control” option and click OK:
When installing any program with the .msi extension, it writes about a problem with the Windiws Installer service, and when starting this service, it writes: The service could not be started on the local computer... Error 2: The specified file cannot be found. Or this service is not in the list.
To restore the Windows Installer service, follow these guidelines:
How to repair Windows Installer
Check your computer for viruses
The first thing you need to do is make sure that your computer is not infected with viruses. To do this, we recommend checking your computer with an antivirus program installed on the system. And also download the treatment utility from dr.web (dr.web cureit!®) and check again with this utility.
Check what startup type is set for the Windows Installer service
To do this, open Control Panel - Administration - Services. Find the Windows Installer service in the central part. Right-click on it and select Properties from the context menu. See what startup type is set. Change it to automatic, restart your computer and check whether the problem recurs or not.
If the service is not in the list, or the problem remains, read below.
Does the windows installer program itself start?
If the problem repeats or the startup type has already been set to automatic, then check whether the windows installer program itself starts. To do this, click Start - Run - Type msiexec and press enter. This should open a window in which the version of windows installer and available commands will be written.
Files required for Windows Installer to function may be damaged.
To check system files for integrity, open the command line as an administrator (click Start - All Programs - Accessories - Right-click on Command Prompt - Run as administrator) and in the command line run the command
Sfc /scannow
Restart your computer and check whether 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 one:
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 the Windows Installer.
If the problem persists, compare the contents of the registry branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver with the same branch on another computer and, if necessary, correct the values on the problem computer.
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.
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 the working system. To do this, on a working computer, run the registry editor (C:\Windows\Regedt.exe) and find the above section. 
Right-click 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 agree to add data to the registry. Restart your computer. 
If the Msiserver service still does not start, check that the RPC (Remote Procedure Call) service on which it depends is running. 
You can re-register the installer files and restart the service using a set of special commands on the command line. For convenience, you can create a batch file: paste a set of actions into Notepad and save it as a .bat extension. To launch a file, simply double-click on it. For the changes to take effect, click on the desktop and press F5. 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.
You rarely have to deal with applications distributed as MSI installers, but for some reason they cause the most problems for users. The most common of them is the error “Could not access the Windows Installer service,” and you can encounter it in any version of Windows. In most cases, the occurrence of an error is associated with incorrect operation of the corresponding service - Windows Installer or msiserver. Most often, when checking, it turns out to be disabled. You can make sure that everything is in order with the service as follows.
Open the service management snap-in with the command services.msc and find the “Windows Installer” item in the list.
By default, this service is in an inactive state, and its startup type is selected as “Manual”.
In theory, when you run the executable MSI file, it should be automatically activated, but this will not happen if for some reason the startup type is set to “Disabled”. You need to change the settings by selecting the “Manual” option in the drop-down list, but most likely the settings will be inaccessible, which is typical for Windows 10. You will have to work around it.
Open the HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/msiserver key in the registry editor and change the Start value from 4 to 3, and then reboot.
The startup type will change to Manual and the startup button will become active. To set the startup type to Automatic, the Start value must be changed to 2. Since the msiserver service is a dependent service, we also recommend checking the status of the RPC Remote Procedure Call service. It must be running and the startup type must be “Automatic”.
It may happen that the Windows Installer service will not appear in the list at all. The most likely reason for this is damage to the data responsible for it in the registry. In this case, try to restore it by merging the Windows_Installer.reg file, available at https://cloud.mail.ru/public/2eVp/mWmQUP8FG. After applying the tweak you will need to restart your computer. You can also update your operating system to the latest build, if that's an option for you.
It's also a good idea to check your Windows Installer policy settings. Using the gpedit.msc command, call the local policy editor and follow the chain Computer Configuration - Administrative Templates - Windows Components - Windows Installer. All policies must have the status "Not Configured".
Similarly, check the settings in the User Configuration section.
Finally, you can restore the Windows Installer service to normal operation by manually re-registering it. To do this, open the command line as administrator and sequentially execute the commands specified in this text file - https://cloud.mail.ru/public/9bBp/bYNiRVB82. After re-registering the service, the computer should be rebooted, and then start the installer service with the net start MSIServer command, if suddenly for some reason it does not start on its own.
Safe Mode in Windows systems is one of the basic tools that allows you to restore system functionality. One of the significant disadvantages of safe mode is the inability to install/uninstall programs from msi packages. This limitation is due to the fact that the developers considered the service Windows Installer(Window Installer) is potentially unsafe, and decided to cancel the start of this service when the system boots in safe mode. Which in some cases is extremely inconvenient.
Most modern applications use the Windows Installer service for their correct installation/uninstallation, and if it is not available, their installation or uninstallation is impossible. Let's assume that in order to restore the system's functionality, it is necessary to remove in safe mode some application that interferes with the normal loading of the system (for example, an antivirus). When you try to run a standard uninstaller to remove an application, the system reports:
The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personal for assistance
It is also not possible to manually start the Windows Installer service in Safe Mode (Services -> Windows Installer -> Start):
Windows could not start the Windows Installer service on Local Computer. Error 1084: This service cannot be started in Safe Mode
However, there is a small trick that allows you to start the Windows Installer service in safe mode and correctly uninstall the software.
To enable the Windows installer service in Safe Mode:
After starting the MSISServer service, it is possible to directly uninstall/install any application with an msi installer in safe mode.
