Error: 0x80073712 when installing KB 2919355

Component   Wow64Provider.DLL  is  not loaded

Can anybody comment on this?

Warning  DISM   DISM Provider Store: PID=... TID=... Failed to Load the provider: C:\Users......\AppData\Local\Temp\A4AF0713-E9AF-4134-BC3C-B1B1FD9977D5\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)

To your first paragraph, that is correct, but is different that the support I was referencing.  Microsoft offers free support for any patch [update] related issues [issues that arise out of the installation or failure of installation].  In other words, any user with a system unable to update to KB2919355 is able to get free support for that specific issue and MS support will remote connect to troubleshoot and provide advice.  What I've noticed however is you get a 50/50 shot of either getting a great tech support rep who is extremely helpful, or you get one that's incompetent who wastes your time and then at the end says you're s.o.l. and there's nothing they can do (unfortunately, it appears the right hand doesn't know what the left hand is doing, to quote Ms. Bradley).  Regardless if a user goes the support option or not, if dism fails when running /restorehealth, the only option to fix this is a repair install, regardless if someone chooses to get remote help from MS or not.

I appreciate you taking the time to at least attempt to read through the thread to find the tutorials, and I had meant to include earlier to start around page 9 and I apologize.  Due to that, I've copied and pasted the two tutorials below.  I ask that you read through all of it prior to partaking, as it was written and added to as more concrete information was discovered, which will allow you to have a concrete understanding of which steps apply and which don't.  I may mention this below, and if I do, I apologize... upon installing KB2919355, you may have a smaller version appear after the initial install and upon attempting to install it you will get one of two, possibly both, errors [one is 80070005, but cant recall the other] which reference an update install currently going on even though a trace of one doesn't exist.  Restart if you receive the error, and if you continue receiving it after restarting, allow your computer to remain on for a few hours here and there for about a day, restarting at random intervals, and within a few hours, windows should give you the "update then restart" option, or may simply say configuring updates when you restart or boot back up.  If it doesn't install within a day, I'd then try tutorial two, which is what I had to do after my first repair install, but not on any other ones (not sure why). Edit: I believe running the windows update cache flush may solve this, however, once you run this, you lose your entire update history. I would prefer not to lose mine, however, you may not mind at all, and if not, upon receiving the two errors, create a restore point and wipe the cache using "second".

I cannot stress the importance of running /startcomponentcleanup, /restorehealth, and /scannow options after the repair install and before running Windows Update. Forgetting to do so (as I did earlier today) will more likely than not lead to a second repair install. 

I know the following to solve all KB2919355 issues, and pasted below are two tutorials.  The first is one that was written to get rid of the component store corruption that 2919355 causes.  The second is how to get 2919355 installed after the repair install if you're still having issues and should only be used as a last resort.  

Tutorial 1

The following fixes the Component Store Corruption KB2919355 AND Windows Update causes

The following DISM commands must be given in the chronological sequential order of:

First

(Fixes Component Store Corruption; Should 1 or 2 fail with an error, rerun. If either fails a second time, you will need to do a repair install, see tutorial at bottom):

1.dism /online /cleanup-image /startcomponentcleanup

2. dism /online /cleanup-image /restorehealth

3. Restart

4. sfc /scannow

5. Restart

Second:

("Resets" Windows Update; however, if you attempt KB2919355 again through Windows Update, the same corruption will occur again)

1. Create bat and run as ADMIN:

net stop wuauserv

rmdir /s /q C:\Windows\SoftwareDistribution\DataStore

rmdir /s /q C:\Windows\SoftwareDistribution\Download

net start wuauserv

2. Restart

‪#‎ WARNING‬:

this was not a fast process... component cleanup took almost 5 hours. Prior to the above sequential steps, I did an install repair (used iso to "upgrade" Win 8.1 Pro to Win 8.1 Pro) as a last ditch effort (after half a day of researching a fix and finding none) to get rid of the corruption... it didn't solve it btw. The insane amount of time could have been due to the install repair, or it could have been because of whatever ‪#‎WindowsUpdate‬ mucked up the first time around trying to install this update (this will become known after another user affected by the corruption causingKB2919355 completes the steps).

‪#‎ ADVICE‬:

run the commands from a bat for an unattended fix. For whatever reason, if these commands are run, but not in chronological sequence, the corruption will remain.

...Now, back to the update ‪#‎Microsoft‬ mucked up (KB2919355)... it still fails after the above lol Bright side: no more corruption in Component Store =] lol

ADVICE:

Download the updates included in KB2919355 individually and install... or do as old Van Winkle did and find a tree.

***If the above fails to get rid of the Component Store Corruption (steps 1,2, or 4fail), then an install repair (upgrade to your same version of windows) will be required.  Although this repair does not eliminate the corruption, if you're unable to fix the corruption using the method above. then the install repair is replacing something that is needed to fix the corruption but which is not able to pro vide a fix on it's own. Also, download [search] "Microsoft Safety Scanner" from the Microsoft website (I apologize, as I don't remember the thread I found the link on) and run it in full mode either way.***

Tutorial for Repair Install "upgrade"

http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html

• Once KB2919355 causes corruption to the extent that /restorehealth no longer operates without errors, there is nothing further than can be done to repair the corruption, except a Repair Install.  DISM /restorehealth was designed to fix component store corruption and is the only application able to do so. Windows Update and KB2919355 causes system corruption to such an extent that using /source and pointing to the installation media or a working windows 8 installtion without corruption does nothing and /restorehealth still fails.
• Once the repair install has completed, run windows update and install the 46 (possibly more depending on configuration) updates. Restart when told to do so.  You may have to restart several times, even though Windows may not direct you to do so.  If you attempt to install additional updates, especially the KB2919355 package update, and receive an error code that is for an error resulting from updates currently being installed (or something to that effect), restart the computer.  It took 3 restarts for Windows to install the 46 updates in 3 stages.  It took an additional 2 (possibly three) restarts to install all updates within KB2919355.DO NOTuse the standalone versions once you do a repair install.  Attempt to do all via Windows Update.  If you're receiving errors other than ones that relate to Windows attempting to install additional updates or installations are in progress, etc. then attempt tutorial 2.
• Upon logging in after the Repair Install and before running Windows Update:
  • Run /startcomponentcleanup
  • restart
  • run /restorehealth
  • restart
  • run /scannow
    • If it completes with errors and directs you to the CBS log even though DISM gave no errors, check the CBS log to see if file permissions are the issue and is what is preventing SFC from accessing those files.  If this is the problem, take ownership of the files in question, and give System full permissions.  It appears the corruption can cause files to lose their ownership, preventing SFC from accessing those particular file and will through an error due to it.
  • restart

DO NOT, I REPEAT, DO NOT REFRESH/RESET YOUR PC.

DISCLAIMERMicrosoft will deny this update caused corruption within end user's systems and will blame it on everything else but components of their own OS, most especially Windows Update.  The only problem with this: thousands of users have reported massive corruption not only to the Component Store, but also within the DISM and System File Checker utilities.  Microsoft closed the two longest running threads on the corruption caused by KB2919355, one 116 pages long, the other 103... all the while telling users to run /scanhealth /restorehealth maybe a /startcomponentrepair in their somewhere, but never in the order which they must be run, or how to explain DISM /restorehealth corruption errors when being used with /source and the source was a mounted install.wim, as well as a VM win 8.1 with no corruption within it's component store.**

Tutorial 2

***KB2919355 Fix that WILL allow the install of KB2919355***

As many discoveries have been made, I discovered this accidentally. and quite by coincidence... 

In order for users, who've been plagued by errors and file corruption, to get a successful completion of KB2919355, all that's needed is to run the 8.1 upgrade installer, and when the 8.1 installer goes to the wait screen after entering the generic product key, start Windows Update for the install of KB2919355

EDIT: It appears, from the input of other users, one must FIRST install the 5 standalone updates included within the Windows Update KB2919355 package, you will then need to restart after the fifth and final standalone, then use Windows Update to install KB2919355 (do not use the standalone installer for KB2919355... use Windows Update). The steps listed below may not be needed for a successful KB2919355 issue, as although I had to do this after the first repair install I did, the second did not require it and updated flawlessly.

Steps

1. Run the Windows 8.1 installer from within Windows, as if you're going to do an install repair "upgrade".
2. Enter the generic product key, and upon clicking next, the installer will say wait...
3. Give the installer about 5 minutes, then start Windows Update (it should show the KB2919355 update), and click install.
4. Windows Update will begin downloading the update... if you have a Windows Update cache problem that causes the speed and percentage to remain at zero, don't worry about it and get the update installed first, then you can clear the cache and remove the directories afterwards.
5. The install may fail, don't worry... simply hit install again, making sure the 8.1 installer screen is still on the "wait" screen, as whatever the installer is doing during the "wait" screen is what makes the KB2919355 install possible.
6. KB2919355 should install and Windows Update should request you to restart... simply do so without cancelling the 8.1 installer.  Windows will finalize the update during the shutdown and restart processes.
7. Upon rebooting into Windows, you will have a multitude of additional updates that will need to be installed (around 10, give or take a few), and you can verify the install of KB2919355 by going to "view installed updates"

While I understand your frustration, the answers to your problem are included in this thread... please read through to find them and if you need help at that point, please post back.  

Also, KB2919355 is an update, not 8.2 or 8.1.1, however, although 8.1 is called an "update" it is not... 8.1 is an entirely separate OS from Windows 8.

EDIT:

In regards to installation keys... the only way this would occur is if you did a clean install of Windows 8.1 and did not perform an upgrade, or you changed your computer name when you set up 8.1 (this is very rare and only a handful of software keys are tied to the computer name, IDM being one of the few).  A clean install changes the Machine ID, which is what most license keys are tied to.

Also, MS Support has not been withdrawn for KB2919355 update issues and is free of charge.

Thanks for your reply JW9014

My understanding is that support for machines that have not been updated with KB2919355 was due to be withdrawn in mid-May but was extended because so many people were having installation issues. As far as I know, support will now be withdrawn in mid June, unless Microsoft announces another support extension. Beyond that date, Windows 8.1 machines that have not had KB2919355 installed will not get any further patches and will become increasingly vulnerable to threats and snags. 

See: http://www.infoworld.com/t/microsoft-windows/microsoft-posts-tips-overcoming-windows-81-update-kb-2919355-errors-242603

I spent several hours reading some of the discussion in this thread. Although I'm an experienced user, I'm not an expert software engineer and find some of the discussion too technical. If there is a solution to the issue that works then Microsoft needs to update the advice at the start of the article. Reading 21 pages of detailed technical discussion and trying to figure out which, if any, of the steps might work for me is something that I don't have time for, besides which, I don't have sufficient technical knowledge to sort the wheat from the chaff and might end up making the problem worse rather than better. Microsoft appears to have created this debacle and they need to provide a solution, via Microsoft Upgrade, that ordinary people can apply.

As regards the original upgrade from Windows 8 to 8.1, I did this using Microsoft Update. I have no idea whether that automatic process was a clean install or an upgrade but a number of software keys stopped working after the update. One of these was software from a company called Arturia and is for virtual synthesizer musical instruments. My MS Office wouldn't work and had to be reinstalled. I had similar issues with software from some other vendors, mainly music production related but also printer related. It took three days to install the upgrade and then resolve all of the consequential issues, time when I should have been carrying out productive work for myself and clients. I've been using Microsoft operating systems since the 80s and never has an upgrade caused so much grief (and that was prior to the KB2919355 debacle).

Sadly, much of my music production software is not compatible with either Mac or Linux; otherwise I would have jumped ship. It's reaching the stage now however that I might have to bite the bullet in the next year or so and invest in a new software suite that is Linux compatible. Despite the significant learning curve that will follow such a decision, it's probably my best long-term option. Now is not good timing for such a change however, given the stage I am at in the development of various recording projects. I should never have chosen Windows 8. Windows 7 was light-years better. I have considered downgrading but am worried that the process will result in a similar experience and wasted time to the 8.1 upgrade.