Updates 2790113 and 2790655 failing

Page 1 of 2 12 LastLast

  1. rusitzky
    Posts : 6
    Windows 7 Professional x64
       New #1

    Updates 2790113 and 2790655 failing


    These 2 updates (2790113 and 2790655) have been failing since they came out about a week and a half ago. Other updates work fine. I have tried many suggestions from Microsoft but nothing has helped. I've run the System Update Readiness Tool and SFC Scan as you suggested. I'm attaching the logs you requested, the screenshot and also a zip of the WindowsUpdate.log file containing just the problem area.

    For what it's worth, this is Windows 7 Professional x64 running on a Malibal laptop.

    Thanks very much for any assistance.
      My Computer
    Quote Quote

  3. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #2

    Your problems stem from this....
    Code:
    Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22209_none_c6e51d4206ffe39b.manifest
 winsxs\manifests\amd64_microsoft-windows-consolehost_31bf3856ad364e35_6.1.7601.22209_none_d31b1c8931ca7785.manifest
 winsxs\manifests\amd64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22209_none_f27d3a7985fc3a80.manifest
 winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22209_none_153debdacc05e77d.manifest
 winsxs\manifests\amd64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22209_none_85c1cd8be444c26c.manifest
 winsxs\manifests\wow64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22209_none_bfaf6c60195efb2c.manifest
 winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.22209_none_1f92962d0066a978.manifest
 winsxs\manifests\wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.22209_none_901677de18a58467.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.22209_none_d139c7943b60a596.manifest
 winsxs\manifests\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.22209_none_fcd1e4cbba5cfc7b.manifest
 winsxs\manifests\amd64_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22209_none_6971452eab80a50e.manifest
 winsxs\manifests\x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.22209_none_0d52a9aaf32333d8.manifest
 winsxs\manifests\wow64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18043_none_1ed7b60fe76ee441.manifest
 winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7601.18043_none_d07ee7772268e05f.manifest
 winsxs\manifests\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.1.7601.18043_none_14830bbdb30e2246.manifest
 winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.22209_none_11dd678a9616f2c8.manifest
 winsxs\manifests\amd64_microsoft-windows-netio-infrastructure_31bf3856ad364e35_6.1.7601.22209_none_b55ac20de4fe3931.manifest
 winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.18042_none_112187237d20143a.manifest
 servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_3_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_4_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2790113_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2790113~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2790655_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2790655~31bf3856ad364e35~amd64~~6.1.1.0.cat
    I'll post a fix protocol later - it may be a while!
      My Computer
    Quote Quote

  4. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #3

    I've uploaded a file - rzkaa.zip - to my SkyDrive at Noel's SkyDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder rzkaa in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer
    Quote Quote

  6. rusitzky
    Posts : 6
    Windows 7 Professional x64
    Thread Starter
       New #4

    I tried the Windows Updates after following your instructions. They still failed (but perhaps you expected that). Here are the 2 files you requested.

    Thanks very much for your assistance.
      My Computer
    Quote Quote

  7. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #5

    So far, so good :)
    All the CheckSUR patches 'took'

    Now please run another SFC /SCANNOW, and post the new CBS.log file.
    Then we'll see if three's anything new been found because of the new data.
      My Computer
    Quote Quote

  8. rusitzky
    Posts : 6
    Windows 7 Professional x64
    Thread Starter
       New #6

    Here's the CBS.log file. Thanks.
      My Computer
    Quote Quote

  10. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #7

    There was one minor file repair made - otherwise, the SFC data is clean.

    First, do a Check for Updates, then attempt to install the oldest one found
    What is the error message now?
      My Computer
    Quote Quote

  11. rusitzky
    Posts : 6
    Windows 7 Professional x64
    Thread Starter
       New #8

    I'm not sure which is oldest, since they are both from Feb 12, 2013. I tried them independently. They both fail the same way as before:
    2790113 still fails with 8007065E
    2790655 still fails with 800B0100
      My Computer
    Quote Quote

  12. rusitzky
    Posts : 6
    Windows 7 Professional x64
    Thread Starter
       New #9

    Any more help on this (please)?
      My Computer
    Quote Quote

  13. NoelDP
    Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       New #10

    Sorry - ISP problems

    I'm playing catchup at present, but I'll get back to you ASAP
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
My updates keep failing and searching for updates takes forever. I have tried a lot of things like: - run MicrosoftFixit50123 - clean boot with only windows services - chkdsk /F - sfc /scannow - try to install packages manually - run CheckSUR and a couple other things I can't remember...
I get a message everytime I try to updates Windows, there is over 112 updates which could not install, I have attached a picture of my error code (In the picture i have only tried one to see if it would work.) Thanks :huh: 301011 301030
Hi, this particular update has refused to install correctly since the 14th. Other updates have installed with no issue. Ran SURT and tried to manually install it from direct download. Any help much appreciated.
Last week I formatted my hard drive and did a clean install of Win7. Windows update found 99 updates, eventually these were all installed. No progs were loaded at this time. More than half have failed; five pages full on a 22" monitor. Many are 'important'. jpeg shows about 1/5 of the failures....
Windows Updates failing
in Windows Updates & Activation

I have 5 windows updates that fail every time I try to install them. They are: KB977863, KB972270, KB978251, KB976264, KB979306. It says error code: 800B0100. I've run the system update readiness tool but it still doesn't work. Any suggestions? Thanks
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 13:33.
Find Us