Windows Update KB2919355

I know what you are saying, but to run KB2919355 you have to have KB2919442 installed. So if I can’t install KB2919442 there is no point of going any further.

I still think the problem lies with the difference between an 8.0 updated to 8.1 and 8.1 installed from the start. There has to be differences between the two file systems 8.1 updated and 8.1 none updated. That’s where MS slipped up; unfortunately I can’t try out the two scenarios to check my theory. The update can’t see the difference  or doesn’t check, between the two 8.1’s and that causes the file corruption.

You can install it by following my instructions, or by doing a repair install, then following the instructions.  

If you wish to carry the belief of a wait and see approach, that's entirely up to you and when you're denied access to patches that your system needs because you believe Microsoft is going to help you, you might reconsider your position.  It should be noted there are 11 patches that are currently available of which 2919355 is a prerequisite for.

Bottom Line, I've posted solutions to your specific issue on most Microsoft threads pertaining to KB2919355, and I will stop responding to your messages as it's pointless.  If you don't want to fix what's wrong in hopes that someone else will [Microsoft], then there's nothing anyone can do to help you.  Solutions to your problem exist, I've posted pages and pages of the same two solutions which will allow you to install ALL standalone updates, and then by following the instructions posted above, you can then install KB2919355.

I wish you the best, but if you're unwilling to help yourself, no one's going to help you... it's really as simple as that.

Just so you know what you're risking.... security patches are released by Microsoft once they discover vulnerabilities in Windows that can allow your system to be compromised.  Due to the nature of the beast, once a security patch is released, it immediately allows hackers to see vulnerabilities within the OS that will allow them access.  If your system is not updated with current security patches, for all intents and purposes, you're simply asking for your system to be compromised.  This is why no one should be running Windows XP still, since all patches released after 4/8 show ways to compromise XP.

I am willing to try your fix using the Windows installer trick, but am not sure what you mean by "generic product key"?

Google "generic key [followed by your version of windows]"

Due to Microsoft's licensing structure change that came with the rollout of Windows 8, generic product keys were publicized by Microsoft for Windows 8 and 8.1 installs that will be required in order to access the installer. These generic keys are freely available for all Windows 8/8.1 versions by googling them. These generic product keys are only there to gain access to the installer and once Windows is booted into, the end user will need to go to PC Settings - Activate and enter their activation keyin order to activate windows, thereby removing the watermark and allowing personalizations to become unlocked.  More likely that not, Microsoft was attempting to safeguard it's OS from KMS activators by requiring a PK before the installer allows you to install... then it backfired.  Users with valid activation keys experienced the same thing I did... upon reinstalling Windows 8 (not 8.1, but 8) on the same computer, the product key I bought from Microsoft no longer worked to get past the installer, even though it worked to activate Windows.  This is why Microsoft released generic product keys for all versions of 8/8.1 (core, pro, enterprise, etc.).

Hello Ellis,

Thank you for your response.

Please refer to suggestions from PaulSey... replied on May 15, 2014 and check if it helps.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_install/kb2919355-windows-81-update-fails-800f0092-and/4d4d23a3-695a-4bd4-b340-d2ce9c75919d

I hope this information helps.

Thank you