How to fix Windows Installer Service could not be accessed error?

"The Windows Installer Service could not be accessed" appears when a setup program asks Windows Installer to install, update or remove software and the service does not answer. Most often the service is disabled, Windows is in Safe Mode, or the service registration is broken. Check the Windows Installer service in Services first.

Facts checked on 16 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What "The Windows Installer Service could not be accessed" means

Windows Installer is the part of Windows that installs, repairs and removes programs packed as .msi files. When a setup runs, the service copies files to their folders, writes the program's registry entries and keeps track of shared components, so that a later update or uninstall knows what belongs to the program. Many .exe installers start Windows Installer too, which is why the error also appears with setups that are not .msi files.

The error means the setup program asked the service to start the job and got no connection to it. The install stops before anything is changed. Microsoft lists the message in its table of Windows Installer messages as 1719: "Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled." Registered and enabled are the two things the fixes below check.

Why the Windows Installer service cannot be accessed

Five of the eight causes below are about the service itself. From the most likely to the least likely:

How to fix the Windows Installer Service could not be accessed error

Fix 1 and Fix 2 solve the error on most PCs, because they make sure the service can start. Fix 3 and Fix 4 repair the service's registration and its registry key. Fix 5 to Fix 8 cover damaged files, other software, malware and missing updates.

Fix 1. Set the Windows Installer service to Manual and start it

3 minutesLow riskEveryone, first. Especially when the service is Disabled or a tuning tool changed your services.

A setup can only start Windows Installer when the service is allowed to run. A disabled service, often switched off by a tool that "turns off unneeded services", gives exactly this message. The service also needs Remote Procedure Call (RPC), which must be running.

1. Press Win + R, type services.msc and press Enter.
2. Click any row and press W to jump down the list. Find Windows Installer; the old guides call it Windows Installer Service.
3. Double-click Windows Installer. The General tab shows the service name msiserver.
4. If Startup type reads Disabled, choose Manual and select Apply.
5. Select Start. If the service is already running, close the window, right-click Windows Installer and select Restart.
6. Find Remote Procedure Call (RPC) in the same list and check that it reads Running and Automatic.
7. Close Services and run the setup again.

The same in a Command Prompt opened as administrator: the first command sets the startup type to Manual (demand), the second starts the service. If it is already running, Windows answers The requested service has already been started.

sc config msiserver start= demand
net start msiserver

Startup types and the PowerShell way are explained in Check and restart Windows services.

Fix 2. Restart Windows normally and turn off Safe boot

3 minutesLow riskThe screen corners say Safe Mode, the message mentions safe mode, or the PC starts in Safe Mode every time.

Safe Mode starts Windows with a minimal set of services, and the installer's own message names Safe Mode as a cause. When Safe boot stays ticked in System Configuration, for example after an old clean boot guide, every restart lands in Safe Mode again and every setup fails.

1. Press Win + R, type msconfig and press Enter.
2. Open the Boot tab and clear the Safe boot check box.
3. Open the General tab. If you are not in the middle of a clean boot test, select Normal startup.
4. Select Apply, then OK, and choose Restart.
5. After the restart, check that the screen corners no longer say Safe Mode, then run the setup again.

Fix 3. Re-register Windows Installer with msiexec /unregister and /regserver

5 minutesLow riskThe service starts, but setups still cannot reach it.

Microsoft's message asks to check that the service is properly registered. These commands remove the registration of msiexec.exe as the Windows Installer service and write it again, so that setups can find the service. A 64-bit Windows has a second copy for 32-bit setups in SysWOW64.

1. Type cmd in the search box on the taskbar.
2. Right-click Command Prompt and select Run as administrator.
3. When User Account Control asks, select Yes.
4. Type the four commands below one by one and press Enter after each. On a 32-bit Windows 10, run only the first two.
5. Restart the PC and run the setup again.

%windir%\System32\msiexec.exe /unregister
%windir%\System32\msiexec.exe /regserver
%windir%\SysWOW64\msiexec.exe /unregister
%windir%\SysWOW64\msiexec.exe /regserver

Fix 4. Check the msiserver registry key: startup value and SYSTEM permissions

10 minutesRead the warningServices cannot change the startup type of Windows Installer, the change does not stick, or Fix 3 did not help.

Services stores the startup type and the program path of Windows Installer in one registry key. If the SYSTEM account has lost its rights on that key, or the values were changed by a tool, the service cannot be set up or started, and the setup cannot reach it.

1. Press Win + R, type regedit and press Enter. Select Yes in User Account Control.
2. Paste the path below into the address bar of Registry Editor and press Enter.
3. Check the value Start: 3 means Manual and 4 means Disabled. If it reads 4, double-click it, type 3 and select OK.
4. Check that ImagePath reads %systemroot%\system32\msiexec.exe /V. If it points somewhere else, do not edit it: run Fix 5 and Fix 7.
5. Right-click the msiserver key and select Permissions.
6. Select SYSTEM in the list and check that Full Control is ticked under Allow. If not, tick it, select Apply and OK.
7. Close Registry Editor, restart the PC and repeat Fix 1.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver

Fix 5. Repair Windows Installer files with DISM and SFC

20 to 30 minutesLow riskFix 1 to Fix 4 did not help, or other Windows tools fail too.

msiexec.exe and msi.dll, the files that make up Windows Installer, are protected Windows system files. DISM repairs the store Windows takes good copies from, and SFC then replaces damaged copies, including those two.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 6. Find a program that blocks Windows Installer with a clean boot

15 to 30 minutesLow riskThe error began after you installed a security suite, an "installer protection" or a PC tuning tool.

A clean boot starts Windows with Microsoft services only. If the setup works then, a program from another maker stops it from reaching Windows Installer. Use the clean boot steps only: do not tick Safe boot, because Safe Mode itself causes this error (Fix 2).

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

   

3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

   

5. Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.

   

6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

Fix 7. Scan for malware with Microsoft Defender

15 minutes to over an hourLow riskWindows Installer is Disabled again after a restart, or security programs will not install while other setups do.

Malware can disable services or change their settings so that you cannot install a security program. A full scan with Microsoft Defender finds it without installing anything, because Defender is already part of Windows.

1. Open Windows Security. Select Start, type Windows Security and open the app.
2. Open Virus & threat protection. Select Virus & threat protection. Under Current threats you see when the last scan ran, how long it took and how many files it checked.
3. Run a quick scan. Select Quick scan. If Windows Security thinks a deeper scan is needed, it tells you when the quick scan is done.

   

4. Open Scan options. If the quick scan finds nothing and you still suspect an infection, select Scan options under Current threats.
5. Run a full scan. Select Full scan and start it. It checks every file and program on the device, so it takes much longer than a quick scan. Leave the PC on until it ends.

   

6. Or scan one folder. To check only a download or a USB drive, select Custom scan in Scan options and choose the folder. You can also right-click a file or folder in File Explorer and select Scan with Microsoft Defender. On Windows 11 you may have to select Show more options first.
7. Read Protection history. Go back to the first page of Windows Security and select Protection history. Select a card to expand it and see the details.

   

These steps were written for Windows 11 25H2 and 26H2, Windows 10 22H2. The full page with the other versions and what each result means: How to scan for malware with Microsoft Defender

Fix 8. Install pending Windows updates

10 to 30 minutesLow riskWindows Update shows Restart required or updates you have not installed yet.

Windows Installer is updated with Windows itself. An update that waits for a restart can leave its files half replaced, and installing it brings msiexec.exe and msi.dll up to date.

1. Press Win + I and open Windows Update (on Windows 10, Update & Security > Windows Update).
2. If you see Restart now, save your work and restart first.
3. Select Check for updates and install what Windows finds.
4. Open Advanced options > Optional updates and install the updates listed there as well.
5. Restart when Windows asks, then run the setup again.

If the Windows Installer Service could not be accessed error is still there

Two logs show where the install stops. Event Viewer keeps the messages of Windows Installer, and a verbose setup log shows every step of one install.

1. Right-click Start, select Event Viewer and open Windows Logs > Application.
2. Select Filter Current Log on the right, choose the event source MsiInstaller and select OK.
3. Read the newest entries from the time of the error. They name the program and the error number.
4. For a .msi file, create the folder C:\logs and run the command below in a Command Prompt opened as administrator, with the real path of your package.
5. Open install.log in Notepad and search for 1719 and Return value 3. The lines just above show which step failed.

msiexec /i "C:\path\to\setup.msi" /l*v "C:\logs\install.log"

• The log folder must exist. Windows Installer writes the log only into a folder that is already there; it does not create it.
• Every fix failed: reinstall Windows over itself and keep your files and apps. This puts back all Windows Installer files and service settings: Reinstall Windows without losing files
• Work or school PC: send the message, the time and the MsiInstaller entries to IT. Company rules can block installs on purpose, and IT can see why.
• Windows 10: support ended on 14 October 2025. Only PCs in Extended Security Updates still get fixes, so a damaged Windows 10 installer is not repaired by new updates.

How to keep the Windows Installer service working

Frequently asked questions

What does "The Windows Installer service could not be accessed" mean?

It means a setup program asked Windows Installer to install, change or remove software and could not connect to the service. Nothing was installed. Microsoft lists it as Windows Installer error 1719 and asks you to check that the service is properly registered and enabled. In practice the service is most often disabled, or Windows runs in Safe Mode. Set Windows Installer to Manual and start it in Services (Fix 1), and restart normally if you are in Safe Mode (Fix 2).

Is the fix different on Windows 11 and Windows 10?

No. The service, its name msiserver, the registry key and the commands are the same on Windows 11 and Windows 10, and so are the fixes on this page. Only the Settings pages for Windows Update have different names: on Windows 10 they sit under Update & Security. Windows 10 left support on 14 October 2025, so a damaged Windows 10 installer is not repaired by new updates unless the PC is in Extended Security Updates.

What is the Windows Installer service?

It is the Windows service that installs, maintains and removes programs that come as .msi packages, and many .exe setups use it in the background. It copies the files to their folders, creates the registry entries and keeps track of components that several programs share. Its display name is Windows Installer, its service name is msiserver, and the program behind it is msiexec.exe in C:\Windows\System32. It runs only while a setup is working.

Should the Windows Installer service be set to Automatic?

No. The correct startup type is Manual. The service starts by itself when a setup needs it and stops again when it is done, so an empty Status column is normal. Older guides advise Automatic, which is not needed and does not fix this error. The only setting that causes the error is Disabled, because then no setup can start the service. Change it back to Manual in Services (Fix 1) or set the Start value to 3 in the registry (Fix 4).

Why does only one program show the error while others install fine?

Because many installers do not use Windows Installer at all. Microsoft Store apps and setups built with other installer tools copy their files themselves, so they still work while the service is broken. Programs packed as .msi files, and .exe setups that unpack an .msi, need the service and stop with this message. If those setups fail and others work, the service is the cause, not the program. Start with Fix 1.

Can I install a program in Safe Mode?

Usually not when the setup uses Windows Installer. Safe Mode starts only a minimal set of services, and the installer message itself names Safe Mode as one cause of this error. Start Windows normally and install the program there. If the PC keeps starting in Safe Mode, Safe boot is still ticked on the Boot tab of System Configuration: clear it as shown in Fix 2 and restart.

What is error 1719 in Windows Installer?

Error 1719 is the number of this same message in Microsoft's list of Windows Installer messages: Windows Installer service could not be accessed. Larger programs often show it as Error 1719 in their own setup window or write it to their setup log. The fixes are the same as for the message without a number. Do not mix it up with system error 1719 in Windows' general error list, which is about network protocol sequences and has nothing to do with installing.

Can I download and reinstall Windows Installer?

Not as a separate download on Windows 10 and 11. Windows Installer is built into these versions, and the standalone Windows Installer packages you can still find online were made for much older Windows versions. To repair it, re-register msiexec.exe (Fix 3) and repair the system files with DISM and SFC (Fix 5). If nothing helps, reinstalling Windows over itself puts back every Windows Installer file and keeps your files and apps.

Is the Windows Installer Service could not be accessed error caused by a virus?

Usually not. Most often a tool or a setting switched the service off, or Windows is in Safe Mode. It is worth a scan when the service turns itself off again after you set it to Manual, or when only security programs refuse to install. Run a full scan with Microsoft Defender, which is already part of Windows and needs no installation (Fix 7), then set the service back to Manual.