Full Fix: ‘Windows Installer Service could not be accessed’ on Windows 10

By: Milan Stanojevic
8 minute read
windows 10 clock fix

For various PC problems, we recommend to use this tool.

This tool will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Quickly fix PC issues and prevent others from happening with this software:

  1. Download this PC Repair Tool with Patended Technologies
  2. Click “Start Scan” to find Windows issues that could be causing PC problems.
  3. Click “Repair All” to fix all issues (requires upgrade).

We all have all sorts of applications that we use on daily basis installed on our Windows 10 PCs. Unfortunately, few users reported Windows Installer Service could not be accessed error while trying to install new applications. This sounds rather serious, but there’s a way to fix this error.

Windows Installer Service could not be accessed on Windows 10

Many users reported that they are unable to install certain applications due to Windows Installer Service could not be accessed error message. Speaking of this problem, these are some of the most common issues that users reported:

  • Windows Installer Service could not be accessed Safe Mode – Many users reported this error message while trying to install applications in Safe Mode. To fix this error, be sure to try some of our solutions.
  • Windows Installer not working Windows 10 – Several users reported that Windows Installer isn’t working at all on Windows 10. To fix the problem, be sure to check if the Windows Installer service is properly running.
  • Windows could not start the Windows Installer Service on local computer – If this error message appears on your PC, you might be able to fix it simply by re-registering Microsoft Installer Service.
  • Windows Installer Service could not be accessed error message when installing application – This message usually appears when trying to install new applications on your PC. Sometimes this can be caused by file corruption, so be sure to run both SFC and DISM commands.
  • Windows Installer Service could not be accessed error 1719, 1601 – Error 1719 and 1601 are closely related to this error message, and if you encounter them, be sure to try some of our solutions.
  • Windows Installer Service could not be accessed Adobe Reader, Skype, Kaspersky, McAfee, .Net Framework 4 – This error message can affect many applications, and if you’re having this problem, be sure to remove any previous version of the application you’re trying to install.
  • Windows Installer Service could not be accessed not correctly installed – This is another problem that can occur with Windows Installer Service. If you’re having this error, be sure that your services are configured properly.

Solution 1 – Reset Windows Installer Service registry

In order to perform this step, you need to add certain values to the registry. Bear in mind that modifying registry can cause system instability if not performed properly, so make sure you create a backup. To create a backup of your registry, do the following:

  1. Press Windows Key + R and enter regedit. Press Enter or click OK.
    Windows Installer Service could not be accessed Safe Mode
  2. Once Registry Editor opens, select File > Export.
    Windows Installer not working Windows 10
  3. Select All as Export range, enter the name of the file and click Save. In case anything goes wrong, you can just run this file and restore your registry.
    Windows Installer Service could not be accessed error message when installing application
  4. Once you’ve created your backup, close Registry Editor.

With registry backup created, you need to create a .reg file and add it to the registry. To do that, follow these steps:

  1. Open Notepad.
  2. Paste the following text into Notepad:
    • Windows Registry Editor Version 5.00
      [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver]
      “DisplayName”=”@%SystemRoot%\\system32\\msimsg.dll,-27”
      “ImagePath”=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,\
      74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,\
      00,73,00,69,00,65,00,78,00,65,00,63,00,20,00,2f,00,56,00,00,00
      “Description”=”@%SystemRoot%\\system32\\msimsg.dll,-32”
      “ObjectName”=”LocalSystem”
      “ErrorControl”=dword:00000001
      “Start”=dword:00000003
      “Type”=dword:00000010
      “DependOnService”=hex(7):72,00,70,00,63,00,73,00,73,00,00,00,00,00
      “ServiceSidType”=dword:00000001
      “RequiredPrivileges”=hex(7):53,00,65,00,54,00,63,00,62,00,50,00,72,00,69,00,76,\
      00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,61,00,\
      74,00,65,00,50,00,61,00,67,00,65,00,66,00,69,00,6c,00,65,00,50,00,72,00,69,\
      00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,4c,00,6f,00,63,00,\
      6b,00,4d,00,65,00,6d,00,6f,00,72,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,\
      00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6e,00,63,00,72,00,65,00,61,00,\
      73,00,65,00,42,00,61,00,73,00,65,00,50,00,72,00,69,00,6f,00,72,00,69,00,74,\
      00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,\
      65,00,43,00,72,00,65,00,61,00,74,00,65,00,50,00,65,00,72,00,6d,00,61,00,6e,\
      00,65,00,6e,00,74,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,\
      00,00,53,00,65,00,41,00,75,00,64,00,69,00,74,00,50,00,72,00,69,00,76,00,69,\
      00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,53,00,65,00,63,00,75,00,72,00,\
      69,00,74,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,\
      00,53,00,65,00,43,00,68,00,61,00,6e,00,67,00,65,00,4e,00,6f,00,74,00,69,00,\
      66,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,\
      00,65,00,50,00,72,00,6f,00,66,00,69,00,6c,00,65,00,53,00,69,00,6e,00,67,00,\
      6c,00,65,00,50,00,72,00,6f,00,63,00,65,00,73,00,73,00,50,00,72,00,69,00,76,\
      00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6d,00,70,00,65,00,\
      72,00,73,00,6f,00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,\
      00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,61,00,74,00,65,00,\
      47,00,6c,00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,\
      00,67,00,65,00,00,00,53,00,65,00,41,00,73,00,73,00,69,00,67,00,6e,00,50,00,\
      72,00,69,00,6d,00,61,00,72,00,79,00,54,00,6f,00,6b,00,65,00,6e,00,50,00,72,\
      00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,52,00,65,00,\
      73,00,74,00,6f,00,72,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,\
      00,65,00,00,00,53,00,65,00,49,00,6e,00,63,00,72,00,65,00,61,00,73,00,65,00,\
      51,00,75,00,6f,00,74,00,61,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,\
      00,65,00,00,00,53,00,65,00,53,00,68,00,75,00,74,00,64,00,6f,00,77,00,6e,00,\
      50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,54,\
      00,61,00,6b,00,65,00,4f,00,77,00,6e,00,65,00,72,00,73,00,68,00,69,00,70,00,\
      50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,4c,\
      00,6f,00,61,00,64,00,44,00,72,00,69,00,76,00,65,00,72,00,50,00,72,00,69,00,\
      76,00,69,00,6c,00,65,00,67,00,65,00,00,00,00,00
      “FailureActions”=hex:84,03,00,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
      00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver\Enum]
      “0”=”Root\\LEGACY_MSISERVER\\0000″
      “Count”=dword:00000001
      “NextInstance”=dword:00000001
  3. Click File > Save as. As the name of file enter repair.reg and set Save as type to All Files and click Save.
    Windows could not start the Windows Installer Service on local computer
  4. Close Notepad.
  5. Locate the repair.reg file, right click it and choose Run as administrator.
  6. If prompted, click Yes.

After you’ve added repair.reg to the registry, try to install the problematic application again.


Solution 2 – Start the Windows Installer Service manually

If you’re having Windows Installer Service could not be accessed error, you might want to try starting the Windows Installer Service manually. To do that, you need to follow these steps:

  1. Press Windows Key + X and choose Command Prompt (Admin) from the menu.
    Windows Installer not working Windows 10
  2. Once Command Prompt opens, enter net start MSIServer and press Enter to run it.
    cmd-start-msiserver

In order to check if the Windows Installer Service is running, you need to do the following:

  1. Press Windows Key + S and enter Services. Select Services from the list of results.
  2. When Services window opens, locate Windows Installer service and double click it.
  3. Check the Service Status in order to see if the Windows Installer service is running.
  4. If the service isn’t running, click the Start button to start it.

Solution 3 – Uninstall the older version of the program you wish to install

If you already have the older version of the program you want to install on your computer, we advise you to remove that version from your PC before trying to install the newer version. This is a simple solution, but it might work for you, so be sure to try it out.


Solution 4 – Re-register Microsoft Installer Service

Sometimes you can fix Windows Installer Service could not be accessed error by re-registering the Microsoft Installer Service. To do that, follow these steps:

  1. Press Windows Key + X and select Command Prompt from the menu.
  2. If you own 64-bit version of Windows enter the following lines and press Enter after each line:
    • %windir%\system32\msiexec.exe /unregister
    • %windir%\system32\msiexec.exe /regserver
    • %windir%\syswow64\msiexec.exe /unregister
    • %windir%\syswow64\msiexec.exe /regserver

After you’ve entered all the lines, close Command Prompt and restart your computer.

If you own 32-bit version of Windows 10, you need to enter the following commands:

  • msiexec /unregister
  • msiexec /regserver

After you’ve entered them, close Command Prompt and restart your computer.


Solution 5 – Use regsvr32 command

In order to use this command, you’ll need to start Command Prompt as administrator. We explained how to do that in several solutions above, so make sure you check it out. Once the Command Prompt starts, enter regsvr32 c:\windows\system32\msi and press Enter to run it. Once you’ve run the command, close the Command Prompt and try to install the problematic application again.

If you’re still having issues on your PC or you simply want to avoid them for the future, we recommend you to download this tool to fix various PC problems, such as file loss, malware and hardware failure. It will also optimize your PC for maximum performance.


Solution 6 – Use uninstaller software

If you can’t remove a certain application due to Windows Installer Service could not be accessed error message, you might be able to solve the problem simply by using an uninstaller software. In case you’re not familiar, uninstaller software is an application that can remove any application from your PC.

In addition to removing applications, these tools will also remove all files and registry entries associated with the application you want to remove.

If you’re looking for uninstaller software, you might want to try Revo Uninstaller and IOBit Uninstaller. All these tools are simple to use, and they can remove any application from your PC, so we encourage you to try them out.


Solution 7 – Use SFC and DISM commands

If you’re getting Windows Installer Service could not be accessed error message, the problem might be caused by file corruption. Sometimes your Windows installation can become corrupted and that can cause this error to appear. To fix the problem, some users are suggesting to repair your installation by using an SFC scan. To do that, follow these steps:

  1. Press Windows Key + X and choose Command Prompt (Admin) from the menu. If Command Prompt isn’t available, you can also use PowerShell (Admin).
  2. When Command Prompt starts, enter sfc /scannow and press Enter to run it.
    Windows Installer Service could not be accessed error message when installing application
  3. SFC scan will now start. Keep in mind that this can take about 15 minutes, so don’t interrupt it.

Once the scan is finished, check if the problem still persists. If the issue is still present, or if you were unable to run SFC scan, you might have to use DISM scan instead. To do that, follow these steps:

  1. Start Command Prompt as administrator.
  2. When Command Prompt starts, run DISM /Online /Cleanup-Image /RestoreHealth command.
    Windows could not start the Windows Installer Service on local computer
  3. The scanning process will now start. Keep in mind that this process can take about 20 minutes or more, so don’t interfere with it.

Once the scan is done, check if the issue still persists. If you were unable to run SFC scan before, or if SFC scan was unable to fix the problem, repeat it again and check if that solves the issue.


Solution 8 – Install Windows Installer Redistributable

Windows Installer Service could not be accessed error message can prevent you from installing new applications, but if you’re having this problem, you might be able to fix it by installing Windows Installer Redistributable.

Several users reported that they fixed the problem by downloading Windows Installer Redistributable and installing it. This is a simple solution that worked for many users, so you might want to try it out.


Solution 9 – Delete the duplicated msiexec file

According to users, you might encounter Windows Installer Service could not be accessed error message if you have a second msiexec file on your PC. Sometimes your PC can create a copy of this file and that can lead to this and many other problems.

To check your msiexec file, you need to do the following:

  1. Go to C:\Windows\System32 directory.
  2. Look for msiexec.exe. Now look for another msiexec file. This file will be 0KB in size and it won’t have a .exe extension.
  3. Rename the duplicated msiexec file to msiexec.old.

After doing that, you just need to go to the Services window and restart Windows Installer service.


Solution 10 – Change Remote Procedure Call service settings

Several users reported that Remote Procedure Call service can lead to Windows Installer Service could not be accessed error. If you’re having this problem, you might be able to fix it simply by changing the settings of Remote Call Procedure service. To do that, follow these steps:

  1. Open Services window and double click Remote Procedure Call (RPC) service.
    Windows Installer Service could not be accessed error 1719
  2. Now navigate to Log on tab and select Log on as Local System Account and check Allow this service to interact with the desktop check box.
  3. Save changes and restart your PC.

Check if the problem still persists. If the issue reappears, repeat the same steps but this time select This account in Log on tab. Click the Browse button and choose Network Service from the list. Save changes and check if that solves the issue.

Windows Installer Service could not be accessed error message can create a lot of problems, but we hope that some of our solutions were helpful to you.


Editor’s Note: This post was originally published in May 2016 and has been since completely revamped and updated for freshness, accuracy, and comprehensiveness.


READ ALSO:

Next up

These features are out for good with Windows 10 version 1809

iamsovy@gmail.com' By: Sovan Mandal
2 minute read

Microsoft is all set to launch its next big update, Windows 10 version 1809 in October. While that should be a nice piece of news […]

Continue Reading

Windows 10 18H2 builds no longer receive new features

By: Matthew Adams
3 minute read

The Windows 10 October 2018 Update (otherwise 18H2) rollout might now be two to three weeks away. For the last few months, new build previews […]

Continue Reading

Windows 7 KB4457139 makes it easier to upgrade to Windows 10

By: Madeleine Dean
2 minute read

Microsoft released a new Windows 7 update to the general public. Update KB4457139 is actually a preview of the upcoming monthly rollup update and allows users […]

Continue Reading

Discussions