I'm not sure I understand what you mean by /fvomus method?
Can I open a support case for you (email susan-at-msmvps.com (change the -at- to@) as without a case whatever you think is broken won't be fixed.
KB2918614 breaks Windows Installer Service
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
105 answers
Sort by: Newest
-
Anonymous
2014-11-12T08:16:50+00:00 -
Anonymous
2014-11-12T08:01:57+00:00 This issue is still present today (12 Nov.) in minor upgrades using the /fvomus method (http://msdn.microsoft.com/en-us/library/aa367575(v=vs.85).aspx).
I can't seem to find anything indicating that Microsoft considers this an issue, but it's a rather serious problem for us. Is Microsoft dropping support for upgrading applications in this way?
-
Anonymous
2014-11-05T16:58:48+00:00 If you have to remove 2918614 and didn't reinstall it after this issue, you are still unprotected from a security issue.
If you can't install it, can you let me know?
-
Anonymous
2014-11-05T16:57:10+00:00 Whom did you contact in order to open a support case. If IT pro, they will ask for a credit card but they will not charge it.
-
Anonymous
2014-11-05T15:59:08+00:00 Thank You, I finally got around to doing the uninstall and IT does require a reboot after the uninstall of the update. After that everything works again.