Author Topic: Missing Windows Packages files  (Read 4606 times)

0 Members and 1 Guest are viewing this topic.

Offline stabbim

  • Newbie
  • *
  • Join Date: Mar 2016
  • Posts: 3
  • Karma: 0
    • View Profile
Missing Windows Packages files
« on: March 07, 2016, 05:14:59 PM »
Hello!

This is my first post here but I've used the Windows Repair utility many times and it's solved a lot of problems I would have considered lost causes , so thank you!

In this case, the pre-scan has found some missing packages files. The reason I'm even working on this machine is that it's having trouble installing some updates, and I have no doubt this is the main reason. Here's the list, it's fairly long:

Code: [Select]
C:\windows\servicing\Packages\Package_117_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_117_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_118_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_118_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_119_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_119_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_120_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_120_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_121_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_121_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_123_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_123_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_124_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_124_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_125_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_125_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_126_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_126_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_127_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_127_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_1_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\windows\servicing\Packages\Package_1_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\windows\servicing\Packages\Package_2_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\windows\servicing\Packages\Package_2_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\windows\servicing\Packages\Package_38_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_38_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_3_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\windows\servicing\Packages\Package_3_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\windows\servicing\Packages\Package_4_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\windows\servicing\Packages\Package_4_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\windows\servicing\Packages\Package_58_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_58_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_59_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_59_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_5_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\windows\servicing\Packages\Package_5_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\windows\servicing\Packages\Package_60_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_60_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_61_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_61_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_62_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_62_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_63_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_63_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_64_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_64_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_91_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_91_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_92_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_92_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\windows\servicing\Packages\Package_for_KB3097989_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\windows\servicing\Packages\Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\windows\servicing\Packages\Package_for_KB3097989~31bf3856ad364e35~amd64~~6.1.1.1.mum

│ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 6)
C:\windows\servicing\Packages\Package_for_KB2972100~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_for_KB3060716_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\windows\servicing\Packages\Package_for_KB2972100~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_for_KB3060716_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\windows\servicing\Packages\Package_for_KB3060716~31bf3856ad364e35~amd64~~6.1.1.0.mum

I've seen a few cases posted on these forums where folks were able to provide the missing files, if anyone would be so kind I'd appreciate it. I'm already aware of how to copy the files into the appropriate place and add them back to the catalogue (I think).

Or, if it's possible to simply copy them from one of my other PCs, I can try it. MS claims that won't work, but maybe that's just because the don't take this software into account?

Online Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 8833
  • Location: UK
  • Karma: 114
    • View Profile
Re: Missing Windows Packages files
« Reply #1 on: March 08, 2016, 02:19:39 AM »
I'll move your thread to the Cat And Mum File Requests section where Julian or Shane will pick it up when they can manage to get onto the forum, as they have been quite busy with their day jobs.

Does it report the first lot as missing with the second lot as bad signatures ?
Tom.

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: Missing Windows Packages files
« Reply #2 on: March 08, 2016, 12:11:08 PM »
First grab the zip file off this page and apply the reg file it in 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. :cheesy:

(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 stabbim

  • Newbie
  • *
  • Join Date: Mar 2016
  • Posts: 3
  • Karma: 0
    • View Profile
Re: Missing Windows Packages files
« Reply #3 on: March 14, 2016, 04:33:20 PM »
My apologies, I forgot to come back and check this thread for a while.

Boggin: Yes, you had that correct. First group missing entirely, second group present but apparently incorrect signatures.

Julian: Trying those files now.

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: Missing Windows Packages files
« Reply #4 on: March 14, 2016, 10:41:01 PM »
Awesome let me know
Julian

Offline stabbim

  • Newbie
  • *
  • Join Date: Mar 2016
  • Posts: 3
  • Karma: 0
    • View Profile
Re: Missing Windows Packages files
« Reply #5 on: March 22, 2016, 01:47:12 PM »
Looking good. Prescan now shows no issues with packages. After repairing Windows Update, I have been able to install the vast majority of updates which had previously been failing.

I only have 3 failing now and they're all with .Net framework so I'm confident that's a separate issue. Thanks very much for your assistance, 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: Missing Windows Packages files
« Reply #6 on: March 25, 2016, 03:25:44 AM »
woot no problem glad it is fixed!
Julian