I'm doing a fresh install and update of windows 7 on an HP Envy laptop.  All has gone well other than a very recent WU security update for IE 11  (https://support.microsoft.com/en-us/kb/3038314) which refuses to install. I have tried installing via Windows Update, and it always fails (have tried multiple times, including after OS restart) with error code 80092004.   Tried downloading and installing manually and that also failed. 

Short of a VM, I cannot imagine a more pristine installation on which to run this update.  I'm really astounded it would fail, but hey when you fire your WU QA staff and quality is job none I guess this is what you get.  great job MS.

 For reference I've done the following

1) Fresh install from DVD's of Win7-SP1 64 bit

2) installed chrome (rather use that than IE8) 

3) using Chrome I downloaded and installed all appropriate drivers for this system directly from HP's site

4) multiple runs of Windows Update until there is nothing left to update. (this included updates to IE, which is at IE11 by the end of this process) until this one recent update showed up in last batch and refuses to update.

So, what now?  any ideas on how to get this security update to take? 

--Chuck

PS.  

Thanks so much MS for getting rid of all your windows update testers.  

• Edited by Chuck vdL 3 hours 15 minutes ago removed duplicate signature

Just found this googling; the exact same thing is happening to me. I was setting up a Windows 7 Pro VM to test some software, and it is failing on the same update with the same error. Complete fresh install in VMware Player.

So yeah, if ever we needed proof that MS has abandoned any pretense of testing and we are now the lab rats, here you have it.

This is one of the easiest scenarios one can imagine testing.  take a VM with a snapshot of a clean install, and let WU do it's thing and apply all updates.. which should of course 'just work'  it's a test of a very common scenario (fresh install) that real users do all the time.. ALL new updates ought to have to pass that test.  but clearly this one is not, so clearly it was never tested this way.

If this was some obscure interaction with a third party add-on or browser extension I would give them a pass, it's impossible to test everything.  but this is very 'golden path' scenario with no complications, just a clean installation and update.