Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Updates 2790113 and 2790655 failing


26 Feb 2013   #1
rusitzky

Windows 7 Professional x64
 
 
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.




Attached Thumbnails
-windowsupdateerror.jpg  
Attached Files
File Type: zip WindowsUpdate.zip (4.1 KB, 2 views)
My System SpecsSystem Spec
26 Feb 2013   #2
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
26 Feb 2013   #3
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
26 Feb 2013   #4
rusitzky

Windows 7 Professional x64
 
 

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.


Attached Files
File Type: log CheckSUR.log (13.0 KB, 3 views)
File Type: log CheckSUR.persist.log (114.5 KB, 1 views)
My System SpecsSystem Spec
26 Feb 2013   #5
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
27 Feb 2013   #6
rusitzky

Windows 7 Professional x64
 
 

Here's the CBS.log file. Thanks.
My System SpecsSystem Spec
27 Feb 2013   #7
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
27 Feb 2013   #8
rusitzky

Windows 7 Professional x64
 
 

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 System SpecsSystem Spec
28 Feb 2013   #9
rusitzky

Windows 7 Professional x64
 
 

Any more help on this (please)?
My System SpecsSystem Spec
28 Feb 2013   #10
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

Sorry - ISP problems

I'm playing catchup at present, but I'll get back to you ASAP
My System SpecsSystem Spec
Reply

 Updates 2790113 and 2790655 failing




Thread Tools



Similar help and support threads for2: Updates 2790113 and 2790655 failing
Thread Forum
Windows7 updates keep failing Windows Updates & Activation
Many but not all updates failing on Windows 64-bit Windows Updates & Activation
Solved Windows Updates Keep Failing Windows Updates & Activation
Updates failing to install Windows Updates & Activation
Solved Win7 32x, format & reload, win updates 60% failing (50+ updates) Windows Updates & Activation
System Updates keep failing Windows Updates & Activation
Windows Updates failing Windows Updates & Activation

Our Sites

Site Links

About Us

Find 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 08:43 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App