none
KB3126587 and KB3126593 Install Fails with error 80070026 RRS feed

  • Question

  • Win 7 64 bit, Home Premium, SP1.  These two updates fail to install with the above error code.  The other Feb 10, 2016 updates installed OK. 

    I have manually downloaded them, ran as administrator (activated hidden Administrator, i.e., net use administrator /active:yes), but no luck.  An Internet search gives no info on the particular error code or any usable answers.

    I have reset/re-registered Win Update components (didn't help), and ran MS's Fixit for Update problems (KB971058).  It came back with "Didn't fix Error 80070026 Problem."

    I use WSUS on my work network, and so far have not any errors on my update test machine, and the on two additional machines after releasing these two updates for install.  All work machines are 64 bit Win-7 Pro SP1.  I'm not sure if the problem is Home vs Pro versions, as I only have one Home machine (at home).

    Any ideas welcome!



    • Edited by cmn27156 Monday, February 15, 2016 1:49 AM
    Thursday, February 11, 2016 3:45 AM

All replies

  • Also, failed install on Win7 x86-Ultimate: Error 80073712.

    Manually downloaded and attempted install with same error.

    Thursday, February 11, 2016 3:57 PM
  • Hi,

    Since the new released updates have the error in your system, please remove the error updates temporarily. Also, you could use System Restore to let the PC back to the point before install the updates. http://windows.microsoft.com/en-US/windows7/Restore-system-files-and-settings

    We need to do more test for the updates.

    Best Regards,

    Simon


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.


    Friday, February 12, 2016 1:16 PM
    Moderator
  • I am getting this issue as well but my error code: 80073701. What Service pack you running on? I am on Windows 7 Pro 64bit SP1.
    Sunday, February 14, 2016 8:08 PM
  • Unfortunately, during testing to try to get them installed, the automatic creation of restore points with each install try completely over-wrote any stored point that that may have preceded the initial Update load. 
    Monday, February 15, 2016 1:52 AM
  • same issue, i have researched the failures as well as possible work arounds, nothing yet. posts for possible CBS store issues/corruption, using the System Update Readiness tool, etc, all failed.

    i did see others recommending adding more archives to the checkSUR archive, and have not tried that yet. (supposedly will allow SUR to verify more files)

    windows\logs\CBS.log is huge by the way, and if you havent cleaned up that folder, you should. running SUR typically generates over 500mb of CBS.log. 

    checkSUR log shows manifest failed catalog errors, i dont know if this is due to those catalogs not being present (the ones people recommended downloading) or if those packages are broken and SUR is failing to fix them. (errors repeat each time its run)

    CBS.log is harder to deal with, if you use UAC, you have to add your user to the file, as users do not have access. 
    if you want to clear the CBS.log you need to stop the Windows Modules Installer service. (not to be confused with WMI, which is Windows Management Instrumentation) 

    seeing errors like this: 

    2016-02-16 03:39:31, Info                  CBS    Disabling manifest caching, because the image is not writeable.
    2016-02-16 03:39:31, Info                  CSI    0000062a CSI Store 33497520 (0x0000000001ff21b0) initialized
    2016-02-16 03:39:31, Info                  CBS    Session: 4800_149566894 initialized by client SPP.
    2016-02-16 03:39:32, Info                  CBS    End of file unexpectedly reached [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Failed to get next Token [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Wrong XML DECL [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Invalid xml format [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Manifest parsing error at line: 1, context: 
    XÛ [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Failed to parse the manifest from the buffer. [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Error                 CBS    Failed to parse package manifest: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\Windows\Servicing\Packages\Package_for_KB3110329_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Failed to initialize package: Package_for_KB3110329_SP1~31bf3856ad364e35~amd64~~6.1.1.1, from path: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\Windows\Servicing\Packages\Package_for_KB3110329_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum, existing package: 1 [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Failed to resolve package [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Failed to populate children. [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Failed to initialize internal package [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Info                  CBS    Failed to create package. [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]
    2016-02-16 03:39:32, Error                 CBS    Failed to internally open package. [HRESULT = 0x80070026 - ERROR_HANDLE_EOF]

    Tuesday, February 16, 2016 7:40 PM
  • Repeated failures for the following updates for me as well: (Windows 7 Home Premium SP1)

    1. Security Update for Windows 7 for x64-based Systems (KB3126587) Error details: Code 80070490
    2. Security Update for Windows 7 for x64-based Systems (KB3126593) Error details: Code 80070490

    Thursday, February 25, 2016 2:24 PM
  • I am also having this issue on a W7 64-bit Ultimate installation.  KB3126587 and KB3126593 fail with Error 80070026, and the C:\Windows\Logs\CBS folder becomes huge.  This is causing quite a problem for my end user, as he has a small SSD drive and runs out of HD space.  Please help us find a solution!!  Thanks!



    Wednesday, March 2, 2016 10:03 PM
  • Same problem here...

    Any news yet?

    Saturday, March 5, 2016 4:37 PM
  • I appear to be at a disadvantage, I am experienced but not as confident as other users in this forum.

    Please provide me with a step by step instructions how to resolve this issue. Thank you.

    I have noticed that KB3126587 is failing to install since 2/10/2016. The system keeps trying with zero success, what follows is a transcript of the error:

    ------------------------------------------------

    Security Update for Windows 7 for x64-based Systems (KB3126587)

    Installation date: ‎02/‎10/‎16 7:17 AM

    Installation status: Failed

    Error details: Code 80070570

    Update type: Important

    A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.

    More information: 
    http://support.microsoft.com/kb/3126587

    Help and Support: 
    http://support.microsoft.com
    Thursday, March 10, 2016 8:58 PM
  • Any news on this one? I'm having the same issue and cannot resolve it. It may be stopping me upgrade to Windows 10.
    Wednesday, May 25, 2016 1:49 PM
  • I am also having this issue. It takes forever for my computer to shut down while it tries to install this one update. Then it takes forever to boot up again trying to undo or apply any changes made. According to my records this update has tried to install over 100 times since February 24th, 2016.

    My only conclusion is that this update is NOT valid for Windows 7 and someone at Microsoft screwed up and mistakenly assigned it an attribute so it shows up as a Windows 7 Update when the update process looks for updates.

    Edit: I just realized that there are two updates in the title of this thread. I am specifically referring to KB3126587. And I still think my idea is correct: Someone who releases these updates to the public accidentally clicked "Windows 7" on this one and now every Windows 7 PC thinks it needs this incompatible update.

    This is actually inspired by an error I recently experienced with Netflix. A show I was watching was always appearing with subtitles despite having English audio. Turns out someone had inadvertently flagged it as a foreign language title and the show is always defaulted to play with subtitles.
    • Proposed as answer by Nilrem333 Friday, September 23, 2016 2:54 AM
    • Edited by Nilrem333 Friday, September 23, 2016 3:21 AM Added specifics of the update number KB3126587
    Friday, September 23, 2016 2:53 AM
  • Is there anybody that has the update actually installed on Windows 7?  I looked at the system requirements listed on the download page for KB3126587.  There is one and only one requirement - Windows 7 SP1.  It would be odd if this is not correct because the fix could be as simple as retracting the update.  It would be nice to know if this patch can be skipped.  (I have hundreds of install failures for this patch on my desktop at work.) 

    And another Netflix analogy, Netflix was in the news because it was completely down for a couple of hours the past weekend.  With my windows 10 machines at home, I cross my fingers and wonder if it will be hours, days, or a re-install of the OS when a non-optional update is installed.  Subtitles and an old OS patch failing are probably not high priorities at the moment. 


    Randy in Marin

    Monday, October 3, 2016 6:24 PM
  • my laptop with Win 7 Home 64 installed this update in Feb when it first came out, but my Win 7 Pro 64 has continually FAILED.
    Friday, November 4, 2016 9:59 PM