• Main Menu
  • How to Solve “Windows Installer Service Could not be Accessed”

    Windows Installer is a very important component of all Windows operating systems. It installs, uninstalls, and supports applications and software. If the Windows Installer is corrupted or the service stops for an unknown reason, an error message comes up. The error message typically appears as: “The Windows Installer Service could not be accessed. This can occur if Windows is running in safe mode or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.”

    The error message may happen when Windows XP is in Normal mode and the Windows Installer Service in Windows XP is damaged or unregistered. It can also occur if the default authentication level is set to None in the DCOM permissions and the default Impersonation level is on Anonymous. The error might also occur if the Windows Installer is attempting to access a folder or registry key that the system account does not have Full permission to access, but this occurrence is only NTFS-specific.

    Methods Used to Fix “Windows Installer Service Could not be Accessed”

    There are five specific methods used to fix the “Windows Installer Service Could Not Be Accessed” error message. The method to use depends on the specific issue. Before using these methods, verify that the service pack is installed. For Windows 2000, SP2 should be installed. For Windows NT 4.0, SP6 should be installed. The methods may not be effective if the appropriate service pack is not installed. Below is a list and description of the five methods used to fix the error message.


    Method 1: Unregister and Re-register the Windows Installer


    1. Click Start then Run. Type MSIEXEC /UNREGISTER and click OK. It may look like nothing happens at this stage.
    2. Click Start then Run. Type MSIEXEC /REGSERVER then click OK. It still may look like nothing happens or an hourglass may appear.
    3. The method is complete. Attempt to use the Windows Installer application again.


    Method 2: Verify the DCOM Permissions


    1. Click Start then Run. Type dcomcnfg and click OK.
    2. Go to the Default Properties tab. Click Connect in the Default Authentication Level list. Click Identify and click OK in the Default Impersonation Level list.
    3. Click Start then Run. Type explorer /select, %windir%\system32\msisip.dll and click OK.
    4. Rename the Msisip.dll file to Msisip.old.
    5. Reinstall the Windows 2000 Service Pack 3.


    Method 3: Give Full Control Permission to the SYSTEM Account


    1. Start Windows Explorer. Right click the computer’s root hard drive. Click Properties.
    2. Click the Security tab then Add.
    3. Click the SYSTEM account in the Select Users, Computers, or Groups dialog box. Click Add then OK.
    4. Click to select the Full Control check box under Allow then click OK.
    5. Click the TEMP folder and confirm that the SYSTEM account has full control.


    Important Note for Methods 4 and 5


    Methods 4 and 5 both entail using the registry. It is extremely important to back up the registry before completing these methods because there is a possibility that all files will be deleted when modifying the registry. If the registry is backed up, then the files will be safe in case an error occurs.


    Follow these steps to back up and restore the Windows registry:


    1. Click Start then Run. Type regedit into the Open box. Click OK.
    2. Click on this registry hive: HKEY_CLASSES_ROOT.
    3. Click Permissions in the Edit menu.
    4. Add SYSTEM to the Group or User Names list if it is not listed already then click Add.
    5. Verify that the local computer name is in the From this Location box.
    6. In the Enter the Object Names to Select box, type in system. Click OK.
    7. In the Group or User Names list, click SYSTEM.
    8. Under Allow in the Permissions for SYSTEM box, select the Full Control check box.
    9. Click Apply, click OK, and Exit the Registry Editor.


    Method 4: Verify the Registry Permissions


    1. Click Start then Run and type Regedt32.
    2. Follow these steps for each of the registry hives:

    a. Select the hive.

    b. For Windows 2000 and Windows NT 4, click Permissions in the Security menu. For Windows XP, click Permissions in the Edit menu.

    1. Confirm that the SYSTEM account has been added and that the account has Full control. If the SYSTEM account does not have Full control, add the SYSTEM account with Full control.


    Method 5: Fix the Broken Security Key for the MsiServer Service


    1. Start up the computer with Windows 2000.
    2. Click Start then Run and type regedit.exe.
    3. Rename the key below to Old_Security: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\Security
    4. Restart the computer.
    5. Run Instmsiw.exe for installer 2.0 again.



    Got Something To Say:

    Your email address will not be published. Required fields are marked *

    1. frederik

      18 June, 2016 at 2:02 am

      I just suggest to try “Long Path Tool” program

    2. Error 628

      20 March, 2012 at 1:11 pm

      While solving this issue error 628 pops up due to problems with your dial-up internet connection. But i fixed it by performing the following tasks:

      Contact ISP to Check the Phone Line
      Upgrade the Network Driver
      Repair your Network Configurations
      Reinstall Modem Device
      Disable the Firewall Protection

    Windows Errors
    175 queries in 0.616 seconds.