Author Topic: .cat and .mum files missing  (Read 2784 times)

0 Members and 1 Guest are viewing this topic.

Offline DougII

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 3
  • Karma: 0
    • View Profile
.cat and .mum files missing
« on: October 12, 2016, 06:53:39 AM »
Hello!
  I have ran the windows repair tool twice and it hasn't helped me being able to open my "turn windows features on or off" window.. it still comes up blank. looking around I guess you have to fix these files. I am not sure how to replace them.. I also cannot get the Microsoft catalogs to open in my IE. anyhow I would appreciate any help.. You guys are the only place I have seen that deals with these files. Thank You in advance for any help!  :smiley:
  Here is my pre-scan log.
P.S. I did manage to get the KB2633952 Update and tried to install it to see if it would take away some of these files. when installing it says it is already installed on this computer, but when I check or search in installed updates it does not find that update.. so a little confused at the moment.


┌────────────────────────────────────────────────────────────────────────────────┐
│ Tweaking.com - Windows Repair v3.9.12 - Pre-Scan
│ Computer: DOUGII-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
│ [Started Scan - 10/11/2016 4:16:29 PM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (10/11/2016 4:16:29 PM)

│ These Files Are Missing: (Total: 204)
C:\Windows\servicing\Packages\Package_110_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_110_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_146_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_146_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_147_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_147_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_148_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_148_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_149_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_149_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_150_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_150_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_151_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_151_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_152_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_152_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_153_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_153_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_154_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_154_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_155_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_155_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_156_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_156_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_157_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_157_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_158_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_158_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_159_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_159_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_160_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_160_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_161_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_161_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_162_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_162_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_163_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_163_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_164_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_164_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_165_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_165_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_166_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_166_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_167_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_167_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_168_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_168_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_169_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_169_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_170_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_170_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_171_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_171_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_172_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_173_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_174_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_175_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_176_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_177_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_178_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_179_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_180_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2859903~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2859903~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_217_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_217_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_237_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_237_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_253_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_253_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_254_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_254_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2286198~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB2286198~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB2984981~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_37_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_37_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB979916~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_57_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_57_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_5_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_5_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_73_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_73_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_74_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_74_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_7_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_7_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB2286198_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB2286198_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2286198~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB2286198~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB2345886_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB2345886~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB2416471_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2416471_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2518867_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2518867~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2522422_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2522422_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2539634_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2539634_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2539634~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2633952_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2633952_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2633952_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2633952_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2633952~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2656373_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2656373_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2859903_RTM~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2859903_RTM~31bf3856ad364e35~amd64~~10.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2859903~31bf3856ad364e35~amd64~~10.2.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2859903~31bf3856ad364e35~amd64~~10.2.1.0.mum

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

│ Files Checked & Verified: 10,129

│ Done Scanning Windows Packages Files.(10/11/2016 4:26:36 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Reparse Points.
│ Started at (10/11/2016 4:26:36 PM)

│ Reparse Points are OK!.

│ Files & Folders Searched: 436,095
│ Reparse Points Found: 63

│ Done Scanning Reparse Points.(10/11/2016 4:31:47 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Checking Environment Variables.
│ Started at (10/11/2016 4:31:47 PM)

│ No problems were found with the Environment Variables.

│ Done Checking Environment Variables. (10/11/2016 4:31:48 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ [Finished Scan - 10/11/2016 4:31:48 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.

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

Offline DougII

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 3
  • Karma: 0
    • View Profile
(Update) .cat and .mum files missing
« Reply #1 on: October 14, 2016, 12:23:03 PM »
Hello again!

Ok.... So I finally figured out how to replace most of the files. I downloaded the Update Readiness Tool and ran it.. I then Downloaded all the update packages on log report.  I then went to c:>windows>Checksur>packages (I had to create the packages folder) I then copied all of the Updates to that folder and ran the Readiness tool again and rebooted.  checked the Cheksur log and most of the files were fixed.  So the ones not fixed I figured I retrieved the wrong package update. I then retrieved different updates and ran Readiness tool again.  This time it fixed more.  I have Ran the Readiness tool several times and rebooted (have even done a power reset)  Still not fixing! I am down to only 10 files (long ways from 204) now and and just cannot get these to be repaired.  I am guessing that this KB2656373 package does not have the files?  :undecided: I have downloaded several different ones and ran Readiness again to no avail at fixing. I have tried to install the update and keep getting that it is already installed on my computer.
  I do not know if there is another way to fix this? Guess I will wait for an expert here to help now!  I have attached a screenshot of what I have downloaded.  Any help would be greatly appreciated, as I am out of ideas now!  :confused:
 
  Thanks again for any and all Guidance or Ideas on this matter!

┌────────────────────────────────────────────────────────────────────────────────┐
│ Tweaking.com - Windows Repair v3.9.12 - Pre-Scan
│ Computer: DOUGII-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
│ [Started Scan - 10/13/2016 5:12:22 PM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (10/13/2016 5:12:22 PM)

│ These Files Are Missing: (Total: 10)
C:\Windows\servicing\Packages\Package_1_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_4_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2656373_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2656373_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2656373~31bf3856ad364e35~amd64~~6.1.1.0.mum

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

│ Files Checked & Verified: 10,323

│ Done Scanning Windows Packages Files.(10/13/2016 5:22:00 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Reparse Points.
│ Started at (10/13/2016 5:22:00 PM)

│ Reparse Points are OK!.

│ Files & Folders Searched: 437,637
│ Reparse Points Found: 63

│ Done Scanning Reparse Points.(10/13/2016 5:23:02 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Checking Environment Variables.
│ Started at (10/13/2016 5:23:02 PM)

│ No problems were found with the Environment Variables.

│ Done Checking Environment Variables. (10/13/2016 5:23:02 PM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ [Finished Scan - 10/13/2016 5:23:02 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.

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

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6602
  • Location: UK
  • Karma: 100
    • View Profile
Re: .cat and .mum files missing
« Reply #2 on: October 14, 2016, 02:52:11 PM »
I've contacted Shane and Julian to see if I can get you help with those, but with it being a weekend, that may be slow in coming.

Offline DougII

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 3
  • Karma: 0
    • View Profile
Re: .cat and .mum files missing
« Reply #3 on: October 14, 2016, 09:55:56 PM »
Thank You Boggin
  I understand you guys have lives too and do this on a volunteer basis.  I am used to waiting for replies.  I have gotten help on Computerhopes forum quite a few times over the years and have waited over two weeks for a reply.  I am just grateful there is sites like this to help me with problems.  I usually do research and try to fix things on my own until I just break down and figure I need help from someone knowledgeable on the subject.  I have learned a lot over the years and I still seem to be a Newbie all the time on comps, even if my family all call me there Tech..LOL  Have a great weekend! :wink:

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 6602
  • Location: UK
  • Karma: 100
    • View Profile
Re: .cat and .mum files missing
« Reply #4 on: October 15, 2016, 02:19:08 AM »
Well I've never done what you have done with the Package files, so you're one up on me :D

It's not often that I'm stuck either as I can usually find a solution to my problems.

 

anything