Windows Installer error 1601: service cannot be accessed

Affected products and symptoms

Product

Windows Installer

Versions and conditions

Windows 11 (confirm the edition and hardware requirements for the feature)

Error codes and identifiers

1601

Symptoms

• Windows Installer error 1601: service cannot be accessed.
• The same condition can persist after a retry or restart.

Causes and conditions

Windows Installer may be disabled or damaged, Windows may be in Safe Mode, or installer registration may have a problem.

Before you start

• Save open documents and allow time for a Windows restart if required.
• Run administrative actions only on a personally managed PC or with administrator approval.
• Save the diagnostic command output so the before and after states can be compared.

Step-by-step instructions

1. 01

   Check normal startup and service state

   #

   The standard Windows Installer may be unavailable in Safe Mode. Return to a normal Windows session, search Start for Services and locate Windows Installer. A stopped service can start on demand, so Stopped alone is not evidence of failure.

2. 02

   Check the state with Get-Service

   #

   Confirm Windows is running normally rather than in Safe Mode, then record the Windows Installer service state and startup type.

   Command or pathCopy

   Get-Service msiserver

3. 03

   Repair through the supported path

   #

   In services.msc, confirm Windows Installer is not Disabled. If it is stopped, launch the approved MSI and confirm that the service starts on demand.

   Command or pathCopy

   Start-Service msiserver

4. 04

   Inspect any service start error

   #

   If Windows Installer is Disabled, check organizational policy. On a personal PC, if manual start fails, record its error number and matching Event Viewer entries. Do not recreate service registration or system files with unofficial scripts; retest using an approved installer.

5. 05

   Verify under the same conditions

   #

   This is an installation command for PowerShell. Replace the MSI path before running it and check the completion screen. If it fails, inspect package-install.log in your temporary folder and remove personal information before sharing the log with support.

   Command or pathCopy

   msiexec /i "C:\path\package.msi" /L*v "$env:TEMP\package-install.log"

Check the result

• The feature starts, connects, or completes without the original error.
• The verification command reports the expected enabled, healthy, or connected state.
• The result remains correct after a Windows restart and no new matching critical event appears.

If the problem continues

• If the same code persists, provide the full message, Windows build, command output, and occurrence time to the PC administrator or Microsoft Support.
• If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.

Scope of this guide

Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.

Frequently asked questions

Official sources and dates

• MsiExec.exe and InstMsi.exe error messages ↗

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

• Resolve Windows Installer error 1618: another installation is running
• WSL 2 error 0x80370102 prevents a distribution from starting
• Restore the WSL optional component when error 0x8007019e appears
• WSL alone cannot resolve names while a VPN is connected
• Hyper-V is missing from Windows Features or cannot be enabled
• WSL 2 or Hyper-V cannot run inside a Hyper-V virtual machine