Author Topic: 73 Missing Files (Windows 7 Home Premium 6.1.7601 - Service Pack 1 - 64-bit)  (Read 4112 times)

0 Members and 1 Guest are viewing this topic.

Offline brandon.barwick

  • Newbie
  • *
  • Join Date: Apr 2016
  • Posts: 1
  • Karma: 0
    • View Profile
Hello Shane and everyone. I tend to be a long-winded fellow, and I don't want to pain anyone with my silliness; I will aim to stay on topic and totally germane. First, thank you for creating and furthering this site! My appreciation is multitudinous. Windows Update has failed on my HP laptop for two months. I've learned more about computers since February than I did in my first 31 years of being. I've spent an embarrassing amount of time trying to resolve this problem; hundreds of hours, for certain. My delving into my PC has caused added problems at various times; however, I do believe I'm finally on the right track and nearing the resolution of this 60-day obstacle, largely because of this website. Thank you.

Here are the 3 Windows Updates that have failed each time I tried to update, since February 9 (release date, I believe):
1. Security Update for Windows 7 for x64-based Systems (KB3126587) - size: 29.2 MB
2. Security Update for Windows 7 for x64-based Systems (KB3126593) - size: 29.5 MB
3. Security Update for Windows 7 for x64-based Systems (KB3140410) - size: 28.0 MB

Occasionally, a different Error Code would accompany the Fail, and I aimed to keep record and research each one, but this is the primary Error, which I've seen posted about on this website, I've followed several different steps, downloaded various folders and files; however, I have not located the files that my PC is missing (I think, unless I'm overlooking something). They might be easy to find or not; I'm not totally sure. Here's the Error Code I've experienced a couple hundred times from Windows Update:

Error Code 80070490 - Windows Update Encountered an unknown error.

I won't list all the things I've done to try and fix it, mainly because it's (I think) pretty much everything Windows, Microsoft, HP, intelligent websites, not-so-intelligent websites, and a slew of troubleshooters, programs, and other pertinent apps suggested I try. In a way, I feel bad listing the 73 missing files because of the space it takes, but I think that's probably important. Here they are:

C:\Windows\servicing\Packages\Package_117_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_117_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_117_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_117_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_118_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_118_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_119_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_119_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_120_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_120_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_121_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_121_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_123_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_123_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_124_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_124_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_125_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_125_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_126_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_126_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_127_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_127_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_38_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_38_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_39_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_39_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB2977629~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_40_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_40_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_41_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_41_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_58_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_58_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_59_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_59_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_60_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_60_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_61_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_61_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_62_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_62_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_63_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_63_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_64_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_64_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_91_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_91_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_92_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_92_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.14.2.mum
C:\Windows\servicing\Packages\Package_for_KB3069392_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3069392_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3069392~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3101746_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3101746_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3101746~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3102429_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3102429_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3102429~31bf3856ad364e35~amd64~~6.1.1.0.mum

I followed Shane's directions from a 6/4/2015 post that appears to be similar to my issues but lists some different files than what's listed above. I think I correctly attained the Take Ownership and Cat/Mum folders and files and I've been prompted to enter files back into the registry, which I believe I completed without screwing anything up, so it feels like I'm super close to achieving this. However, I can't seem to find all of these files listed above. I'll keep looking around this site, in my recent downloads from the site, and other places, and I hope to hear back at your convenience. Thank you again; I am indebted! -Brandon (608) 312-8134

(P.S. I think this is my first time ever posting to a computer-affiliated forum, and I might have left out some key data that you need. I'm on computers most of the day, so if I receive any replies/messages, I should be able to get right back to you. I have documents galore, both tangible and electronic, associated to this HP repair endeavor. It's been a wild ride. Thanks!)

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 8959
  • Location: UK
  • Karma: 114
    • View Profile
I'll move your thread to the Cat and Mum File Requests section so that either Shane or Julian will pick it up, but of all of the update error codes, you had to go and pick that one.

This is what MS have for that and other error codes but they didn't work for another forum member who had the same error code.

https://support.microsoft.com/en-us/kb/2509997

After having the missing/corrupt packages uploaded and installed, the member installed AVG which bundled a tune up program which sorted it - but a lot of the time, those with that update error have had to reinstall/factory reset.

However, if your restore points go back to before the main batch of updates installed, try those to before their install - redo the Pre-Scan to see if it still reports Package File corruption and if not, reinstall the updates.
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
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