Here is a bit sophisticated because you have coruupted not only in
C:\Windows\Servicing\Packages but also in
C:\Windows\WinSxS\Manifests
I attached to post corrupted files according to path they should be placed
Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7600.20602_none_c4f7d8ca09dfa6fb.manifest
winsxs\manifests\amd64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7600.16491_none_c40bea82f10bec2c.manifest
winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7600.20602_none_cf4c831c3e4068f6.manifest
winsxs\manifests\wow64_microsoft-windows-wow64_31bf3856ad364e35_6.1.7600.16491_none_ce6094d5256cae27.manifest
servicing\packages\Package_1_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_1_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_2_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_2_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB978637_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB978637_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_1_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_1_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_2_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_2_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB978637_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB978637_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB978637~31bf3856ad364e35~amd64~~6.1.1.1.cat
Two methods to fix thiese files (your choose)
METHOD I
1.Empty folder
C:\Windows\Logs\CBS
next download files attached to post and unpack them anywhere
2.Navigate to
C:\Windows\Servicing\Packages ,takeownership of this folder and add your account to have full control
3.Copy my *.cat ,*.mum files to this folder -if you have already any file then replace it.
4.Remove your account from permissions to Packages folder
5.Restore ownership of Packages folder back to "NT Service\TrustedInstaller"
6.Go to
C:\Windows\WinSxS\Manifests ,takeownership of this folder and add your account to have full control
7.Copy my *.manifest files to this folder -if you have already any file then replace it.
8.Remove your account from permissions to Manifests folder
9.Restore ownership of Manifests folder back to "NT Service\TrustedInstaller"
helpful links (please read them)
Take Ownership of file - Vista Forums
TrustedInstaller - Restore as Owner - Vista Forums
Folder Permissions - Vista Forums
//sometimes you may have problem to apply changes for Manifests problem even if you everything correct doing//
METHOD II (uncomfortable but always work)
1.Download attached to post
FixPacks.zip file -in zip file is packed
Packs folder -you have to unpack it and place directly on C: exactly as I show below:
2.Boot Win 7 DVD (if you don't have Win7 DVD instead use special recovery disk
Download Windows 7 System Recovery Discs — The NeoSmart Files )
Choose language>>Repair Computer>>WinRE>>command prompt
and type:
robocopy C:\Packs C:\ /E /IS
press ENTER,and next type:
del C:\Windows\Logs\CBS\*.*
press ENTER
3.Run system normally and try install updates
If still no result again run Readiness Tool and attache new CheckSur.log to post.