Error: 0x80073712 when installing KB 2919355

As I also speculated about that "corruption" what about then finding out which package they came from and then removing only it (not the composite one)?   Then either installing just it or, even better, using the /source: and /limitaccess  operands to get it repaired without another download?

I like this idea a lot. If DISM can detect "corruption" then it's got to know what file that "corruption" is in. Why not replace just that file? Of course you'd still probably have to have some kind of image/DVD to pull that file from. Again, a hard copy of a "Clean" version would be useful, I'd think.

Jim

The files should be on the root.  Run the setup from within windows.  Depending on if you have a UEFI setup with a bios locked key will determine if you'll be required to input a product key. If you are required to, the 8.1 Pro generic key is XHQ8NC3MCJRQXB6WCHYGC9WKB.  If you have a different version of windows, google "<windows edition> generic product key".  If you have to use a generic key to install, you'll need to manually activate windows through PC Settings with your activation product key.

Select the option to keep everything the same [paraphrased], which should be the 1st option out of three and should be located at the top of the window.  Let the install do it's thing and be patient as it can take a while.  I've had it take as little as 30 - 60 min, but when I did it yesterday to fix the same problem you're having, it took a few hours.  You're not going to be able to use your pc during this time.

 

I put the files from the 8.1 DVD onto my desktop, ran the setup using the included key and doing the "keep everything the same" option.

After it finally reinstalled, I turned off auto updates. Update history is blank but I'd wager the corruption is still there. MS Tech support is supposed to call on Friday, $20 says he just attempts to install 2919355, has it fail, and then tells me to just reinstall windows 8.1 completely from the media he sent.

I will then say that's no an acceptable solution.

One thing that concerns me, you say your procedure cleans up the corruption, but 2919355 still won't install after that - but does the attempt to install it corrupt the component store again?

Ok, although I’m not sure a typical computer user is going to be able do all of this, and I’m not saying your directions are not clear, just overwhelming for most. If I follow you correctly, your method provided is basically to clean up the component store and then attempt the KB2919355 installation. I agree a component store cleanup is needed. Do you know if it will work if parts of KB2919355 are already installed? I thought I read somewhere that using the DISM after the subfile 2919355 is already installed actually can cause additional corruption.

Personally, I'd like to see MS just make available a DVD or download with Windows 8.1 Update 1 on itwith a self repair installer included. I'd even be willing to pay maybe $10.00 (I know, it should be free after all of the time people have put in so far) for it just so I can have a "clean" version for the next fiasco that will probably take place when they release the rumored Update 2. If all of the corrupted files are not fixed, even on those machines that had successful installs, these issues are only going to compound.

Of course, maybe Disney would let TRON come out of retirement and fix everything ;-)

Unfortunately, a typical computer user isn't going to have a choice...  If dism /restorehealth fails repeatedly, the only way for end users to solve this is by an install repair since /restorehealth is the only option to repair component store corruption and is the only reason for it's existence.  Since windows xp, a repair install has been a common tool, but which for reasons escape me, microsoft prefers to tell end users to essentially fumigate their home because they saw a lone ant on their porch by informing them to refresh or reset... both of which creates an even bigger problem since the computer then has no installed applications (or oem drivers in the case of a reset) and they're unable to revert to their state prior to the refresh/reset.  (The only way a refresh should ever be used, in my opinion, is only after an end user customizes their system the way they want it, creates a wim of the system, and replaces that wim with the refresh wim.)

Microsoft has already made it very clear they will withhold all patches for windows 8/8.1 users who do not update to KB2919355 (deadline was this or last week, but was extended to the first week of June)... and even if microsoft comes up with a fix for the KB2919355 problems that plague thousands of users,  they're not going to offer advice on how to repair the massive corruption their mucked up update caused, which leaves the end user with a crippled system that has corruption of vital system files.  

I'm not an expert and am an experienced windows user at best, which is why I wrote and posted that main post on numerous threads related to KB2919355 update.  I did my best to write it in a simplistic, yet straightforward way, and am more than happy to take the time and help anyone whom may become overwhelmed by the amount of information contained therein... but someone needed to provide all the included information (which is all material combined from a plethora of threads on different forums I came across, and I wish I could notate who I got the information from, but I never planned on writing the post I had and only did so after becoming increasingly irritated by the same cookie cutter response from Microsoft Moderators who were not only giving steps that would never solve the issue, but providing steps that would make the situation far worse) in a condensed format to counteract the ridiculous and incompetent responses from Microsoft Moderators.

"If I follow you correctly, your method provided is basically to clean up the component store and then attempt the KB2919355 installation."

Yes and no...

• The 5 steps under "*First"*are to fix the component store, however if either of the first two steps presents errors after running either twice, then the end user will need to do an install repair by upgrading to the current version of windows the end user is running.
• Attempting the KB2919355 update via Windows update will cause corruption again, and will more likely than not require another install repair.  I can't 100% attest to this as the repair install I did took more than 4 hours, when it normally should only take 30 - 60 minutes at most, and I simply didn't have more time to devout to repair installs. Considering though that I had no component store corruption prior to attempting the update through windows update (I had just run /restorehealth and /scannow the prior day with no corruption on either), and massive corruption afterwards, i believe it would be factual to say attempting another update via windows update would result in the same result.

"Do you know if it will work if parts of KB2919355 are already installed?"

From my experience on my own PC, yes.  I downloaded the standalone installers for all updates included in KB2919355, and not knowing in which order Microsoft installed them, I chose smallest file size to largest which would end with the standalone of KB2919355.  Every update installed fine, except the standalone of KB2919355, which still fails (and has failed 4 separate times this far).  I ran /startcomponent cleanup and it completes successfully. as does /restorehealth, however /scannow returns errors as if there's component store corruption, even though /restorehealth finishes successfully with no errors... still a bit baffled by this and plan to do more research in the coming days.

"I thought I read somewhere that using the DISM after the subfile 2919355 is already installed actually can cause additional corruption."

From my experience with my PC thus far, it appears SFC still returns a corrupted component store error even though /restorehealth finshes successfully without errors.

Anyone, especially Microsoft Moderators, are ENCOURAGED to discuss the collage of steps included in my post, as if Microsoft intends to keep it word and prevent end users not updated to KB2919355 from receiving additional patches, this causes a security risk to all users not updated.