80080005 error on update KB2419640.

Page 1 of 2 12 LastLast

  1. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #1

    80080005 error on update KB2419640.


    Hi! Everyone,
    I'm not sure if I have a problem or not, and I need your valued opinions.

    This morning I had five updates, four from patch Tuesday, and one MSE. for a total of 26.6MB.

    I accepted all five, and told Win Update to go ahead and install them all. There were some that needed a restart and at the end of the update I was asked to restart my machine which I did.

    Update came back and said that one failed (KB2419640) because of an 80080005 error. The troubleshooter offered suggestions on how to fix this, and one of them was to restart my machine which I did again, and it still came back that it failed.

    I then went to KB2419640's download page, downloaded the file, proceeded to install it when it came back and said it wasn't going to because it was already installed....At that point I became .

    I went back to Control Panel\All Control Panel Items\Windows Update\View update history, and this is what I saw. See attachment.

    So...Do I have a problem or is it something not to worry about?

    Maybe try the registry mod suggested here?
    I only have two user accounts on this machine with only one running at a time.
    Attached Thumbnails Attached Thumbnails 80080005 error on update KB2419640.-patchtuesday11211.jpg  
      My Computer


  2. Posts : 24
    Win 10 pro x64 SP1
       #2

    Anak,

    My ISP was down last night so I did the updates this evening, I'm not sure this will help but here is what happened to me.

    On My desk top I did as you and accepted all 5 updates I had the same code and failure, my course was to "try again" so I let the PC load the action center (after re-boot) and when updates were checked again it showed the failed update, it loaded and succesfully installed.

    I then went to my wifes lap-top and on it I diden't select the "non-esstioal" update (the one unchecked) the four went in fine and when windows checked again after update it advised of teh remaining update, I checked it and it loaded without error

    Point being if you simply run Windows update will it load KB2419640 and complete rather than downloading it from microsoft?

    all the best -- Bill
      My Computer


  3. Posts : 232
    Window's 7 Ultimate 64bit
       #3

    I did all 5 updates on my 64 bit system and had the one fail also and then got it to install and when the compute started was on a black desktop and on a default user account not able to get to my regular user account Any one else have this problem tried system restore and registry restore to no avail still boots to the black temp default user account.
      My Computer


  4. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
    Thread Starter
       #4

    w7bill said:
    I then went to my wifes lap-top and on it I diden't select the "non-esstioal" update (the one unchecked) the four went in fine and when windows checked again after update it advised of teh remaining update, I checked it and it loaded without error.

    all the best -- Bill
    That's how it showed on my machine, with the one unchecked, with your success that's what I'm going to do from now on..

    And many happy returns to you and yours....Steve
      My Computer


  5. Posts : 10,455
    Microsoft Windows 7 Home Premium 64-bit Service Pack 1
       #5

    I think a lot of people are getting a failure on that update including myself. The solution for me was to allow the reboot before the failed update was attempted again. it went through cleanly on its own.
      My Computer


  6. Posts : 6,349
    Windows7 Pro 64bit SP-1; Windows XP Pro 32bit
       #6

    Anak

    Control Panel> Windows Update> View Update History.
    For those who don't know.

    Then in the left picture below click circled in yellow Installed Updates.

    Picture on right find the update and highlight. Then click "Uninstall" at top of list just to the left of "Organize."

    Re download and install update.
    Best would be direct from MS.
    It should work with old one deleted.

    Mike
    Last edited by Hopalong X; 26 Jan 2011 at 10:32.
      My Computer


  7. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
    Thread Starter
       #7

    kado897 said:
    I think a lot of people are getting a failure on that update including myself. The solution for me was to allow the reboot before the failed update was attempted again. it went through cleanly on its own.
    I seem to remember in the days of 3.1, 95, 98, and maybe even XP. Updates would warn a user to install certain updates separately because of the chance of a conflict when they were implemented after a reboot.

    Maybe that is why the box was unchecked even though it was an "important" update...sigh...

    Hopalong X said:
    Anak

    Control Panel> Windows Update> View Update History.
    For those who don't know.

    Then in the left picture below click circled in yellow Installed Updates.

    Picture on right find the update and highlight. Then click "Uninstall" at top of list just to the left of "Organize."

    Re download and install update.
    Best would be direct from MS.
    It should work with old one deleted.

    Mike
    Hopalong X said:
    For those who don't know.
    Hi! Hoppy, great to hear from you again!
    We had an advertising slogan at the newspaper where I retired from..."Now you know"!...

    Your solution is a lot more elegant than what I went through. Thanks for the tip!

    Steve
      My Computer


  8. Posts : 10,455
    Microsoft Windows 7 Home Premium 64-bit Service Pack 1
       #8

    Anak said:
    kado897 said:
    I think a lot of people are getting a failure on that update including myself. The solution for me was to allow the reboot before the failed update was attempted again. it went through cleanly on its own.
    I seem to remember in the days of 3.1, 95, 98, and maybe even XP. Updates would warn a user to install certain updates separately because of the chance of a conflict when they were implemented after a reboot.

    Maybe that is why the box was unchecked even though it was an "important" update...sigh...
    Yes. I think they expect most people to use the automatic install option, in which case it would probably have gone through OK.
      My Computer


  9. Posts : 6,349
    Windows7 Pro 64bit SP-1; Windows XP Pro 32bit
       #9

    I did one at a time. I just had a feeling not to try even two.

    Mike
      My Computer


  10. Posts : 908
    Vista Home Premium x86 SP2
       #10

    Hello!

    Apologies for the late reply. I have been taking a mini break :) Anyway, I actually believe that this issue is now resolved. Your update history shows a success, and the standalone thinks it has been installed. I think this is all that really needs to be said. If you are not happy, tell me, and I will check the logs files (not WindowsUpdate.log!)

    However, I may as well explain the error message while I am here.

    We are looking for an error lookup from winerror.h. This one is easy, because it only derives from winerror.h:
    Code:
    C:\Users\Richard>err 80080005
    # for hex 0x80080005 / decimal -2146959355 :
      CO_E_SERVER_EXEC_FAILURE                                      winerror.h
    # Server execution failed
    # 1 matches found for "80080005"
    
    C:\Users\Richard>
    This error code is usually caused by stress, and therefore sporadic. There must have been something in this update which stressed COM. You can read more about this error here: When CoCreateInstance returns 0x80080005 (CO_E_SERVER_EXEC_FAILURE) - Antimail - Site Home - MSDN Blogs

    I don't think that it is worth trying such an invasive solution for something which I believe is already installed. However, let me explain what it does. All it really does is set the Desktop heap. On a computer such as yours, it will likely limit the heap. This is not necessarily a bad thing. I would imagine that this is already in place on your computer anyway. Desktop heap is stored next to page file for a good reason, they are quite similar. You can read more about this whole key here: Windows and the ClearCase process limit: Understanding the desktop heap

    If you want me to see how installed it actually is, copy C:\Windows\Logs\CBS\CBS.log to your Desktop, right click on it > Send to > Compressed (zipped) folder, and upload that zip file here.

    I hope I have managed to contribute something, even in my lateness!

    Richard
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:36.
Find Us