sodcalculator

10 Tech How-To

Fix Windows Installer Service Error

Guide 10-20803 · Updated · Step by step

If you see “The Windows Installer Service could not be accessed” when trying to install or uninstall a program, the fix is usually to restart the Windows Installer service, re-register the installer engine, or repair corrupted registry permissions. This guide walks through the most reliable fixes in order, from quick checks to more thorough repairs.

What Causes This Error?

The Windows Installer service (also called msiserver) is a background component that manages the installation, repair, and removal of programs packaged as .msi or .msp files. When the service cannot be accessed, Windows cannot run any installer that relies on it. Common triggers include:

  • The service is disabled or set to manual when it should be running.
  • Third-party security software blocks the service from starting.
  • Windows Update or a system restore left the service in a broken state.
  • Registry permissions for the installer keys are corrupted or changed.
  • Malware or a failed uninstall left the service’s files missing or unregistered.

This error can appear on any recent Windows version, including Windows 10 and Windows 11, and often happens after a major update or when a user has disabled services to “speed up” their PC.

Restart the Windows Installer Service

The simplest fix is to ensure the service is running. If it’s stopped or disabled, you can start it manually.

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll to Windows Installer in the list.
  3. Right-click it and choose Start if it’s not running. If it’s already running, choose Restart.
  4. Double-click the service, set Startup type to Manual (the default), and click OK.

If the service fails to start, note the error message. A common one is “Error 5: Access is denied,” which points to a permissions problem rather than a simple disabled service.

Re-register the Windows Installer Engine

If the service starts but the error persists, the installer’s DLL files may be unregistered. Re-registering them is a safe, built-in fix that works on Windows 10 and 11.

  1. Open Command Prompt as administrator (search “cmd”, right-click, “Run as administrator”).
  2. Type the following commands one at a time, pressing Enter after each:
msiexec /unregister
msiexec /register

The first command unregisters the installer, and the second re-registers it. You won’t see a confirmation message; the command just returns to the prompt. After both run, restart your PC and try the installation again.

Check the Service’s Dependencies

Windows Installer depends on the Remote Procedure Call (RPC) service. If RPC is disabled or broken, the installer will fail even if it’s set to run. To check:

  1. Open services.msc again.
  2. Find Remote Procedure Call (RPC) and DCOM Server Process Launcher.
  3. Both should be set to Automatic and running.
  4. If either is stopped, right-click and start it, then set the startup type to Automatic.

Also check Windows Management Instrumentation (WMI) and Windows Update services, as they sometimes interact with installer operations. A quick way to see all dependencies is to open the Windows Installer service properties and look at the “Dependencies” tab.

Repair Corrupted Registry Permissions

When the installer service cannot be accessed even after starting, the registry keys that control it may have incorrect permissions. This often happens after a botched uninstall or a security tool changed ACLs. The safest repair is to use the built-in SubInACL tool, though it’s no longer officially distributed. Instead, you can manually reset the keys using the regedit or use a PowerShell script. A simpler approach that works for many users is to run the System File Checker and DISM:

  1. Open Command Prompt as administrator.
  2. Run sfc /scannow and wait for it to finish.
  3. Then run DISM /Online /Cleanup-Image /RestoreHealth.
  4. Restart your PC.

These commands repair corrupted system files, including the installer service files. If the error is purely a registry permission issue, you may need to use the Microsoft’s Fix it tool or manually take ownership of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer key and grant SYSTEM and Administrators full control. Only do this if you’re comfortable with regedit, and always back up the registry first.

When to Use System Restore or In-Place Upgrade

If the above steps don’t work, you can try rolling back to a previous restore point. System Restore reverts system files and registry settings to an earlier state without affecting your personal files. Search for “Create a restore point”, open the System Protection tab, and click System Restore. Choose a point from before the error started.

If no restore point exists, an in-place upgrade repair install is the next step. This reinstalls Windows while keeping your files, settings, and installed apps. Download the Windows 11 or Windows 10 installation media from Microsoft’s official site, run the setup, and choose “Keep personal files and apps”. This often fixes deep service corruption without a full reset.

Preventing Future Installer Errors

Once resolved, you can reduce the chance of it happening again by:

  • Keeping Windows Update enabled and running regularly.
  • Avoiding “debloat” scripts that disable services like Windows Installer.
  • Installing software only from trusted sources that use proper MSI packages.
  • Using the official “Programs and Features” uninstaller rather than deleting files manually.

Also, if you use a third-party cleanup tool, check its settings to ensure it doesn’t remove MSI cache files or registry entries. Some aggressive cleaners have been known to break the installer service.

Frequently Asked Questions

Why does the error appear when I install any program?

Because nearly all modern Windows installers rely on the Windows Installer service. If the service is broken, every MSI-based installation will fail with the same message. The fixes above target the service itself, so they apply to all programs.

Can I fix this without admin rights?

No. Starting or re-registering the service requires administrator privileges. If you’re on a work or school PC, contact your IT department. If you’re the administrator, make sure you run Command Prompt as administrator, not just as a standard user.

Will this delete my files?

No. All the fixes here only affect system services and registry entries. Your personal files, documents, and installed programs remain untouched. The in-place upgrade also keeps your files and apps, though it’s always wise to back up important data before any repair.

What if the service is missing from services.msc?

That’s rare but possible after a severe corruption. You can reinstall the service by running msiexec /unregister and msiexec /register as administrator. If that doesn’t recreate it, a repair install or system restore is the most reliable path.

Is this error caused by a virus?

Sometimes malware can disable the installer service to prevent you from removing it. If you’ve recently noticed other odd behavior, run a full antivirus scan using Windows Defender or a reputable third-party tool before attempting repairs. But the error is more commonly caused by a disabled service or a failed update.

How long does the fix take?

The service restart and re-registration take under five minutes. The SFC/DISM scans can take 15-30 minutes. A system restore or in-place upgrade can take 30-60 minutes. Most users resolve the issue with the first two steps.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →