Why Can’t I Access the Windows Installer Service and How Can I Fix It?
Why Can’t I Access the Windows Installer Service and How Can I Fix It?
4 Answers

Understanding and Fixing the “Windows Installer Service Could Not Be Accessed” Error
Ever tried to install or uninstall a program on your Windows computer and hit the frustrating “Windows Installer Service could not be accessed” error? Annoying, right? This issue can seriously mess up your software installation and removal plans. Let’s break down why this happens and how you can fix it.
Why You Might See the “Windows Installer Service Could Not Be Accessed” Error
Windows Installer Service Not Running
The Windows Installer Service could be stopped for various reasons—system crashes, sudden shutdowns, or other software conflicts. When it’s not running, you’re bound to see this error.
Service Disabled or Set to Manual
Sometimes, the service might be disabled or set to manual start, needing a manual push to get going. This can be due to user error or some particular software settings.
Windows Installer Not Properly Installed or Damaged
If the Windows Installer itself is corrupted or not installed correctly, it won’t be able to do its job. This can stem from incomplete installs, software conflicts, or even malware attacks messing with your system files.
System File Corruption
System file corruption can throw a wrench in the works. Causes could range from power outages and improper shutdowns to software installation failures and malware infections.
Permission Issues
Sometimes, it’s a simple case of not having the right permissions. If your user account lacks admin privileges or file permissions are screwed up, you might face this error.
How to Resolve the “Windows Installer Service Could Not Be Accessed” Error
Method 1: Start the Windows Installer Service Manually
- First up, press Windows + R keys together to open the Run dialog box.
- Type services.msc and hit Enter to open the Services window.
- Find the Windows Installer service, double-click it to open its properties.
- In the General tab, click Start. If it’s already running, try restarting it by hitting Stop and then Start again.
- Once it’s up and running, click OK to close everything.
- Give your software installation or uninstallation another go.
Method 2: Use Command Prompt to Start the Windows Installer Service
- Press Windows + R keys to open the Run box.
- Type cmd and press CTRL + SHIFT + ENTER to run Command Prompt as an admin.
- In Command Prompt, type net start MSIServer and hit Enter to start the service.
- Close Command Prompt, then try installing or uninstalling your software again.
Method 3: Check and Tweak Service Startup Type
- Follow steps 1-3 of Method 1 to open the Windows Installer service properties.
- In the General tab, look for the Startup type dropdown.
- If it’s set to Disabled, switch it to Automatic. If it’s on Manual, you might want to go with Automatic too.
- Click Apply and make sure the service is running by hitting Start.
- Hit OK and try your software operation again.
Method 4: Repair the Windows Installer Component
- Grab your Windows installation disc or find the installation files.
- Hit Windows + R to open the Run dialog box.
- Type msiexec /unregister and press Enter.
- Then type msiexec /regserver and hit Enter to re-register the Windows Installer service.
- Restart your computer right after.
- Give the software installation or uninstallation another shot.
Method 5: Run the System File Checker (SFC) Tool
- Press Windows + R to open the Run dialog box.
- Type cmd and press CTRL + SHIFT + ENTER to run Command Prompt as admin.
- In Command Prompt, type sfc /scannow and hit Enter.
- Let the System File Checker do its thing. It might take a while.
- Restart your computer once it’s done.
- Try the software installation or uninstallation again to see if it worked.
Method 6: Check User Permissions and File/Folder Permissions
- Make sure you’re using an admin account. If not, switch to one and try again.
- Right-click the installer file or program folder, and select Properties.
- Head to the Security tab.
- Check your user account’s permissions. Click Edit if you need to tweak them. Ensure your account has full control.
- Confirm changes and close the Properties window.
- Give the installation or uninstallation another try.
Wrapping Up
Dealing with the “Windows Installer Service could not be accessed” error is a hassle, for sure. But if you follow these steps, you’ll hopefully get it sorted and get back to adding or removing software like a pro. Still having trouble? It might be time to call in the tech experts for some advanced troubleshooting.

Running into the “Windows Installer Service could not be accessed” error? Don’t worry; it’s a pretty common hiccup on Windows systems, whether you’re on Windows 10, 11, or even older versions like XP. This pesky message usually means the Installer service isn’t running, isn’t registered right, or there are tricky permission roadblocks. Let’s dive into how you can sort this out.
What’s Going On?
This error usually pops up for a few reasons like:
- The Service is Sleeping: Sometimes, the installer service just takes a nap or is turned off completely.
- Registration Snafu: The installer might not have its paperwork in order with Windows.
- Permission Slip Issues: The SYSTEM account might be missing a permission slip to access necessary files.
- File Funkiness: Sometimes the files that run the installer are corrupted or just aren’t the right ones.
Steps to Troubleshoot
Step 1: Is the Windows Installer Service Awake?
First things first, let’s check if the service is even on:
- Hit
Win + R
, typeservices.msc
, and smack Enter. - Hunt down “Windows Installer” in the list.
- If it’s not doing its thing, right-click on it and hit “Start.”
If it’s already running, maybe just give it a little nudge by restarting it.
Step 2: Give the Installer a Makeover (Re-register)
Let’s make sure the installer service is officially on the books:
- Open a Command Prompt with admin powers.
- Type
cmd
in the search, right-click, and choose “Run as administrator.”
- Type
- Type these commands one by one:
msiexec /unregister
msiexec /regserver
Step 3: Permissions, Permissions, Permissions
Make sure the SYSTEM account’s got the right permissions:
- Head to
C:\Windows\System32
. - Right-click
msiexec.exe
, choose Properties, tap the Security tab. - Click Edit and make sure SYSTEM’s got Full Control.
Also, give the registry permissions a once-over:
- Hit
Win + R
, typeregedit
, and press Enter. - Find your way to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer
. - Right-click MSIServer, choose Permissions, and ensure SYSTEM has Full Control.
Step 4: DCOM Configuration Tango
Bad settings here can mess you up:
- Press
Win + R
, typedcomcnfg
, and hit Enter. - In Component Services, expand the menus to “Computers,” right-click “My Computer,” and go to Properties.
- Under Default Properties, make sure:
- Default Authentication Level is Connect.
- Default Impersonation Level is Identify.
Step 5: SFC and DISM to the Rescue
Corrupted files are a pain. Let’s fix them:
- Command Prompt again, as an admin.
- Type:
sfc /scannow
- Once that’s done, try:
DISM /Online /Cleanup-Image /RestoreHealth
Step 6: Identity Crisis with Msiexec.exe?
If you’ve got a bunch of dodgy msiexec.exe files hanging around:
- Back to
C:\Windows\System32
. - If you see duplicate
msiexec
files (maybe without extensions), rename those suckers (like tomsiexec.old
). - Give your computer a reboot for good measure.
With these moves, you should be well on your way to clearing up the “Windows Installer Service could not be accessed” error. Just take it step by step—get that service running, make sure it’s registered, sort out any permission craziness, tweak DCOM settings if they’re off, and keep those system files in check. You can do this!

Windows Installer Service is like the big boss when it comes to managing how software gets installed, updated, or tossed off your Windows PC. And when this service capriciously decides not to cooperate, it throws up the error \’Windows Installer Service Could Not Be Accessed\’, which leaves you stranded when trying to install or uninstall software. This problem usually pops up due to service quirks, messed up system files, or some pesky permission issues.
Main Causes & Fixes
1. Service Disabled or Not Running
The Gist: Sometimes the Windows Installer service (msiserver) plays hide and seek—either it\’s disabled or just refuses to run.
Fixes:
- Try Restarting the Service:
- Hit up Services.msc (just press
Win + R
, type inservices.msc
and boom, you\’re there). - Find Windows Installer, right-click on it, then go to Properties.
- Switch Startup type to Automatic, and smash that Start button to fire up the service.
- Hit up Services.msc (just press
- If You\’re Handy with Command Line:
- Launch an elevated Command Prompt (in less geeky terms, just run it as admin).
- Type in:
msiexec /unregserver msiexec /regserver
- Give your system a reboot to seal the deal.
2. Permission Issues
The Gist: Sometimes the permissions get all bungled up for the user or the DCOM settings are not on speaking terms.
Fixes:
- Run as Administrator: Make sure you\’re playing the boss and running install files or commands like
regsvr32 msi.dll
as admin. - Tweak Registry Permissions:
- Swing by
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MSIServer
in Registry Editor (regedit
). - Give the MSIServer key a right-click, pick Permissions, then give Full Control to the Administrators group.
- Swing by
3. Corrupted Windows Installer Files
The Gist: The files that make stuff happen like msiexec.exe
or related DLL files take the off-road and get wrecked.
Fixes:
- Re-register Important DLLs:
- Get an elevated Command Prompt rolling, and type in:
regsvr32 msi.dll
- Give your system a nice restart.
- Get an elevated Command Prompt rolling, and type in:
- Reinstall Windows Installer:
- Secure the latest Windows Installer version from good ol\’ Microsoft’s official hangout.
- Pop in the update and let your system hit the reboot button.
4. WOW64 Registry Conflict
The Gist: Incorrect registry entries in the 32-bit compatibility layer, common on those snazzy 64-bit systems.
The Fix:
- Fire up Registry Editor and head to:
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\MSIServer\\WOW64
. - Change the WOW64 setting from 1 to 0, and shoot to restart the service.
5. System File Corruption
The Gist: Important files like Msiexec.exe
just aren\’t what they used to be—damaged or corrupted.
Fixes:
- Hit up System File Checker:
- Launch an elevated Command Prompt, and type in:
sfc /scannow
- Let your computer wave goodbye with a reboot afterwards.
- Launch an elevated Command Prompt, and type in:
- Manually Swap Files:
- Look for
Msiexec.exe
inC:\\Windows\\System32
—if it\’s gone AWOL, fetch it from a backup or trusty installation media.
- Look for
6. Safe Mode or Third-Party Conflicts
The Gist: In Safe Mode or when antivirus tools get cheeky—they sometimes block the service.
Fixes:
- Get back to Normal Mode (Safe Mode doesn’t cut it when it comes to installers).
- Try disabling antivirus/firewall or any software acting up temporarily.
Deep Dive Troubleshooting
- Clear Orphaned Entries: Dust off those troublesome installer remnants with tools like Windows Installer Cleanup Utility.
- System Restore/Repair Install: When you\’ve tried everything else, give it a shot—restore to a previous happy place or go for a Windows upgrade.
If you work through these fixes, there’s a good chance that pesky error will bow out. But if it\’s being especially stubborn, don’t hesitate to dive into Microsoft\’s official support docs or jump into some community discussions to see what other folks have tried.

So, you’ve bumped into the ‘Windows Installer Service could not be accessed’ error, huh? That’s a real roadblock when you’re trying to install or update software. Let’s take a look at some down-to-earth fixes that should help you out:
1. Restart the Windows Installer Service:
- Hit Win + R to pop open the Run box.
- Type
services.msc
and press Enter. - Scroll around the Services window till you find ‘Windows Installer’ and give it a double click.
- If you see that the service isn’t running, hit ‘Start’. If it’s already on, click ‘Restart’.
- Make sure the Startup type is set to ‘Manual’.
- Tap ‘Apply’ and then ‘OK’.
2. Re-register the Windows Installer Service:
- Press Win + X and choose ‘Command Prompt (Admin)’ or ‘Windows PowerShell (Admin)’.
- Type these commands and make sure to hit Enter after each one:
msiexec /unregister
msiexec /regserver
3. Check for System Corruption:
- Open Command Prompt with admin privileges.
- Type
sfc /scannow
and let’s see what pops up. - Let the System File Checker do its thing and fix any corrupted files it finds.
4. Update Windows:
- Head over to Settings > Update & Security > Windows Update.
- Hit ‘Check for updates’ and get any updates that are up for grabs.
5. Modify Registry Settings (Advanced):
Be careful here; tweaking your registry can lead to system issues if you don’t handle it right.
- Press Win + R, type
regedit
, and Enter. - Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer
. - Look at the ‘ImagePath’ and make sure it says:
C:\Windows\System32\msiexec.exe /V
6. Use the Microsoft Program Install and Uninstall Troubleshooter:
- Download and fire up the troubleshooter straight from the Microsoft website.
- Just follow the steps they give you to sniff out and fix common installer issues.
These tips should steer you clear of that pesky ‘Windows Installer Service could not be accessed’ glitch. If you’re still having trouble, don’t hesitate to reach out to Microsoft Support or a savvy techie for a little extra help.