Author Topic: Corrupted Package Files - Need Help (WR issues - Solved)  (Read 11149 times)

0 Members and 1 Guest are viewing this topic.

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Corrupted Package Files - Need Help (WR issues - Solved)
« on: December 29, 2015, 12:50:07 PM »
Hi,  Using Windows Repair v3.7.3 - Pre-Scan

Pre-Scan found some corrupt (bad signature) packages.  Pasting log:

┌────────────────────────────────────────────────────────────────────────────────┐
│ Tweaking.com - Windows Repair v3.7.3 - Pre-Scan
│ Computer: DONNA-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
│ [Started Scan - 12/29/2015 2:56:06 AM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (12/29/2015 2:56:06 AM)

│ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 6)
C:\Windows\servicing\Packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum

6 Combined 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: 6,617

│ Done Scanning Windows Packages Files.(12/29/2015 2:56:35 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Reparse Points.
│ Started at (12/29/2015 2:56:35 AM)

│ Reparse Points are OK!.

│ Files & Folders Searched: 195,874
│ Reparse Points Found: 46

│ Done Scanning Reparse Points.(12/29/2015 2:56:51 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Checking Environment Variables.
│ Started at (12/29/2015 2:56:51 AM)

│ No problems were found with the Environment Variables.

│ Done Checking Environment Variables. (12/29/2015 2:56:51 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ [Finished Scan - 12/29/2015 2:56:51 AM]

  • 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.

└────────────────────────────────────────────────────────────────────────────────┘



Thank you guys for the Repair Tool, can I get some help on replacing these corrupt packages?

Thanks
Omni
« Last Edit: January 14, 2016, 11:56:56 AM by The_Omni »

Offline Julian

  • "Cat and Mum Guy"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1320
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #1 on: December 29, 2015, 04:45:37 PM »
hmm i got all but 2 files
Code: [Select]
Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat
Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum


First grab the zip file off this page and apply the reg file in it to add the take owner ship to the right click menu in explorer.
http://www.tweaking.com/articles/pages/add_quottake_ownershipquot_to_right_click_menu_in_vista_amp_7,1.html

Once that is done go to C:\Windows\servicing\ and right click on Packages and click on take ownership. You will now be able to copy the files into that folder.

I have attached the missing files, extract the files out of the attached zip file and put them in the C:\Windows\servicing\Packages\ folder.

Then run the pre-scan again, put a check on the box to have it add the cat files back to the database. :wink:

Julian

(THIS REPAIR IS USER SPECIFIC IF YOU ARE HAVING ISSUES WITH MISSING CAT OR MUM FILES MAKE A POST IN COMPUTER HELP AND I WILL HUNT DOWN THOSE FILES FOR YOU) :cheesy:
Julian

Offline Julian

  • "Cat and Mum Guy"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1320
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #2 on: December 29, 2015, 04:50:35 PM »
Both Windows Repair and SFC look at
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" To know what files are inside the packages folder. So since this was a bad update I think the best thing to do would be to remove those file entries from that registry location.

You have to take ownership and permissions of "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" and have it do all the subitems as well, then you will be able to remove them.

backup the registry just in case, remove the items and then reboot and see how it goes.

by removing them from that registry location both Windows Repair and SFC will stop looking for them. I think when the update was pulled and the new version sent and installed, it removed the files but didnt remove the registry keys pointing to them.
these are the ones you will be looking for in the registry
Code: [Select]
Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat
Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
Julian

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #3 on: December 29, 2015, 06:48:47 PM »
Thanks Julian, but I don't see the attached zip file.

Omni

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #4 on: December 31, 2015, 10:35:24 AM »
Julian?

Can you post the zip file again?

Thanks
Omni

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9239
  • Location: UK
  • Karma: 117
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #5 on: December 31, 2015, 02:11:19 PM »
I wasn't aware that KB3108381 had been pulled as I have it as installed on the 9th Dec.
Tom.

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #6 on: December 31, 2015, 04:46:21 PM »
Boggin,

Its funny because according to Uninstall list this PC doesn't have KB3108381 installed, but obviously it does.

Julian, I still need the zip file.

Thanks,
Omni

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9239
  • Location: UK
  • Karma: 117
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #7 on: January 01, 2016, 01:33:13 AM »
Install KB3108381 then do the Pre-Scan again to see if it still snags those files.

https://www.microsoft.com/en-us/download/details.aspx?id=50302

Tom.

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #8 on: January 03, 2016, 07:29:08 PM »
Thank you Boggin

Ok Here is an update:

Tried to update KB3108381 using the standalone updater, it failed.

Error Code 80073712

Then used DISM tool resulted in these errors

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-01-02 17:24

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)   CBS MUM Corrupt   0x800F0900   servicing\Packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum      Line 1:
(f)   CBS Catalog Corrupt   0x800B0100   servicing\Packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat      
(f)   CBS MUM Corrupt   0x800F0900   servicing\Packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum      Line 1:
(f)   CBS Catalog Corrupt   0x800B0100   servicing\Packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat      
(f)   CBS MUM Corrupt   0x800F0900   servicing\Packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum      Line 1:
(f)   CBS Catalog Corrupt   0x800B0100   servicing\Packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat      

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_7516585c176aff7a.manifest   x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_7516585c176aff7a   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_d134f3dfcfc870b0.manifest   amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_d134f3dfcfc870b0   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_d0b0235eb6a81fc4.manifest   amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_d0b0235eb6a81fc4   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_749187dafe4aae8e.manifest   x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_749187dafe4aae8e   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646.manifest   wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075.manifest   wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a.manifest   amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b.manifest   amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b   

Summary:
Seconds executed: 542
 Found 14 errors
  CSI Manifest All Zeros Total count: 8
  CBS MUM Corrupt Total count: 3
  CBS Catalog Corrupt Total count: 3

Unavailable repair files:
   winsxs\manifests\x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_7516585c176aff7a.manifest
   winsxs\manifests\amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_d134f3dfcfc870b0.manifest
   winsxs\manifests\amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_d0b0235eb6a81fc4.manifest
   winsxs\manifests\x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_749187dafe4aae8e.manifest
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646.manifest
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b.manifest
   servicing\packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
   servicing\packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
   servicing\packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
   servicing\packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
   servicing\packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
   servicing\packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
   servicing\packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat
   servicing\packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat
   servicing\packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
   servicing\packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
   servicing\packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat
   servicing\packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat

----------------------------------------------------------------------------------------------------------

Downloaded and used Windows6.1-KB3108381-x64 with DISM to repair, Results:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-01-02 18:35

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)   CBS MUM Corrupt   0x800F0900   servicing\Packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum      Line 1:
(fix)   CBS MUM Corrupt   CBS File Replaced   Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab.
(fix)   CBS Paired File   CBS File also Replaced   Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.cat from Cabinet: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab.
(f)   CBS MUM Corrupt   0x800F0900   servicing\Packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum      Line 1:
(fix)   CBS MUM Corrupt   CBS File Replaced   Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum from Cabinet: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab.
(fix)   CBS Paired File   CBS File also Replaced   Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat from Cabinet: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab.
(f)   CBS MUM Corrupt   0x800F0900   servicing\Packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum      Line 1:
(fix)   CBS MUM Corrupt   CBS File Replaced   From Directory: C:\Windows\Temp\CheckSUR\MSU\
(fix)   CBS Paired File   CBS File also Replaced   From Directory: C:\Windows\Temp\CheckSUR\MSU\

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_7516585c176aff7a.manifest   x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_7516585c176aff7a   
(fix)   CSI Manifest All Zeros   CSI File Replaced   File: x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_7516585c176aff7a.manifest From: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_d134f3dfcfc870b0.manifest   amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_d134f3dfcfc870b0   
(fix)   CSI Manifest All Zeros   CSI File Replaced   File: amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.23278_none_d134f3dfcfc870b0.manifest From: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_d0b0235eb6a81fc4.manifest   amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_d0b0235eb6a81fc4   
(fix)   CSI Manifest All Zeros   CSI File Replaced   File: amd64_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_d0b0235eb6a81fc4.manifest From: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_749187dafe4aae8e.manifest   x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_749187dafe4aae8e   
(fix)   CSI Manifest All Zeros   CSI File Replaced   File: x86_microsoft-windows-c..fe-catsrvut-comsvcs_31bf3856ad364e35_6.1.7601.19062_none_749187dafe4aae8e.manifest From: C:\Windows\Temp\CheckSUR\MSU\Windows6.1-KB3108381-x64.cab
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646.manifest   wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075.manifest   wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a.manifest   amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b.manifest   amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b   

Summary:
Seconds executed: 498
 Found 11 errors
 Fixed 7 errors
  CSI Manifest All Zeros Total count: 8
  Fixed: CSI Manifest All Zeros.  Total count: 4
  CBS MUM Corrupt Total count: 3
  Fixed: CBS MUM Corrupt.  Total count: 3
  Fixed: CBS Paired File.  Total count: 3

Unavailable repair files:
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646.manifest
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b.manifest
--------------------------------------------------------------------------------------------------------------


After the repair I was able to get KB3108381 to install.

After getting KB3108381 to install I ran the scan again.


 Tweaking.com - Windows Repair v3.7.3 - Pre-Scan
│ Computer: DONNA-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
│ [Started Scan - 1/3/2016 8:15:24 PM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (1/3/2016 8:15:25 PM)

│ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 3)
C:\Windows\servicing\Packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum

3 Combined 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: 6,663

│ Done Scanning Windows Packages Files.(1/3/2016 8:16:09 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Reparse Points.
│ Started at (1/3/2016 8:16:09 PM)

│ Reparse Points are OK!.

│ Files & Folders Searched: 203,888
│ Reparse Points Found: 46

│ Done Scanning Reparse Points.(1/3/2016 8:16:31 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Checking Environment Variables.
│ Started at (1/3/2016 8:16:31 PM)

│ No problems were found with the Environment Variables.

│ Done Checking Environment Variables. (1/3/2016 8:16:31 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ [Finished Scan - 1/3/2016 8:16:31 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.

└────────────────────────────────────────────────────────────────────────────────┘
----------------------------------------------------------------------------------------------------------


So here we are again with more KB3108381 errors.  Note DISM does not show these errors but instead shows errors in some manifest files.

Another note Windows Update is still failing to install  KB3109103  with Code 80073712

Security Update for Windows 7 for x64-based Systems (KB3109103)


Thank for any help you can provide
Omni


Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9239
  • Location: UK
  • Karma: 117
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #9 on: January 03, 2016, 08:45:53 PM »
Error Code 80073712 is directly related to the corrupt Manifest.

A sfc /scannow would be the first step and then the SURT, but as it is unable to repair, wait for Julian or Shane to get to you with the zip file for the Packages now that the festive season is over.
Tom.

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #10 on: January 03, 2016, 10:25:13 PM »
SFC doesn't see any issue.

Thank you kindly for the help given Boggin  :artist:

Offline Julian

  • "Cat and Mum Guy"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1320
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #11 on: January 04, 2016, 12:03:02 AM »
wow how did i not upload that! i'm sorry here you go.
Julian

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #12 on: January 05, 2016, 12:39:42 PM »
Julian it is not a big deal, I realized it was the holiday, and I appreciate the volunteer work you guys do here.

Is the file you posted the original file?  or did you rebuild a new one after the changes I went through with Boggin?

Thanks,
Omni

Offline Julian

  • "Cat and Mum Guy"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1320
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #13 on: January 06, 2016, 11:59:54 PM »
files are these one's
C:\Windows\servicing\Packages\Package_2_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3108381_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3108381~31bf3856ad364e35~amd64~~6.1.1.1.mum
Julian

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help
« Reply #14 on: January 07, 2016, 06:00:49 PM »
Thank you Julian.

I was able to repair those files.

I know it is not directly related to Windows Repair but I am still having an issue installing Windows update KB3109103 with the following error details:

---------------------------------------------------------------------------
Security Update for Windows 7 for x64-based Systems (KB3109103)

Installation date: ‎1/‎7/‎2016 5:35 PM

Installation status: Failed

Error details: Code 80073712

Update type: Important
---------------------------------------------------------------------------


Following the recommended repair actions, I ran the DISM tool and the results from the tool are as follow:

CheckSur.log

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-01-07 18:17

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646.manifest   wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075.manifest   wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a.manifest   amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a   
(f)   CSI Manifest All Zeros   0x00000000   winsxs\Manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b.manifest   amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b   

Summary:
Seconds executed: 443
 Found 4 errors
  CSI Manifest All Zeros Total count: 4

Unavailable repair files:
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646.manifest
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b.manifest
------------------------------------------------------------------------------------------

Is there any chance you could help me identify/find the manifest files so that I can use the tool to replace them?

Again thank you for all the assistance

Omni

Offline Shane

  • Top Geek, err uh Dog.
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9280
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: Corrupted Package Files - Need Help (WR issues - Solved)
« Reply #15 on: January 17, 2016, 05:36:55 PM »
I only focused on the packages folder and so i didnt save all the manifest files, I need to start getting thoughs as well, the only downfall is the insane number of files!

My mum and cat file collection is already at 409,301 files, adding manifest files will eaily double it. NTFS file systems do have a max number of file limits. While the limit is around 4 billion files
http://www.ntfs.com/ntfs_vs_fat.htm

You should see how big the MFT gets with just the 1 million files on my system already, I may need to see how the exFAT filesystem would handle it, because the files are just going to keep growing.

This might explain why Microsoft never made a database like this, it is better to download the update itself and extract the files, but a lot of updates get removed and you cant grab them. I may need to try to find another way to fix these such as getting windows to not look for them anymore instead. But that is a whole beast on itself.

Shane
PLEASE EDIT YOUR TOPIC AND PUT (SOLVED) IF YOU ARE ALL FIXED.

(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help (WR issues - Solved)
« Reply #16 on: January 22, 2016, 04:31:28 PM »
Julian

Is there a way to just isolate these?


Unavailable repair files:
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_bcce057ed30b1646.manifest
   winsxs\manifests\wow64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_bd47d2d1ec355075.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.23260_none_b2f3287fb7d48e7a.manifest
   winsxs\manifests\amd64_microsoft-windows-rmcast_31bf3856ad364e35_6.1.7601.19055_none_b2795b2c9eaa544b.manifest

Can you tell me how to look for them?  I do have a clean win7 w/sp1 installation disc.

Thanks Again,
Omni

Offline Julian

  • "Cat and Mum Guy"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1320
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Corrupted Package Files - Need Help (WR issues - Solved)
« Reply #17 on: January 28, 2016, 02:53:57 PM »
okay here are those manifest files you needed. take ownership of this folder C:\Windows\winsxs\Manifests and now put them in C:\Windows\winsxs\Manifests.
Julian

Offline The_Omni

  • Newbie
  • *
  • Join Date: Dec 2015
  • Posts: 10
  • Karma: 0
    • View Profile
Re: Corrupted Package Files - Need Help (WR issues - Solved)
« Reply #18 on: February 09, 2016, 06:09:15 PM »
Thank you Julian,

I will let you know how they worked when I get my hand back on the PC.

Omni