Error 1719

Windows Installer Service Unavailable: Fix in 5 Minutes

Windows Errors Beginner 👁 7 views 📅 Jun 28, 2026

Windows Installer won't start. This fix restarts the service and registers the installer DLL. Works on Windows 10 and 11.

Quick answer: Open Command Prompt as admin and run msiexec /unregister then msiexec /regserver. Reboot. That's it.

What's going on?

Windows Installer is the service that handles .msi files — think installing Office, printer drivers, or security updates. When it's unavailable, you'll see "Error 1719: Windows Installer Service could not be accessed." This usually happens after a Windows update screws up the registry, or if a malware scan deleted some files. I've seen it most often right after a major Windows 11 feature update (like 22H2 or 23H2). The service is still there, it's just not registered correctly.

Before you try anything else: check if the Windows Installer service is even running. Press Win + R, type services.msc, hit Enter. Find "Windows Installer" in the list. If it's not running, click "Start" and set Startup type to "Manual" — but honestly, half the time it's already running and still broken. So skip that and go straight to the real fix below.

Fix it: Step-by-step

  1. Open Command Prompt as administrator. Click Start, type cmd, right-click "Command Prompt", choose "Run as administrator." You'll get a UAC prompt — click Yes.
    After this step: A black window with a blinking cursor will show up. That's where you type commands.
  2. Stop the Windows Installer service. Type: net stop msiserver and press Enter.
    After this step: You'll see "The Windows Installer service is stopping." Then "The Windows Installer service was stopped successfully." If it says "not started," that's fine — move on.
  3. Unregister the installer. Type: msiexec /unregister and press Enter.
    After this step: You won't see any message. The cursor just drops to a new line. That means it worked. If you get an error like "This version of Windows does not support..." — don't panic, just keep going.
  4. Register it again. Type: msiexec /regserver and press Enter.
    After this step: Same thing — no message. It just works silently. That's normal.
  5. Start the service. Type: net start msiserver and press Enter.
    After this step: You'll see "The Windows Installer service is starting." Then "The Windows Installer service was started successfully."
  6. Reboot your computer. Don't skip this. Click Start > Power > Restart.
    After this step: Your computer will restart. Log back in. Now try installing your .msi file again.

That's usually all it takes. I've fixed dozens of machines with these four commands. But if it still says "unavailable" after reboot, read on.

Alternative fixes when the main one fails

1. Re-register Windows Installer using the full path

Sometimes the msiexec command doesn't find the right file. Use the exact path:

%windir%\system32\msiexec.exe /unregister
%windir%\system32\msiexec.exe /regserver

Type these one at a time in the same admin Command Prompt. Then restart the service and reboot.

2. Check for corrupted system files

If the service still won't start, Windows might have deeper file corruption. Run these in admin Command Prompt:

sfc /scannow

This scans all protected system files. It takes 10-15 minutes. If it finds problems it can't fix, run the System File Checker with DISM:

DISM /Online /Cleanup-Image /RestoreHealth

DISM downloads fresh system files from Windows Update. You need an internet connection. After both finish, reboot and try the msiexec commands again.

3. Clean boot to rule out interference

Antivirus software — especially McAfee or Norton — sometimes blocks the Windows Installer service. Boot into a clean state:

  • Press Win + R, type msconfig, hit Enter.
  • Go to the "Services" tab, check "Hide all Microsoft services", then click "Disable all".
  • Go to the "Startup" tab, click "Open Task Manager". Disable everything in the list.
  • Click OK and restart.

After restart, try installing again. If it works, one of the disabled services was the problem. Re-enable them one by one to find the culprit.

Prevention tip

This error loves to show up after a Windows Feature Update. So before you install the next big update (like 24H2 or whatever they call it), manually stop the Windows Installer service: open admin Command Prompt and run net stop msiserver. Then run the update. After the update finishes, run net start msiserver. That keeps the service registered cleanly. Saves you from having to mess with /regserver later.

Also — and this is important — don't let CCleaner or similar "registry cleaners" touch anything related to Windows Installer. I've seen those tools delete registration entries they shouldn't. Stick to manual fixes like the one above. It's faster and safer.

Was this solution helpful?