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

Hello, M W 67

     I gather from the discussion you've begun: "If your MS 8.1 Update 1 Failed...please post here", and from your posts to this thread, to the one I linked as containing a possible solution, to "Have Any Microsoft Moderators contacted Microsoft about the bug in Windows 8.1 Update?", & to others (I must be a glutton for punishment, as I've read every post on those threads - as of this writing, 230+ pages in those threads/discussions alone, not to mention the many, many other pages in similar threads here & in other forums), that you've basically tried everything various folks have posted to resolve this problem with your machine, including what's outlined in the Windows Club article "Fix: Windows 8.1 Update fails to install" (I presume, as the title is so similar to that for your discussion) and the new support article "Install the latest Windows 8.1 Update".  I can only imagine your frustration with this problem, which seems to be triggered by a variety of different things (various VPN and Proxy implementations, "in-box" applications, injudicious use of Piriform's CCleaner & registry cleaners, insufficient size of the hidden system reserved partition, lack of prerequisites, host bus adaptors, usb hubs, and various other hardware, aggressive interaction by anti-virus solutions with such a complex kernel update, the lack of a C:\ProgramData\Microsoft\Windows\Start Menu\Programs\System Tools folder, the use of Classic Shell, and more), mostly on OEM builds (for instance, I've had no problems installing the 5-in-1 2919355 WUpD on fresh builds constructed from a bloat-free wim). 

     With that last in mind, and given the reliability history of Microsoft's documentation (very high) and the ensured-compatibility (forwards and backwards) history of even the largest vendors large and small (not so high), the fact that so many of these triggers are being found to be so OEM-dependent seemingly points to a lack of adherence to Microsoft guidelines (although considering the recent reliability history for WUpD, I'm far from ruling out Redmond's desire to unify various devices onto a single platform, as expressed with Windows 8, as being the root cause of the problem, despite the burgeoning evidence that the former consideration appears @ this point to be the most likely source); given also the virtually-unique nature of each user's computer after the first installation of just about any program (whether 3rd-party or made in Redmond), I highly suspect that there will be no Fixit or other "one size fits all" solution forthcoming, and that we'll all be resolving this on a case-by-case basis.  I do expect that the 13 May deadline will likely be extended - but I've been wrong before, dadgummit...

     One thing I didn't seem to see in your previous posts, however, was exactly what error/stop code (or codes) WUpD is returning for you.  Might I be so bold as to inquire what you're seeing?

I've been seeing numerous codes actually.  I can't recall them all.  It seems once you fix one error another one occurs.  Someone from escalated MS support is going to call me Monday and hopefully he'll be able to fix it although at this point I probably will need to do an "inplace upgrade."  I don't have any installation media so I am going to ask for an 8.1 iso preferably with the installed update and a license key.  It's the least they owe me.  I've already had two remote sessions with 2 separate techs and uploaded my diagnostic logs some time ago.  Microsoft should have developed three separate builds for 8.1...one for mobile, one for tablets, and one for desktop/laptop.  It's plain to see that this experiment is a miserable failure.

Hello, Chris LaMantia

    I hope you'll overlook any obtuseness on my part if I've missed a previous post of yours in the various threads that already answers what I'm about to ask (I'm honestly struggling just a tad to remember all the posts in the 300 or so pages I've viewed in the Answers Community & other forums/sites about this recalcitrant update over the last month - and an "ol' fogey" like me should probably be glad he can remember how to turn a computer on, much less repair it!), but I'd like to ask a few questions about your corrupted component store and your WUpD problems, if you don't mind. ("WUpD" is my colloquialism for Windows UpDate; I pronounce it "whupped" - southern slang for "whipped" - in commemoration of the many times it's tried to do just that to me in the last 20 years.)

    Are you saying that manually invoking Inbox Corruption Repair (i.e., running "C:\Windows\System32>DISM.exe /Online /Cleanup-image /Restorehealth" with elevated privileges) fails to correct the corruption of your WinSXS ("component store") folder as reported in

C:\Windows\Logs\CBS\CBS.txt?  And if so, have you tried this in Windows 8 Safe mode after cleaning out the winSXS folder  (i.e., running "C:\Windows\System32>DISM.exe /online /cleanup-image /startcomponentcleanup /resetbase" with elevated privileges), rebooting, and then cleaning out your disk with cleanmgr (i.e., running "C:\Windows\System32>cleanmgr.exe" with elevated privileges), followed by another reboot, into Safe Mode? (Please note that the post by Thenrik I mentioned earlier in this thread, along with feedback in both the The HotFix Share and Shavlik's Patch Management List as well as my own testing all appear to indicate that running the latter command without the "/resetbase" switch may actually be causing component store corruption if the msu package from a failed instance of KB2919355 isn't first removed by running the command "C:\Windows|System32>DISM.exe /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14- again,

with elevated privileges; the command argument should be DISM.exe /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~x86~~6.3.1.14for 32-bit versions of Windows 8.1)

     If the answer to all is yes, have you tried this with any and all anti-virus programs - including any pre-installed trial versions that came with the computer (as well as any previously-used/now-uninstalled programs, even if they were installed when the computer was running a previous-version operating system) - not only uninstalled (temporarily, just for purposes of applying the WUpD) but actually wiped clean from the computer?  There are usually a good deal of  "left-behinds" not removed by the uninstallers of previously-used A-V programs; for this reason, most A-V providers have created "removal tools" that will wipe away any problematic vestiges of both previous installations and pre-loaded trial A-V programs as well - pre-loaded A-V software can cause problems even if it has never been activated. If you have now or have had any programs of either type (previously-installed, or pre-loaded "trial"), I'd suggest removing all traces of them first by using the correct removal tool; a good resource to obtain a given removal tool is Wiki Author, Community Moderator, and MVP Stephen Boots' List of anti-malware product removal tools.

     And finally, if none of the above is applicable, did you originally install Windows 8.1 via the Windows Store, and thus have no installation media (DVD, thumb drive)?  If so, did you do so from Windows 8?  If both these are true, do you have a copy of your Windows 8 product key?

I followed the previous simple advice and it worked!  Simply copy and paste the following code at the command prompt, then install the individual files.

1. Run CMD as administrator (Go to start screen, all apps, seach CMD, right-click and select run as administrator).
2. Enter: dism /online /remove-package /packagename:Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14
3. When step 2 has completed, enter: dism /online /cleanup-image /startcomponentcleanup
4. Make sure KB2919442 is installed.

Then in order:

KB2919355

KB2932046

KB2937592

KB2938439

KB2934018