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-10-16T09:23:52+00:00

    "The profile for the user is a temporary profile" error when you install

    a MSI package in Windows:

    http://support.microsoft.com/kb/3000988

    See if this fixes your issue please?

    Could you please provide the KB ID of this Windows Update.

    Thanks.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-10-16T09:45:19+00:00

    Automatic Updates just gets worse by the week. Read here what happened to me this morning - on 2 different PCs (from different manufacturers and with different hardware). Whoever's in charge of Automatic Updates (and whoever's testing them) should be thoroughly ashamed of themselves. If I was running Microsoft I'd sack them.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-10-16T13:50:02+00:00

    I'm sorry I'm not following your question?  KB 2918614 needs a hotfix of KB3000988 as noted above.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-10-17T09:01:08+00:00

    Oops. Missed that. Thanks.

    Just wanted to check if the update is marked 'Important' or 'Optional'.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-10-22T17:05:55+00:00

    **Workaround 2:**Whitelisting.

    Only if you trust the application that it is always digitally signed and doesn't contain anything malicious(even in the future).

    Step 1: Enable Whitelisting

    Under Key “HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer”, create a DWORD: “SecureRepairPolicy” and set its Value to 2.

    Step 2: Add the application to the whitelist

    Create a new key “SecureRepairWhitelist” under "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer” and create StringValues with the product codes(Including flower brackets {}) of the product.

    Sadly though, both these workarounds need admin privileges!

    I had previously been blocked from installing the Java JDK, with the "SECREPAIR: Crypt Provider not initialized. Error:997" error (I/O overlap message shown).

    I tried this (registry fix, listed above) with the Java SE Development Kit 7 Update 71 (64-bit) installer, and it worked. The GUID that I included in the registry was the same one that it had been generating as "SourceHash{64A3A4F4-B792-11D6-A78A-00B0D0170710}" in the C:\Windows\Installer folder.

    Other background:-

    • restoring to a restore point before the updates installed didn't work
    • uninstalling the  KB2918614 fix via "Installed Updates" also didn't work -- and, as mentioned by others, even after KB2918614  was uninstalled, the SourceHash{GUID} files are still generated during installation of (some?) MSIs.
    • I deleted my C:\Users\CScholt\AppData\Roaming\Microsoft\Crypto\RSA folder (wisdom would suggest perhaps renaming, or movingit elsewhere instead, though).
    • I had installed the MS Hotfix KB3000988 (and that itself didn't help -- after installing that, I still couldn't complete the JDK installation... it was the registry mod that 'fixed' it).

    Thank you for sharing.

    Was this answer helpful?

    0 comments