home » Health and beauty » Failed to access windows 7 installer service. Failed to access windows installer service. Follow the instruction below

Failed to access windows 7 installer service. Failed to access windows installer service. Follow the instruction below

Sometimes, during the installation of a program, an error code 1719 may pop up on the screen, which says that the Windows installer service is not available. There can be several reasons for this problem. Let's look at them and try to solve them.

Windows 7, 8, 10 Installer Service is unavailable or not responding

Scanning system files

So, when you see such a message on the screen, you should immediately scan the system files. To run the scan tool, you need to run the command line as administrator, click Start on the desktop - enter cmd in the search, click on the corresponding icon command line right click mouse and select - Run with administrator rights. In the command line window that opens, write the sfc / scannow task and click Enter... Once the verification is complete, your problem can be resolved.

Windows installer

Open up Start - Run... In the window that opens, enter the services.msc task.

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 through the Command Line. In it you need to register net start MSIServer and press Enter... After that, you will see a corresponding notification that the service is running.

Deleting and re-registering a service

If, after the performed manipulations, 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 you have installed on your computer is 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 msiexec / unregister, which will deactivate the installer. Click Enter and then enter msiexec / register, which will re-register it.

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

Then restart your machine.

The second option involves using the Run service, which can be opened from the Start menu. In the line enter msiexec / unregister and click OK. Then enter msiexec / regserver. Don't worry if you don't see any changes on the screen. Your problem, however, should disappear after this.

Registry changes

A more radical method is to change parameters in the registry. In the Run service, enter the regedit command. The 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 item name and enter the required parameters in the window that appears. After that, you need to start the services.msc service as described.

On a 64-core system, the WOW64 option must also be considered. Its indicator should be equal to 0, the system of calculation should be hexadecimal.

After making the changes, restart your computer. There should be no more mistakes.

Removing a program

Sometimes the program does not allow you to install the presence outdated version... Then it must be removed. To do this, go to Start - Control Panel - Programs. Find the Uninstall / Change program function and apply it to the shortcut you need. Then reboot the system and try to install again.

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: The service could not be started on the local computer ... Error 2: The specified file cannot be found. Or the service is not listed.

To restore service Windows Installer follow these guidelines.

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 your computer antivirus program installed on the system. And also download the cure utility from dr.web (dr.web cureit! ®) and perform the check again with this utility.

Check the startup type for the Windows Installer service

To do this, open Control Panel - Administrative Tools - Services. Locate the Windows Installer service in the center. Right-click on it and select Properties from the context menu. See which startup type is set. Change it to automatic, restart your computer and check if the problem recurs 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 automatic, then check whether it starts itself windows program installer. To do this, click Start - Run - Type msiexec and press enter. This should open a window in which the windows installer version and available commands will be written.

Files required for Windows Installer to function may be damaged

To check system files for integrity, open a command prompt as administrator (click Start - All Programs - Accessories - Right-click on Command Prompt - Run as Administrator) and in 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 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 test the Windows Installer.

If the problem persists, 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 \u200b\u200bon the problem computer.

It is rare to deal with applications distributed in the form of MSI installers, but for some reason they cause the most problems for users. The most common of these is the error "Failed to access the service. windows Installer Installer ", and you can run into it at any windows versions... In most cases, the error is associated with incorrect work the corresponding service - Windows Installer or msiserver. Most often, it turns out to be disabled when checked. You can make sure that everything is in order with the service as follows.

Open the services.msc command in the service management snap-in and look for Windows Installer in the list.

By default, this service is in an inactive state and the startup type is set to Manual.

In theory, when the executable MSI file is launched, 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 unavailable, 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 value of the Start parameter from 4 to 3, and then reboot.

The launch type will change to Manual, and the launch button will become active. To set the startup type to Automatic, the Start value must be replaced with 2. Since the msiserver service is dependent, we recommend that you also check the status of the RPC service. It must be running and the startup type must be "Automatic".

It may be that the Windows Installer service will not be listed at all. The most likely reason for this is corruption of the data in the registry responsible for it. 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 the operating system to the latest current build, if this option is acceptable to you.

It's also a good idea to check your Windows Installer policy settings. Use the gpedit.msc command to invoke the local policy editor and follow the chain Computer configuration - Administrative templates - Windows components - Windows Installer. All policies must have a status of Not Configured.

Check the settings in the User Configuration section in the same way.

Finally, you can restore the normal operation of the Windows Installer service by manually re-registering it. To do this, open the command line on behalf of the 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 the installer service should be started with the net start MSIServer command, if for some reason it does not start itself.

If programs from .msi files do not start, this is a direct indication of a problem. windows services Installer. Any Windows 7 user can face a similar phenomenon. Therefore, if Windows Installer does not work for you, it is worth reading some recommendations.

Causes of Windows Installer crashes

The reasons for Windows Installer not working can be the following factors:

Viral lesion system files... At the same time, cleaning the OS does not always solve the problem.
Incorrect installation of updates.
Incorrect editing of the registry, removal of installer components.
Antivirus blocking .msi file
Change of PC security policy.

All of these factors can affect the operation of the Windows Installer service.

Checking the integrity and health of files

Windows Installer consists of the following components:

The msiexec.exe file, which is located on the "C" drive in the "Windows" and "System32" folders.
The msi.dll file, which is nothing more than an installer library.
The Msiserver service, whose parameters are located in the registry editor key at 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 that there are no unnecessary values. The correct list is shown in the photo.

If there is no section or some files are missing, copy the elements on the working system and, by right-clicking, select "Export".

Select the location to save the files and write 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".

Access rights check

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 see that the user has full access to the service.

Windows 7, 8, 10 Installer Service is unavailable or not responding

Scanning system files

So, when you see such a message on the screen, you should immediately scan the system files. To run the scan tool, you need to run the command line as 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, write the sfc / scannow task and click Enter... Once the verification is complete, your problem can be resolved.

Windows installer

Open up Start - Run... In the window that opens, enter the services.msc task.

In the new window, find the Windows Installer item.

Deleting and re-registering a service

If, after the performed manipulations, 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.

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

Then restart your machine.

Registry changes

A more radical method is to change parameters in the registry. In the Run service, enter the regedit command. The Registry Editor window will open. In it, you need to follow the branch:

HKEY_LOCAL_MACHINE \\ SYSTEM \\ CurrentControlSet \\ services \\ msiserver

Hello. Today I want to bring up a topic that has become painful. I don’t know about you, but lately at work I’m quite often faced with Windows Installer problems - errors msi... Moreover, this question is relevant both for the good old Windows XP, and for the relatively "fresh" Windows 7 and Windows 8. Let's analyze this issue in detail, since the topic is very serious and if the problem arose once, then believe me, it’s life for you complicate - definitely.

What are these files that have the extension msi?

This is the installation package file that installs the software and uses the Windows Installer service. Name extension msi took from Microsoft Installer » as the Windows Installer version was previously called. Such a file contains a complete script for installing a software product, auxiliary components, libraries and, in most cases, all installation files compressed into cab archives. You can discuss for a long time all the advantages and disadvantages of the Windows Installer, but you still have to accept it "as is", and we will correctly and adequately respond to some problems in the work. Errors can occur both in the operation of the service and due to the msi files.

Here's what sometimes happens: and then the system asks me to make sure if there really was an installer file that I ran. Sounds strange at first. But, reading the message from the system further, I understand that I am being asked to make sure not only that the file is present, but also my rights to access it. As it turned out, it was not me, but Windows Installer was deprived of access to the file, hence the problem.

This issue is not resolved in a complicated way. Let's first make sure that the system has full access to the file, for which in the "Properties" of the file go to the tab "Security" and find the user "System (System)".

I am more than sure that you will not find it there, so we add it ourselves - 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).
We confirm - OK and put a mark in the checkbox “ Full access", We 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 folder with the contents, from which, as usual, the installation takes place software (as in my case the "Install" folder).

If you have Windows XP on your computer 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 general access to files ". Also, you risk not finding this tab in different "assemblies" and "light versions" of both Windows XP and Windows 7. To access this tab, you will have to boot into Safe mode and log in with 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 msi-file properties, put a tick in the corresponding checkbox).

There may also be problems when you try to install the program from a removable media, flash drive, for example (you can prohibit such actions in the operating system settings) - 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 the installation package into it, from there and run the installation - it is useful for errors number 1603, 214 728 7035, 2203 and 1723.

Make sure that the system has access to the temporary file directories. Open "System Properties" (Win + Pause or in context menu by right-clicking on the My Computer icon, select the Properties line), in the "Additional system parameters",

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 if the system has access to them (according to the algorithm already described above). I hope you remember that 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 make a transition to the folder. And at the same time you can do a useful thing - to clear all temporary folders from their contents.

It will also be the right decision to check for access rights the directories in which you plan to install applications and the directory named Config. Msi fundamentally system partition... For all the directories indicated above, encryption must be disabled, since Windows Installer in this case does not have access to them, unlike the user.

Well, and 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 from another mirror.

Cause of Windows Installer error

Now it's 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, whatever application you are trying to install, then most likely the problem is in the installer service itself. System error messages may appear that include relevant phrases such as: Installer Package Error or Windows Installer Error. The reason for this can be both errors in the system registry and a virus attack. Let's start by checking the status of the Windows Installer service and the type of startup. For this purpose, we enter the command in the Run line (Win + R) services. msc, and in the console that opens, we find the desired item - "Windows Installer".

Let's see if it works and what it has Startup type (must be set Manually) If the service does not work and has a different startup type, then we start (click “Start”, you can - “Restart”) it, and in the properties we change the startup type 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 parameters for launching Windows Installer and its version number.

I see further elimination of the problem in fixing corrupted operating system files. To implement this, in the "Run" line, execute the command sfc/ scannow (Prepare in advance the disk from which you installed your operating system, it may be required in this process) and then restart the computer. The problem, in theory, should disappear.

In the event that the "Status" column indicates that the installer is working, although this does not correspond to reality at all, you can try to restart this service by clicking the corresponding item in the upper left corner. After that, all that remains is to restart the computer and test the Windows Installer. If, after such settings, the program returns to normal, we can congratulate ourselves, this "torment" is over. Otherwise, you will have to "step" further.

Step # 3: Re-register the service via the command line

You can return the Windows 7 installer to normal operation by re-registering such a service in the system. How do we act?

We go to the "Start" menu, set the cmd value in the search and press Enter. Next, in the console that appears, we drive the msiexec / unregister parameter, click Enter, and then after the command line response, enter the msiexec / register value into it and press Enter again:

We repeat entering commands if we are dealing with 64-bit Windows 7, and then restart the computer. In principle, this is often where all the difficulties with Windows Installer end. However, if the working atmosphere did not return to the Windows installer after that, before reinstalling it, you can try to reanimate it through the registry editor. But what if?

Step # 4: Debug via Registry Editor

You can try to resurrect Windows Installer through the registry editor in this way:

and delete all available parameters in them:

If there is no data in the destination folders, right-click on the Installer folder, and then click the "Permissions" item in the list that appears. Next, in the window that opens, click on System, mark the "Full Control" parameter and click OK: