Author Topic: Windows Installer Service could not be accessed  (Read 15194 times)

0 Members and 1 Guest are viewing this topic.

Offline Shelly300

  • Newbie
  • *
  • Join Date: Jun 2013
  • Posts: 3
  • Karma: 0
    • View Profile
Windows Installer Service could not be accessed
« on: June 25, 2013, 05:32:51 am »
I'm having trouble with the Windows Installer Service on Windows 7 Ultimate.
Was able to install MalwareBytes, CCleaner and various other programs but am unable to install XLite, Adobe Reader, AVG, and others.
The message I get is: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. That message was delivered by Adobe but the message is similar from one and all.

Things I have done already include:
  • Check that the windows installer service is running - it is
    Stop and start the service
    Stop and start the MSIServer
    Disk check
    Virus check
    CCleaner on the Registry
    Run Tweaking.com's Window Repair (all in one)
None of the above has helped.

I couldn't find a .msu for Windows 7; all I get is service pack 1 which is already installed.

I ran sfc /scannow. I did this early in the piece and did it again after all the above with the same results. It said: Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

A search of the CBS.log file showed a number of errors that I have no idea what to do about.

Here are all the errors the scan identified:

  • CBS    Failed setting restore point [HRESULT = 0x80040155 - Unknown Error]
    CBS    Exec: Begin: nested restore point - failed, ignoring and continuing. [HRESULT = 0x80040155 - Unknown Error]
    CBS    Failed to get IVssEnumMgmtObject interface. [HRESULT = 0x80040155 - Unknown Error]
    CBS    SQM: Warning: Failed to get System Restore max diff area. The data won't be available. [HRESULT = 0x80040155 - Unknown Error]
    CBS    Failed to find localized custom property bag [HRESULT = 0x80070490 - ERROR_NOT_FOUND] - this particular error is listed 5 times
    Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #330619# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xa0c8f0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[94]"\??\C:\Windows\WinSxS\amd64_angel264.inf_31bf3856ad364e35_6.1.7600.16385_none_9421cee72a5bb5c5"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa0c8d0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
    Error                 CSI    0000000c@2013/6/25:06:09:39.509 (F) d:\w7rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
    Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #330618# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
    Error                 CSI    0000000e (F) STATUS_OBJECT_NAME_NOT_FOUND #330617# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0xa0d1e8->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_angel264.inf_31bf3856ad364e35_6.1.7600.16385_none_9421cee72a5bb5c5"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
    Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #330619# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x9ecc20->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[94]"\??\C:\Windows\WinSxS\amd64_angel264.inf_31bf3856ad364e35_6.1.7600.16385_none_9421cee72a5bb5c5"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x9ecc00, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
    Error                 CSI    0000000c@2013/6/25:11:12:08.256 (F) d:\w7rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
    Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #330618# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
    Error                 CSI    0000000e (F) STATUS_OBJECT_NAME_NOT_FOUND #330617# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0x9ed518->SIL_OBJECT_ATTRIBUTES {s:40; on:"amd64_angel264.inf_31bf3856ad364e35_6.1.7600.16385_none_9421cee72a5bb5c5"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)

Is there any advice you can give me that doesn't involve a re-install of the OS?

Kind regards

Offline Willy2

  • Hero Member
  • *****
  • Join Date: Oct 2011
  • Posts: 1165
  • Karma: 18
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #1 on: June 25, 2013, 10:24:58 am »
The Service is used by the Windows installer technology. Some programs use this technology and other don't.

1. Install the latest version of Registry Backup (v1.61) and make sure it makes a copy of the registry once a day. It's also in a subfolder of where Windows Repair is installed. The Services are registered in the registry.
2. Did you run WR's reset file & reset registry permissions ?
3. Did you run WR's "Restore Important Services to default" ?

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #2 on: June 25, 2013, 07:27:57 pm »
Windows installer is MSI and I have a repair for that in my Windows repair tool, have you tried it yet?

Shane

Offline Shelly300

  • Newbie
  • *
  • Join Date: Jun 2013
  • Posts: 3
  • Karma: 0
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #3 on: June 25, 2013, 08:11:42 pm »
Thanks for your replies.

Willy2, on point 1, I have used CCleaner to do a registery backup but, as the problem is already in place, a backup can't help me now. On point's 2 and 3, yes I did.

Shane, yes I did.

I used WR tools... all of them. I did everything as instructed by your software as well as crossing my fingers and toes during the process. Your software seems like a great tool that has worked wonders for many but it said something about commenting on the forum if my problem wasn't fixed. I don't want to be the someone with the unsolved problem but here I am.

In the CBS log errors there is something called the 'localized custom property bag' - see the fifth error I have listed. I have no idea what this is but if it's missing and it's supposed to be there shouldn't I try and replace the missing something?


Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #4 on: June 26, 2013, 01:42:34 pm »
Lots of unknown errors in the log you posted. When sfc is messing up you know there is a problem that is deep.

The best thing to do would be a repair install, which would keep all your programs and settings and just get Windows reinstalled.

To do that you need a Windows 7 cd with SP1 already on it, you can grab that here
https://sites.google.com/site/linuxlablibrary/windows-iso

Then follow this guide :wink:
http://www.sevenforums.com/tutorials/3413-repair-install.html

Shane

Offline Shelly300

  • Newbie
  • *
  • Join Date: Jun 2013
  • Posts: 3
  • Karma: 0
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #5 on: June 26, 2013, 11:50:38 pm »
Thanks Shane

I will do what you have advised. It sounds like the best option.

Kind regards

Offline Rick

  • Hero Member
  • *****
  • Join Date: May 2013
  • Posts: 829
  • Karma: 2
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #6 on: June 28, 2013, 11:13:25 am »
Shane, there are several issues with this problem; I would only do a repair install too...

The other way is to create a new CBS store, it usually still does not fix any problems and reports the same errors.

could run sysinternals to see a report too to compare system files related to the missing errors.

Best solution, do a repair install

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #7 on: June 28, 2013, 12:03:32 pm »
Got a link on how to repair the CBS store by chance?

Shane

Offline Rick

  • Hero Member
  • *****
  • Join Date: May 2013
  • Posts: 829
  • Karma: 2
    • View Profile
Re: Windows Installer Service could not be accessed
« Reply #8 on: June 29, 2013, 02:25:59 am »
This is related; have a look at the next to last post in this thread. this other person that re-installs will need to do this anyway..

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/how-do-i-fix-cbs-catalog-corrupt-0x800b0100-error/fc5da114-78aa-403a-8750-8333fd7a5b56?auth=1