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: Update Errors and Unavailable repair files

12 May 2015   #1
elkevo20

Windows 7 Professional 64 bit
 
 
Update Errors and Unavailable repair files

The windows update error codes are Code 80073712 and 64C Also Looking at the CheckSUR Log I have many unavailable repair files.




Attached Files
File Type: log CheckSUR.log (24.4 KB, 4 views)
My System SpecsSystem Spec
.
12 May 2015   #2
americancritic2

Windows 7 Home Premium 64-Bit SP1
 
 

Hello and welcome to the sevens forum.

1. First I would do is a complete scan using your security.

2. Go to accessories right click the command promt, type sfc /scannow and let it run without using your system to see if it will repair any files.
My System SpecsSystem Spec
12 May 2015   #3
elkevo20

Windows 7 Professional 64 bit
 
 

Scanned nothing came up, and the sfc scan didn't find any problems.
My System SpecsSystem Spec
.

13 May 2015   #4
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Here's the error-list from the CheckSUR log...
Code:
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.18637_en-us_b818f58670898bbd.manifest
 winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22843_none_80a46a3e85194f37.manifest
 winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22843_none_25d0997ea843ed32.manifest
 winsxs\manifests\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.18637_none_c937305dd6bd2876.manifest
 winsxs\manifests\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.18637_none_ecb2935b6af13c52.manifest
 winsxs\manifests\wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.18637_none_f7073dad9f51fe4d.manifest
 winsxs\manifests\x86_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22843_en-us_672eda97174dc073.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.22843_en-us_e535f381c671cf9d.manifest
 winsxs\manifests\amd64_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22843_en-us_c34d761acfab31a9.manifest
 winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18637_none_0eb286a7a7d91f21.manifest
 winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22843_none_4fb9a6ae1504ca69.manifest
 winsxs\manifests\x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22843_none_c627b51c19090c11.manifest
 winsxs\manifests\amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22843_none_bc6c74c221728719.manifest
 winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.22843_none_db410c0392613b8e.manifest
 winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22843_none_995b6a47ac8b8c3f.manifest
 winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22843_none_0f2d5444c10272a7.manifest
 winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22843_none_2246509fd1667d47.manifest
 winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22843_none_4564fc5be0a4086e.manifest
 winsxs\manifests\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22843_none_360bd4ac6c7e009c.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22843_none_04d8a9f28ca1b0ac.manifest
 winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22843_none_604dd93e691515e3.manifest
 winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22843_none_8af91490b97a1132.manifest
 winsxs\manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.22843_none_e595b655c6c1fd89.manifest
 winsxs\manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22843_none_a3b01499e0ec4e3a.manifest
 winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22843_en-us_5c75279fd1556e0d.manifest
 winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.18637_none_2555cbe18f1a99ac.manifest
 winsxs\manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22843_none_d9ed3928b4208f66.manifest
 winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.18637_en-us_5bfa5a02b82c1a87.manifest
 winsxs\manifests\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.22843_none_ed2d60f8841a8fd8.manifest
 winsxs\manifests\wow64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.22843_none_f7820b4ab87b51d3.manifest
 winsxs\manifests\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22843_en-us_b893c32389b2df43.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18637_none_045ddc5573785d26.manifest
 winsxs\manifests\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22843_none_c9b1fdfaefe67bfc.manifest
 servicing\packages\Package_105_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_105_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_106_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_106_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_107_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_107_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_108_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_108_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_109_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_109_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_111_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_111_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_112_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_112_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_113_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_113_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_114_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_114_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_115_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_115_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_3_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_49_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_49_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_4_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_50_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_50_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_51_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_51_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_53_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_53_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_54_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_54_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_5_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_80_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_80_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB3003057_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB3003743_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB3003743_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
I'll post a fix protocol later.
My System SpecsSystem Spec
13 May 2015   #5
elkevo20

Windows 7 Professional 64 bit
 
 

So any idea?
My System SpecsSystem Spec
14 May 2015   #6
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

I've uploaded a file - accaa.zip - to my OneDrive at Noel's OneDrive
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 accaa 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
14 May 2015   #7
elkevo20

Windows 7 Professional 64 bit
 
 

Ok it seems to look a lot better only says 1 thing is unavailable now.


Attached Files
File Type: log CheckSUR.log (27.2 KB, 2 views)
File Type: log CheckSUR.persist.log (62.9 KB, 0 views)
My System SpecsSystem Spec
14 May 2015   #8
elkevo20

Windows 7 Professional 64 bit
 
 

Also now when I do a sfc /scannow I get
The CBS Log is 330 mb So I zipped it and put it on onedrive heres the link https://onedrive.live.com/redir?resi...int=file%2czip


Attached Images
Update Errors and Unavailable repair files-sfc-error.jpg 
My System SpecsSystem Spec
15 May 2015   #9
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

Here's the CheckSUR error...
Code:
Unavailable repair files:
 winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22843_en-us_5c75279fd1556e0d.manifest
... back in a jiffy!
My System SpecsSystem Spec
15 May 2015   #10
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

I've uploaded a file - e20aa.zip - to my OneDrive at Noel's OneDrive
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 e20aa in the same place.
Open this folder - there should be one folder inside it (Manifests, )

Copy 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
Reply

 Update Errors and Unavailable repair files




Thread Tools




Similar help and support threads
Thread Forum
Unavailable repair file Manifest Missing
My Checksurlog indicates 1 CSI Manifest Missing and 41 CSI Payload Files Missing. I found one instance of this manifest file on the internet but was not able to get it recognized by Windows. Nor could I find the related KB-number. Otto
Installation & Setup
win 7 sp1 not showing up. Checksur unavailable repair files.
Hi all; Windows update reports no available updates yet sp1 is not installed. SFC found no violations. Checksur completed and the log is as follows. I have not had any luck finding the files mentioned. ================================================================== Checking System Update...
Windows Updates & Activation
Errors when opening/saving Office files, how to repair?
Hello all, Office decided to stop working last night. Everytime I save/rename a document I've been working on I get an error. Saving an Excel document I've been working on: "Your changes could not be saved to FILE NAME because of because of sharing violation" When I click OK on that: "Your...
Microsoft Office
Getting Update Error 800B0100, unavailable repair files
I tried to perform a windows update after it being such a long while and got an error of 800B0100. I have also tried running update readiness tool. I included the log in the attachments can someone please help me i'm just trying to update my windows.
Windows Updates & Activation
Update Error 800B0100, unavailable repair files
I noticed end of last month after coming back from travel that my PC did not offer any updates. To make sure I manually started the check for updates. It came back with Windows Update Error 800b0100. I tried - restarting PC - restarting windows update service - renaming...
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 10:58.
Twitter Facebook Google+