For days now Vista has been bugging me about an update that just would not install (KB967723).
Even if I would shutdown the machine, it would just try and fail.
And not simply fail... but give me an amazing error code (80070490) which to cut a long story short meant that some internal database of updates was corrupt and I had to repair installation from the Vista CD. What???? Over my dead body!
Can you see the big picture here? I was minding my own business and one more Digital Misfortune came my way uninvited. But don't get me wrong here. If there is ONE technological feat that I admire in this world that is Microsoft Update. I just can believe such a thing is working. One major screw up (or security breach) and millions of computers can become unusable; just the security requirements of this blew my mind away... So I forgive them some glitches.
Anyway, since I had to debug this issue, I thought I might as well write a couple of lines about it, so that other poor souls like me might get a better chance when searching for an answer.
By searching the net and reading other posts I found some people mentioning that in similar situations they downloaded the standalone installer for the update and surprisingly enough it installed without problems.
Now that should ring some bells...
It is a seemingly non-rational action but it often has results.
So I downloaded the standalone installer for KB967723 and bingo! It installed and problem solved :-)
Isn't digital life so sweet?
Have Fun!
Dimitris Staikos
Even if I would shutdown the machine, it would just try and fail.
And not simply fail... but give me an amazing error code (80070490) which to cut a long story short meant that some internal database of updates was corrupt and I had to repair installation from the Vista CD. What???? Over my dead body!
Can you see the big picture here? I was minding my own business and one more Digital Misfortune came my way uninvited. But don't get me wrong here. If there is ONE technological feat that I admire in this world that is Microsoft Update. I just can believe such a thing is working. One major screw up (or security breach) and millions of computers can become unusable; just the security requirements of this blew my mind away... So I forgive them some glitches.
Anyway, since I had to debug this issue, I thought I might as well write a couple of lines about it, so that other poor souls like me might get a better chance when searching for an answer.
By searching the net and reading other posts I found some people mentioning that in similar situations they downloaded the standalone installer for the update and surprisingly enough it installed without problems.
Now that should ring some bells...
It is a seemingly non-rational action but it often has results.
So I downloaded the standalone installer for KB967723 and bingo! It installed and problem solved :-)
Isn't digital life so sweet?
Have Fun!
Dimitris Staikos
Superb! I had exactly the same problem and this trick resolved it.
Thank you very much
Posted by: HaJo Kremer | October 09, 2009 at 10:46 PM
thank you so much.. i was searching for this issue and finally solved it with your help.. :) but i am not sure if i will not be warned by the same code at the next update.. :) lets hope not.. thank you once again..
Posted by: mahir | October 11, 2009 at 12:18 PM
Thanks for this, I also solved the same problem with KB967723 with your observation and suggestin...Thank you
Posted by: Jorge Zetache | October 18, 2009 at 04:57 AM
I could have sworn I tried this first... it really sucks to get old. I noticed that the failed install all gave the name "Security Update for Windows Vista for x64-based Systems (KB967723)" and the successful update says simply "Security Update for Windows (KB967723)". Odd. Check out all the frustrated folks on the Microsoft blogs. e-gads. When I see endings that say "..hope this helps" I know the responder is hopeful, not knowledgeable. I use eset for virus scan and disabled it before the install. Works! Thanks Dimitris!
Posted by: Timothy Proksch | October 20, 2009 at 11:29 AM
thanks
Posted by: chad del rosario | November 25, 2009 at 11:03 PM
Great Solutions worked as a charm!!!
Thank you very much!
Posted by: James Logan | December 15, 2009 at 04:40 AM
Very nice. Thank you very much!
Posted by: Cecil | December 18, 2009 at 12:47 AM
Thanks, I solved the same issue for Windows Server 2008 64-bits
Direct link for that update:
http://www.microsoft.com/downloads/details.aspx?familyid=6E46822E-F79D-492D-AD01-EE680AD324F5&displaylang=en
Posted by: Hugo | December 22, 2009 at 09:10 AM
Finally, thank you so much, this problem has cost me already so many hours and now it is finally solved. Good work Mr Staikos!
Danny Lowet
Posted by: Danny Lowet | January 24, 2010 at 03:34 PM
Got the same code error on Windows Server 2008 (80070490). I read in various places that an update installation was necessary which made me cringe. After downloading KB967723 and KB976098 for Windows Server 2008 x86 directly I was able to manually install them successfully.
Posted by: Lance | January 30, 2010 at 02:47 AM
Thanks a lot! worked for me too ... next time we know where to go!
Posted by: Andre | February 17, 2010 at 02:08 PM
More echoed thanks. Same problem was quickly resolved with this post. You have my permission to buy yourself a donut.
Posted by: Brad | March 16, 2010 at 05:55 PM
BruteForce, you are the best! This issue was really "bugging" me & your solution fixed the problem L&S (i.e. lickity split). Thanks again, esdogman
Posted by: Eugene Sheffield | March 25, 2010 at 08:40 PM
Thanks a lot. it worked for me with Windows 2008 x64
Posted by: Marcin | March 26, 2010 at 12:48 AM
THANK YOU!!! What a service this is. You saved me so much time. Thanks again!!
Posted by: Cathy (in Portland Oregon) | April 22, 2010 at 08:00 AM
Thanks for that....but Windows Update still thinks it hasnt applied it?
Posted by: Philip | May 22, 2010 at 05:09 AM
Worked great, thanks.
Posted by: -- | September 27, 2010 at 05:11 PM
I wish I had seen this earlier. Would have saved a load of Microsofts misleading rubbish
Posted by: Allen | October 15, 2010 at 02:58 PM
Fantastic! It's also worked with other failed updates
Posted by: Tom | November 20, 2010 at 05:43 PM