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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-09-04T13:05:29+00:00

    What is the error you get when this happens and what behavior do you experience, e.g., won't install at all, fsios part way through? Does every computer fail with the same error? Have you tried running the update with a clean bout, do you get the same failure or a different one? It is curious why some many of the computers are failing 100% of the time but the update doesnt effect every pc elsewhere

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-09-04T05:52:11+00:00

    I've also encountered this error on Windows 7 SP1 and Windows 8.1 Pro

    For me the error appeared when attempting to install Adobe Shockwave 12.1.3.153 via MSI.

    All the machines I tried the install on that had this patch installed failed, while a system that did not have that patch installed it without issue. After removing the patch from an affected system the install runs fine.

    The EXE based installer for Shockwave did not display this issue.

    I've set the update to Remove on my WSUS server, and intend to do the same at work once I verify the problem exists there as well.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-09-03T06:20:25+00:00

    My system is Windows 7 Home Premium 32-Bit.

    I have exactly the same problems with installing *.msi installation files after updating windows.

    So I uninstalled the update KB2918614 and the Windows Installer works fine again.

    Now I have to handle my updates manually to prevent the KB2918614 update.

    I hope Microsoft will fix this problem.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-08-30T03:47:14+00:00

     Error:-2146893813

    Converting to Hex would probably provide a better search result:

    http://social.technet.microsoft.com/wiki/contents/articles/15260.windows-update-agent-error-codes.aspx

    (BING search for

        (0x8009000B OR 8009000B) "Installer service"

    )

    <quote>

    0x8009000B -2146893813 NTE_Bad_Key_State

    </quote>

    Hardly more informative!

    The good news may be that this symptom may be fixable.  The bad I don't know how to apply this information to your case:

    http://social.technet.microsoft.com/Forums/sqlserver/en-US/d7aba2a0-e81e-48ce-b0d5-c181251de74c/key-not-valid-for-use-in-specified-state-with-an-exception?forum=sqlreportingservices

    (BING search for

        (0x8009000B OR 8009000B) NTE_Bad_Key_State  site:microsoft.com (MVP OR MSFT)

    )

    FYI

    Robert Aldwinckle

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2014-08-29T14:52:09+00:00

    Which log is that in?

    Was this answer helpful?

    0 comments