give me a bit that's a lot of files i'm going to check if I have them if not ill get them from microsoft's update catalog database. :cheesy:
I have started a huge file repository on my system with all the cat and mum files and made a little program for myself where I put in the list of files and it goes and grabs them for me. I plan on making a tool and putting these files online later on. :wink:
Shane
Problem grabbing those missing files, MS updated that update with a new version and so the old version cant be downloaded.
It only gave me
package_for_kb2952664~31bf3856ad364e35~x86~~6.1.10.5
Notice the 6.1.10.5 while he needs the 6.1.6.1.
So what needs to be done instead is to go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
and delete the keys that point to those missing files.
Shane
Yes that should work BUT he needs to take permissions of that registry section first in order to remove them.
Shane
Hi, check up with windows readiness tool for windows 7. It is a good tool at getting missing windows files
Hi, check up with windows readiness tool for windows 7. It is a good tool at getting missing windows files
Hi,
https://support.microsoft.com/en-us/kb/2700601
Please see this link. especially steps to resolve part.
If you could see the check sur log and then get the files for which fix are not available . These files you have to download from other machine from same version. Hope that this helps
I have the files removed and 2 installed but now still failing with error 80073712
When you try to install updates from Windows Update or Microsoft Update, you may receive error 0x80073712, and the update does not install.
This issue may occur if the Component-Based Servicing (CBS) manifest is corrupted.
QuoteI have the files removed and 2 installed but now still failing with error 80073712
Ok so that sounds like progress, 2 updates installed, which updates are failing?
The error meansQuoteWhen you try to install updates from Windows Update or Microsoft Update, you may receive error 0x80073712, and the update does not install.
This issue may occur if the Component-Based Servicing (CBS) manifest is corrupted.
Thanks Shane
Much appreciated.
Just really frustrating.
Which means some manifest files are corrupt or missing, which from the log you posted is a lot of them. And looks like some files as well, all of these it is looking for are in the Winsxs folder, looks like you might of had something remove files from there when it shouldnt have.
I can see if I have those in my winsxs folder and if I do I can grab them for you.
Shane
Hi, Internet explorer normally updated itself with window updates . Please check.
Try the appropriate Offline Installer from http://windows.microsoft.com/en-GB/internet-explorer/ie-11-worldwide-languages but should your original problem be due to your AV program, downloading while in Safe Mode with Networking will isolate all 3rd party programs.
I am not sure how to replace these files.
Tweaking.com - Windows Repair - Pre-Scan
Computer: (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
Started at (6/4/2015 4:47:53 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (6/4/2015 4:47:53 PM)
These Files Are Missing: (Total: 66)
C:\Windows\servicing\Packages\Package_105_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_105_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_106_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_106_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_107_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_107_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_108_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_108_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_109_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_109_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_111_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_111_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_112_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_112_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_113_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_113_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_114_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_114_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_115_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_115_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3006137~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3006137~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_49_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_49_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_4_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_50_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_50_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_51_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_51_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_53_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_53_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_54_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_54_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_5_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_5_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB3006137~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_5_for_KB3006137~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_80_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_80_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_for_KB3003057_RTM~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3003057_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3003057~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3003743_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3003743_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3003743~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3006137_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3006137_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3006137~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3006137~31bf3856ad364e35~amd64~~6.1.1.0.mum
Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.
These files do not keep the repairs from working, you may still run the repairs in the program.
If you need help in replacing these files, post on the Forums at Tweaking.com for help.
Files Checked & Verified: 5,503
Done (6/4/2015 4:49:54 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (6/4/2015 4:49:54 PM)
No problems were found with the Reparse Points.
Files & Folders Searched: 191,316
Reparse Points Found: 108
Done (6/4/2015 4:52:40 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (6/4/2015 4:52:41 PM)
No problems were found with the Environment Variables.
Done (6/4/2015 4:52:41 PM)
--------------------------------------------------------------------------------
Done (6/4/2015 4:52:41 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Done (6/4/2015 4:52:41 PM)
Scan Complete - Problems Found!
You can use the Repair Reparse Points or Repair Environment Variables tools at the bottom of this Window if needed.
While problems have been found, you can still run the repairs in the program.
But for the best results it is recommended to fix the problems reported in this scan if possible.
If you need help fixing any of the items in the log, just post in the forums at Tweaking.com for help.