Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 1601

Error 1601 and 1719: Windows Installer Service Could Not Be Accessed

10 min read Updated October 5, 2026 Installers, Runtimes & App Deployment

Fix it now

1601 is ERROR_INSTALL_SERVICE_FAILURE – the Windows Installer service could not be accessed – and 1719 says the same thing, asking you to verify the service is properly registered and enabled. Every MSI on the machine fails while this is true. The service is msiserver, it starts on demand rather than at boot, and it is usually disabled, misconfigured or damaged.

Run these in an elevated Command Prompt, in order; the space after start= is required

sc query msiserver
sc qc msiserver
sc config msiserver start= demand
net start msiserver
  1. Read sc qc msiserver. The binary path should point at msiexec.exe in System32 with the /V switch, the start type should be DEMAND_START, and the service should run as LocalSystem.
  2. If the start type is disabled and reverts after a reboot, a policy is setting it: run gpresult /h %USERPROFILE%\Desktop\gp.html and read the System Services section.
  3. If the service will not start at all, check the System log for a Service Control Manager entry naming the reason before you change anything.
  4. Test with a small, known-good package and /l*v logging. A quiet install – add /qn – proves whether the engine works when no interface is involved.

If you are working in Safe Mode, expect 1652 rather than 1601. Microsoft’s text is that Windows Installer is not accessible when the computer is in Safe Mode, and the documented remedy is to exit Safe Mode and try again, or to use System Restore.

If a test package installs and the service starts on demand afterwards, you are done. If the service exists and still refuses, the next section covers what each refusal means.

Why it happens

When you double-click an MSI, the copy of msiexec you launched is only half the picture. It hands the package to a second instance running as a service under the local system account, which does the privileged work. That service instance is msiserver, registered to run msiexec.exe with the /V switch. It is not started at boot; the client half starts it on demand and it stops again shortly after the transaction ends. A stopped Windows Installer service is normal, not a fault.

1601 and 1719 both come from that handover failing. If the service is disabled, the client cannot start it. If its registry entry has been damaged so the command line no longer points at a valid msiexec.exe, the Service Control Manager fails the start and records the reason in the System log as event 7000. Microsoft documents the Service Control Manager as waiting for the period set by ServicesPipeTimeout before logging 7000 or 7011, which is why a slow machine and a broken registration can look identical from the desktop.

The remaining codes narrow it usefully. 1631 is ERROR_CREATE_FAILED, “The Windows Installer service failed to start” – that is the service itself, not your access to it. 1621 is ERROR_INSTALL_UI_FAILURE, an error starting the installer’s user interface, which shows up on machines with a damaged profile or in a session that cannot display a window. And 1652 is ERROR_INSTALL_SERVICE_SAFEBOOT, which is specific and easily mistaken for corruption: the installer is simply not available in Safe Mode.

The service is disabled

You have this one if sc qc msiserver shows a start type of DISABLED, or services.msc shows Windows Installer set to Disabled.

  1. Set it correctly: sc config msiserver start= demand.
  2. Start it: net start msiserver.
  3. If it reverts after a reboot, produce a policy report with gpresult /h and look at System Services.
  4. Correct the policy at source rather than on the machine, then run gpupdate /force.

The service registration is damaged

You have this one if The service exists, fails to start, and the System log records a Service Control Manager event 7000 for Windows Installer.

  1. Read the event first; it names the underlying error and often ends the investigation there.
  2. Compare sc qc msiserver against a healthy machine: the binary path, the start type and the LocalSystem account.
  3. Repair the component store rather than the key: sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
  4. Reboot and retest with a small package.

You will find advice to run msiexec /unregister followed by msiexec /regserver. Neither switch appears in Microsoft’s documented msiexec command-line options, so treat them as legacy and undocumented rather than as the fix, and do not stop there when nothing changes.

You are trying to install in Safe Mode

You have this one if Error 1652, on a machine deliberately booted into Safe Mode to remove or repair something.

  1. Boot normally and run the install there. That is Microsoft’s documented remedy along with System Restore.
  2. Where the work genuinely has to happen in Safe Mode, look for a vendor-supplied removal tool that does not need Windows Installer.
  3. If nothing else will do, System Restore to a point before the problem is the supported route back.

Adding an MSIServer key under the SafeBoot branch to force the service to run in Safe Mode is widely circulated and is not a documented Microsoft procedure. It changes what runs in the mode people boot into precisely because they want less running.

The session cannot show the installer interface

You have this one if Error 1621 rather than 1601, often over Remote Desktop, in a service context, or on a machine with a damaged user profile.

  1. Prove the engine works with no interface: msiexec /i package.msi /qn /l*v C:\temp\quiet.log.
  2. If the quiet install succeeds, the fault is in the interactive session rather than in the installer.
  3. Test with a different user profile, or repair the one that fails.
  4. For unattended deployment, keep using the quiet switch; there is no need for an interface at all.

Full reference

What the service should look like

Property Expected value
Service name msiserver
Display name Windows Installer
Start type Demand – it is started by the client half and stops again afterwards
Account LocalSystem
Binary msiexec.exe in System32, with the /V switch

Check all five with sc qc msiserver before you touch anything. A service that is present, demand-started and running as LocalSystem, but still refuses, is a component-store problem rather than a configuration one, and the remedy is different.

The five codes, as Microsoft states them

Code Constant Message
1601 ERROR_INSTALL_SERVICE_FAILURE The Windows Installer service couldn’t be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered
1719 – The Windows Installer service could not be accessed; verify that it is properly registered and enabled
1631 ERROR_CREATE_FAILED The Windows Installer service failed to start
1621 ERROR_INSTALL_UI_FAILURE There was an error starting the Windows Installer service user interface
1652 ERROR_INSTALL_SERVICE_SAFEBOOT Windows Installer isn’t accessible when the computer is in Safe Mode. Exit Safe Mode and try again, or try using System Restore

Reading the Service Control Manager’s account of it

  1. Open Event Viewer, Windows Logs, System, and filter on Service Control Manager.
  2. Look for event 7000 at the time of the failed install. It names the service and the reason the start failed.
  3. Event 7011 is the timeout variant. Microsoft documents both as being logged after the Service Control Manager has waited for the period set by ServicesPipeTimeout.
  4. Where a machine is genuinely slow to start services, Microsoft documents creating a DWORD ServicesPipeTimeout under HKLM\SYSTEM\CurrentControlSet\Control, in milliseconds, and increasing it in small steps – while advising you to find out why it is slow rather than simply waiting longer.

Export the msiserver key before you change it. In Registry Editor select the key, choose File then Export, and keep the .reg file until the machine is installing normally again. Service keys hold the account and permission settings the operating system uses to start itself.

Repairing rather than rebuilding

  • sfc /scannow first, then DISM /Online /Cleanup-Image /RestoreHealth. Most damaged service registrations are one symptom of a damaged component store rather than an isolated deletion.
  • An in-place upgrade from current Windows installation media rebuilds the service database while keeping applications, settings and data. It is the supported fallback when DISM cannot repair the store.
  • Copying the msiserver key from another machine works only when that machine runs the same Windows version, build and architecture, and it is fragile enough to be a last resort.
  • On a managed estate with a standard build, reimaging is often quicker than any of this, and leaves a machine whose state you understand.

Deployment tools and this error

A deployment tool that reports 1601 across many machines at once is almost never seeing a coincidence of damaged registrations. Look for a policy that disables Windows Installer, for a maintenance window in which another installation holds the engine, or for the tool running the package in a context that cannot reach the service. Test one machine by hand with /l*v: if it installs interactively and fails from the tool, the difference is the account and the session, not the service.

Every code this article covers

Code What it points at Source
1601 ERROR_INSTALL_SERVICE_FAILURE: the Windows Installer service could not be accessed Microsoft Learn
1719 The same access failure phrased for the user, asking you to verify the service is properly registered and enabled Microsoft Learn
1631 ERROR_CREATE_FAILED: the Windows Installer service failed to start Microsoft Learn
1621 ERROR_INSTALL_UI_FAILURE: there was an error starting the Windows Installer service user interface Microsoft Learn
1652 ERROR_INSTALL_SERVICE_SAFEBOOT: Windows Installer is not accessible in Safe Mode; exit Safe Mode or use System Restore Microsoft Learn
Event ID 7000 System log entry from the Service Control Manager when a service fails to start; logged after the wait set by ServicesPipeTimeout, alongside 7011 for the timeout case Microsoft Learn

Confirm the fix worked

  1. sc query msiserver shows the service can be started on demand without an error.
  2. sc qc msiserver shows demand start, LocalSystem, and msiexec.exe with the /V switch.
  3. A small, known-good MSI installs with /l*v logging and completes.
  4. The System log records no new Service Control Manager 7000 entries for Windows Installer.
  5. Reboot and install something again, so you know the fix survived a restart.

Questions people ask about this

Is there anything to buy here?

No. Windows Installer is part of Windows and every step above uses built-in tools. If someone is selling you a registry cleaner to fix 1719, decline.

Why does the service keep stopping?

Because that is how it works. msiserver is a demand-start service: it starts when an installation begins and stops a short time after it finishes. A stopped state only matters if it refuses to start when asked.

Does msiexec /regserver still do anything?

Neither /regserver nor /unregister appears in Microsoft’s documented list of msiexec command-line options, so there is nothing published to rely on. Running them is unlikely to make things worse, but do not treat them as the fix, and move on to the service configuration and the component store.

Can I copy the msiserver key from another machine?

You can, provided the source machine runs the same Windows version and architecture and you export only that key. It is a reasonable last resort before an in-place upgrade, but repair the component store first.

I need to uninstall something and I am stuck in Safe Mode.

Microsoft’s documented answer is that Windows Installer is not available there: exit Safe Mode and try again, or use System Restore. Where a product genuinely cannot be removed from a normal boot, look for a vendor removal tool that does not depend on Windows Installer.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix MSI 1904 and 1920: Module Failed to Register or Service Failed to Start Free Fix Error 2502 and 2503: Called RunScript When Not Marked in Progress on Install License Error 0x80070005: Access Denied During Install When Endpoint Protection Blocks It License Error MSI 1306: The File Is in Use and Setup Cannot Replace It
โ† Back to Knowledge Base