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 No comments

105 answers

Sort by: Most helpful
  1. Anonymous
    2014-09-16T07:00:35+00:00

    C:\Users\xxx\AppData\Roaming\Microsoft\Crypto\RSA

    Delete content in the above location, and the problem will be resolved.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-09-12T16:12:07+00:00

    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.

    Except for the wallpaper factor that doesn't sound like the same symptom.  That sounds just like your Display configuration (aka Project) is set to Extend and you are starting in Desktop (or you have Show Taskbar on all displays checked) but as I indicated somehow your main monitor is being used as your secondary.  Press Win-P, CursorUp, Enter to change that case.

    In fact, though, I suppose this same (hypothetical) quirk could explain others' blank screen symptoms.  E.g. their default would be to start in the Start Screen but their Taskbar option would be to have it only on the main monitor (which they can't see or which would normally be hidden by the Start Screen.)  But then with the new "MUF elements anywhere" change that occurred in W8.1 they should be able to see those MUF bars regardless of the monitor which was current, e.g. Win-C for the Charms bar, etc.  Then again, maybe not being able to do that would be consistent with your lack of wallpaper symptom.  E.g. another sign that explorer.exe is broken and needs to be restarted at least.

    BTW others with a blank screen are claiming no keyboard workarounds are possible but do say they observe the Network icon (probably from the Lock screen) "flashing" on the left and then the screen can show mouse movement but no input of any kind is possible.  Please say if that Network icon is appearing at all for your case(s).  That would be a clue for how far things are progressing before the blockage.

    FWIW I don't know what event log will be involved with this but I imagine that it would help to have some extra tracing enabled for whatever it is.  For a guess try opening  WindowsUIImmersive  (under Applications and Services logs) and try enabling its Operational log (for a start).  I'll turn that on too and see when it starts recording after a boot.  I suppose results will also depend on your Navigation options regarding Start Screen.  E.g. I have  When I sign in or close all apps on a screen, go to the desktop instead of Start  checked so possibly might not see any immediate tracing in there at all after a boot.  TBD.

    HTH

    Robert


    Was this answer helpful?

    0 comments No comments
  3. 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 No 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 No comments
  5. 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 No comments