Author Topic: Pre-scan - 121 missing cat and 1 corrupt mum (solved)  (Read 6901 times)

0 Members and 1 Guest are viewing this topic.

Offline macroman68

  • Newbie
  • *
  • Join Date: Oct 2015
  • Posts: 2
  • Karma: 0
    • View Profile
Pre-scan - 121 missing cat and 1 corrupt mum (solved)
« on: October 10, 2015, 04:19:02 AM »
Hi, I've been trying to upgrade a 64-bit Windows 7 Home computer to Windows 10, but the process fails and rolls back win Win7. Putting the Win10 upgrade to the side for the moment, I've tried just running Windows Update, but that too fails. The pre-scan from Windows Repair shows 121 missing .cat files, and 1 corrupt .mum file. I'm clueless as to why and how that many are missing.

Can this many files be replaced somehow? Let me know if more info is needed. Appreciate any advice anyone may have.

┌────────────────────────────────────────────────────────────────────────────────┐
│ Tweaking.com - Windows Repair v3.6.0 - Pre-Scan
│ Computer: USERT-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
│ [Started Scan - 10/10/2015 8:06:44 PM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (10/10/2015 8:06:44 PM)

│ These Files Are Missing: (Total: 121)
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~9.4.8112.16421.cat
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~9.4.8112.16421.cat
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Package-MiniLP~31bf3856ad364e35~amd64~en-US~9.4.8112.16421.cat
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Package-TopLevel~31bf3856ad364e35~amd64~~9.4.8112.16421.cat
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~en-US~9.4.8112.16421.cat
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-Package~31bf3856ad364e35~amd64~~9.4.8112.16421.cat
C:\Windows\servicing\Packages\Microsoft-Windows-InternetExplorer-VistaPlus-Update~31bf3856ad364e35~amd64~~9.4.8112.16421.cat
C:\Windows\servicing\Packages\Package_1_for_KB2530548~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2559049~31bf3856ad364e35~amd64~~9.4.1.3.cat
C:\Windows\servicing\Packages\Package_1_for_KB2586448~31bf3856ad364e35~amd64~~9.4.1.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2618444~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2647516~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2675157~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2719177~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2722913~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2744842~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2761451~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2761465~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2792100~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2797052~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2829530~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2838727~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2846071~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2847204~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2862772~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2870699~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2888505~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2898785~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2909921~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2925418~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2936068~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2953522~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2957689~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2962872~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2964358~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2976627~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2719177~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2722913~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2744842~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2761451~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2761465~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2792100~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2829530~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2838727~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2846071~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2862772~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2870699~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2888505~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2898785~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2909921~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2925418~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2936068~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2957689~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2962872~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2976627~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2530548_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2530548~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2559049_RTM~31bf3856ad364e35~amd64~~9.4.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB2559049~31bf3856ad364e35~amd64~~9.4.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB2586448_RTM~31bf3856ad364e35~amd64~~9.4.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB2586448~31bf3856ad364e35~amd64~~9.4.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB2618444_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2618444~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2647516_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2647516~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2675157_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2675157~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2699988_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2719177_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2719177~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2722913_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2722913~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2744842_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2744842~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2761451_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2761451~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2761465_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2761465~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2792100_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2792100~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2797052_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2797052~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2829530_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2829530~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2838727_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2838727~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2846071_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2846071~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2847204_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2847204~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2862772_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2862772~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2870699_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2870699~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2879017_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2888505_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2888505~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2898785_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2909921_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2909921~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2925418_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2925418~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2936068_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2936068~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2953522_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2953522~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2957689_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2957689~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2962872_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2962872~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2964358_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2964358~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2976627_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2976627~31bf3856ad364e35~amd64~~9.4.1.0.cat

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

122 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,536

│ Done Scanning Windows Packages Files.(10/10/2015 8:08:50 PM)
└────────────────────────────────────────────────────────────────────────────────┘
« Last Edit: October 17, 2015, 04:43:00 PM by macroman68 »

Offline Julian

  • "Professional Googler"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1325
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Pre-scan - 121 missing cat and 1 corrupt mum
« Reply #1 on: October 10, 2015, 01:08:57 PM »
hmmm apparently i don't have those 122 in my data base of 40k cat and mum files lol let me go manually download them and see.
Julian

Offline RaveRocks

  • Newbie
  • *
  • Join Date: Sep 2015
  • Posts: 37
  • Location: Vancouver, BC Canada
  • Karma: 0
    • View Profile
Re: Pre-scan - 121 missing cat and 1 corrupt mum
« Reply #2 on: October 10, 2015, 06:57:55 PM »
Someone has 121 missing cats AND a corrupt mum ? Think of the cat food you're not having to buy.
You'll find me on Twitter and You-Tube but never again on Facebook. My first computer was a $99 TI-994a. By the end of the first day, I was able to write and save the Oscar Myer Weiner song.  If only today's goals were so simple.

Offline Julian

  • "Professional Googler"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1325
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Pre-scan - 121 missing cat and 1 corrupt mum
« Reply #3 on: October 10, 2015, 09:04:20 PM »
Someone has 121 missing cats AND a corrupt mum ? Think of the cat food you're not having to buy.
Lol that was a good one.
Julian

Offline Rick

  • Hero Member
  • *****
  • Join Date: May 2013
  • Posts: 829
  • Karma: 2
    • View Profile
Re: Pre-scan - 121 missing cat and 1 corrupt mum
« Reply #4 on: October 12, 2015, 05:12:39 PM »
I would suggest try 360

http://www.360totalsecurity.com/

*** In windows update, be sure disable all updates, Manually and otherwise
*** in 360, be sure not to enable disable updates ...

regards

Offline Shane

  • Lead Developer - Coder
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9279
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: Pre-scan - 121 missing cat and 1 corrupt mum
« Reply #5 on: October 13, 2015, 03:15:30 AM »
I think i know the problem and why none of the files are in the file database we have been keeping.

I checked and as an example KB2957689 is in the list, well this was a bad update from MS and they pulled it. So this is why it isnt pulling up for us.

I am willing to be that is the story behind most of them.

Both my program and windows look at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages

To know what files are inside the packages folder. So since these where bad updates 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 my program and windows 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.

Shane

Offline Rick

  • Hero Member
  • *****
  • Join Date: May 2013
  • Posts: 829
  • Karma: 2
    • View Profile
Re: Pre-scan - 121 missing cat and 1 corrupt mum
« Reply #6 on: October 13, 2015, 07:37:13 PM »
I think i know the problem and why none of the files are in the file database we have been keeping.

I checked and as an example KB2957689 is in the list, well this was a bad update from MS and they pulled it. So this is why it isnt pulling up for us.

I am willing to be that is the story behind most of them.

Both my program and windows look at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages

To know what files are inside the packages folder. So since these where bad updates I think the best thing to do would be to remove those file entries from that registry location.

First; BACKUP THE REGISTRY BEFORE MAKING ANY CHANGES !

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, remove the items and then reboot and see how it goes.

by removing them from that registry location both my program and windows 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.

Shane

Offline Julian

  • "Professional Googler"
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jun 2015
  • Posts: 1325
  • Location: USA, New Mexico
  • Karma: 38
    • View Profile
Re: Pre-scan - 121 missing cat and 1 corrupt mum
« Reply #7 on: October 14, 2015, 12:22:33 AM »
Ah that makes sense I was like what is going on! lol
Julian

Offline macroman68

  • Newbie
  • *
  • Join Date: Oct 2015
  • Posts: 2
  • Karma: 0
    • View Profile
Re: Pre-scan - 121 missing cat and 1 corrupt mum (solved)
« Reply #8 on: October 17, 2015, 04:49:09 PM »
Thanks for the tips Shane, cleaning up those registry items led me in the right direction. Windows Repair reports no further problems. Windows Update still has issues, but I've since found out the HD has too many bad sectors. It's not worth continuing with it, so time for a new one.  Thanks again.