Error: 0x80073712 when installing KB 2919355

That's awesome it worked without any hiccups =] This just adds more absurdity to the KB2919355 update... Microsoft still doesn't know why thousands have had issues where others have had no issue, why a failed update should cause this level of system file corruption, why once the corruption occurs dism still won't fix component store corruption with the /source flag, and now this.  It's just odd and extremely perplexing.

For example, when I did my repair install, I installed all the updates up until 2919355, created a manual restore point, then attempted 2919355 four times throughout the day and it failed every time and caused file corruption again.  I went through this for several days, trying different ways, and doing a system restore countless times to before the 2919355 update and still couldn't figure it out.  I then tried installing the 5 included updates via their standalone installers, which went fine, got to the actual 2919355 installer and it failed numerous times more.  Tried it via windows update with the standalones installed, failed three times.  

By this time, I was incredibly frustrated and decided I was going to perform another repair install, and the "wait..." step was taking over an hour and thought it had frozen, so I go to restart the computer and it has "update then restart" and I was like "huh..." checked windows update and low and behold 2919355 was half way through installing.  I had a hunch, so I force closed the 8.1 installer and within seconds windows update returned a failed update attempt.  I rebooted the installer and my update went through.  Like I said... perplexing.

I don't have enough technical knowledge to know how to figure out what the installer was doing during the "wait..." screen, and if anyone does know, please let me know as I'm curious to see why that allows for the install of KB2919355.

"A repair installDID FIX***my problem.***After doing the repair install, WU installed 47 updates; after a reboot, it did an 800MB 2919355 with no issues. I'm fully patched now."

You're an anomaly then, as every other user who's done a repair install and posted about it, including myself, was still unable to update.  

I also thought from your post a bit ago that you were using the 8.1 installer to enable the install through windows update.  

All the repair install does is clear the component store corruption... it does not hasn't allowed for the install of KB2919355, it will still fail and will cause corruption again if it isn't run alongside the 8.1 installer. Running the 8.1 installer, then running windows update about 5 minutes after the "wait..." screen begins will allow for the install of 2919355... it is has been the actions of the installer that allows for the KB2919355 install, not the repair install.

EDIT: If you didn't run WU alongside the 8.1 installer, would you please list out the steps you took starting from when you logged back in after the repair install? Thanks :D  Also, after re-reading this i thought it came across a bit snarky, which wasn't my intent at all and apologize if it did to you as well.

I feel lucky then! This has been such a nightmare -- and I should probably do a /scanhealth to see if I now have corruption! Will do and report back...

Anyway, I didn't do the "alongside installer update" you've given instructions for. MS Sent me install media for Windows 8.1, one 64bit and one 32bit disk. No DVD drive on this Asus so I copied the contents to a thumb drive, then that to the desktop. Ran the repair install, it took about an hour.

Turned off auto update until MS called back. (Which was unnecessary as it turns out). All he did was log in to my computer, run Windows Update, it installed 47 updates, about 800MB. Rebooted, ran WU again  (the desktop version though I doubt that matters) and it reported needing one update, 29193555, 800MB. Ran the update and no problems, it actually completed and rebooted without issues. Now I'm current on updates and 8.1 Update 1 is installed.

I asked the tech if doing a repair install was the known fix, he said yes he'd fixed many systems that way. But who's to say...They always tell ya what you want hear.

I was a bit perplexed about that as well since an install is point and click... unless you're using deployment tools, the only customization that can be done via the installer is disk partitioning and installing RAID drivers.

It's as if moderators live in a fantasy world and refuse to pay attention to what the facts are and listen to only what Microsoft tells them.