KB2919355 (Windows 8.1 Update) Fails (800f0092 and 80073712) on Windows 8.1 Pro w Media Center

Throwing my hat in.  4 Windows 8.1 systems.  3 are Surface Pro2's, native windows 8.1.  The other is a W8 laptop (OEM) with Media Center upgraded to 8.1 months ago.  All working previously. Problem free.   

I'm an IT professional.  Have tried all the fixes here (except reset and clean install).  Can't spend any more time on this.  Others pay for my time.  I can't give it to MS for free.  Would rather not start over.  I've seen MS through worse and like everything else this too will pass.  Its a shame because these mistakes gravely affect customer satisfaction and opinion.  I was an early adopter of W8 and have already deployed many 2012 Servers.  I like metro.  I'm hoping that patience will win the day.         

I managed to upgrade 3 systems via Windows Update automatically with no issues.

I also managed to install the update in 2 offline VMs (one 32 Bit and the other 64 Bit) and one offline system which had only installation with the Windows 8.1 .iso and the generic product key. These had the following installed:

64 Bit

• Windows 8.1 Update KB2919442
• Windows 8.1 Update 1 KB2919355

32 Bit

• Windows 8.1 Update KB2919442
• Windows 8.1 Update 1 KB2919355

There were no issues.

Were any of your systems Windows 8.0 and upgraded via the Store?

For e.g. I have here Win 8.1 from MSDN .iso - doesn't work.

Unfortunately I have no system to look up, but maybe you can look at times in this directory, and tell me how the content is there (only on x64 Systems):

%windir%\WinSxS\amd64_microsoft-windows-help-privstatement_r_31bf3856ad364e35_6.3.9600.17031_none_57e5a2f32866988f

I have a RTF in that folder:

Name: privacy

Date Modified: 01/02/2014 05:59

Type: Rich Text Format

Size: 107 KB

Opening the document in Word 2010 its not in English. From Google Translate its in Malay. This is an EN-GB install.

No hidden items.

Thank you.

I have the same file.

I really don't understand why the update stops there.

One thing which might be worth doing is create a new "local" user account and once the account is created ensure it has administrator privileges.

Log into this local account and uninstall KB2919442 if its installed, the reset and then try manually installing the following updates with the local administrator account:

• Windows 8.1 Update KB2919442
• Windows 8.1 Update 1 KB2919355

When I select that update KB2919442 I do not get the option to uninstall it like any of the others in the list.

Okay in that case can you do a system restore to a point before KB2919442 was installed?

[1] No to the Norton or McAffee.

[2] Yes, I run two antimalware products. Symantec, because I needed an AV that worked with Windows Server (Defender doesn't

@Michael Cherry only:

A1. You may not have installed a Norton or a McAfee application since you've owned the computer, but if Vista came OEM-preinstalled on the computer, chances are a Norton or a McAfee free-trial was preinstalled. The "leftovers" may be your troublemaker here.

A2. What's Windows Server got to do with it and what version of Windows Server is it?

• Reminder: This is a Consumer-specific support forum (not that you'd necessarily be any better off in the Win8.1 IT Pro forums at this point).

3. I believe you mentioned "Tech Support" assistance in a previous reply. Was that (legit) Microsoft Support or...?
4. KB2919442 has been installed, correct?
5. Is KB2936068, KB2922229, KB2894853 and/or KB2942844 also listed in Installed Updates?
6. Have you tried installing KB2919355 (via Windows Update, not manually) after restarting the computer in "Clean Boot troubleshooting" mode? cf. http://support.microsoft.com/kb/929135

Note: Remain in clean boot mode only long enough to test - reboot into normal (Windows) mode ASAP.

7. Was Win8.1 Preview (beta) installed on the computer as suggested by this previous thread of yours?

Status report:

Patch Tuesday day two and counting.  Post release status report.  33 days to get everyone updated by May 13, 2014:

I have opened about 28 cases so far from folks that have volunteered from this thread (thank you to all that volunteered).  We are still in investigation mode.  At this time I would advise everyone to hang tight and let Microsoft support do their thing and investigate. 

In the meantime you might want to also deal with another patching issue - that of the OpenSSL bug called Heartbleed.  Please be advised that Heartbleed/OpenSSL does not impact this forum or any other Microsoft web property.  But you may wish to use sites like LastPass - http://www.cnet.com/news/lastpass-checks-sites-for-heartbleed-automatically/ to check web sites that are scrambling to patch for the Heartbleed bug and thus may recommend you change your password.

My sincere thanks - and apologies as a Microsoft shareholder - to all impacted by this. 

This patching public service announcement has been brought to you by the Letter P.

(tribute to Sesame Street for anyone who grew up with that)