KB2918614 breaks Windows Installer Service

Anonymous
2014-08-17T15:30:13+00:00

I didnt know where best to post a bug report about KB2918614.

This is for Windows 8.1 Pro

It appears on August 13 I received KB2918614 and immediately after I began having trouble with certain MSI installations, especially those that required any version of Visual C++ Redistributable to be installed.

Now, of course I have most of those already installed, but the install process of many programs runs those redistributables before the actual install runs.  It would always give me the error of "key not valid for use in specified state" and exit with a 1603 event.

I didnt know what caused the problem at the time and went through many troubleshooting steps including sfc/scannow, registry modifications (which have all been switched back to their original values), and attempts at re-installing the Windows Installer Service for Windows 8.1 (5.0) which apparently does not have its own redistributable install file.

Eventually I determined that I received a large number of updates on 8/13, so I removed them all.  This immediately fixed my problem.

As I didnt know if that was a fluke and I didnt know which specific update caused the problem, on reboot they all re-installed.

The problem returned as soon as I started back into windows.

I went through each of the knowledgebase articles and located KB2918614 as being the only one that modifies the MSI Windows installer service files.

I have now removed and hidden this update.

I wanted to notify Microsoft of this issue but did not know the best method to do so, so I am posting it in the Microsoft community in the event another user has the same problem as I did in order to work around it.

Windows for home | Previous Windows versions | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

105 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-09-10T00:50:02+00:00
    1. I'm also getting a Windows Cryptographic Service Provider reported an error message trying to sign Adobe Acrobat pdf files: "Keyset does not exist". Error code 2148073494.

    That's the sort of detail I would use ProcMon to supplement as needed.

    BTW the code is different:  0x80090016

    Otherwise you can guess at a possible resolution

    http://www.eventid.net/display-eventid-36870-source-Schannel-eventno-1099-phase-1.htm

    (BING search for

        (80090016 OR 0x80090016) site:support.microsoft.com

    )

    Good thing BING ignored my site: specification.   ; )

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-11T06:10:06+00:00

    From what I understand,

    With KB2918614, MS have apparently tried to fix something in the Windows Installer Service.

    New stuff:

    i. They are creating a file by name "SourceHash{PRODUCT-GUID}" under %windir%\Windows\Installer. This is done for every product installed on the machine(with KB2918614 already installed).

    ii. SECREPAIR- They are computing 'Stored Hash Value' and 'Current Hash' for a given MSI.

    1. And, in this comparison, for some reason, these mismatch! (Found these in the MSI verbose logs).
    2. Once this fails, it looks for
      • Machine policy value 'AlwaysInstallElevated'
      • User policy value 'AlwaysInstallElevated'
    3. Now, if you are running a silent install "qn", this error is thrown: MSI_LUA: Elevation prompt disabled for silent installs.
    4. Removing silent install cmdline option for msiexec- ex., "qr" or "qb", will throw a UAC prompt. (which most likely will not be the expected behavior).

    Additional Info:

    My MSI is ivkoded through a bootstrapper exe. But, it doesn't really matter. Even a manual call to msiexec through cmd line behaves the same way.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-11T09:52:05+00:00

    Groan....  what on earth is going on at Microsoft??? I have two copies of Windows 7 installed on different machines (one is Win32 and the other is Win64). This morning they both did automatic updates. The Win32 box seemed to go smoothly - but after re-booting the Win64 machine, my entire desktop was missing and  I got a message saying "Failed to connect to the System Event service. This will prevent a standard user from logging on".

    To my relief, a power-down and power-up seems to have solved the problem - but this really isn't the standard of service I expect from Microsoft.

    Have you guys lost some software testers recently?? If so...  GET THEM BACK !!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-09-11T13:37:26+00:00

     after re-booting the Win64 machine, my entire desktop was missing

    Is that the symptom that others are seeing which made them press Ctrl-Alt-Delete to get into Task Manager?  I still don't know whether explorer.exe is running then or not?  Any more clues in the Event log?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-09-12T08:14:27+00:00

    Is that the symptom that others are seeing which made them press Ctrl-Alt-Delete to get into Task Manager?  I still don't know whether explorer.exe is running then or not?  Any more clues in the Event log?

    By the next reboot it seemed to have fixed itself but I could post some log entries if I knew where to look for them. Where can I find the relevant log? I'll look to see if there's anything in it from around that time.

    P.S. Explorer was running in my case. I could see my taskbar at the bottom of the screen but my desktop had no wallpaper (completely black) and no icons.

    Was this answer helpful?

    0 comments