Main Forum > General Computer Support
Windows 7 Update Errors
oboist1:
I keep getting Windows 7 update errors. Per a Tweaking analysis, I need to replace these files:
These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 51)
C:\Windows\servicing\Packages\Package_1_for_KB3013531~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3020369~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3020370~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_2_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_3_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_3_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_4_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_5_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_7_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB3013531_SP1~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB3013531~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB3020369_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3020369~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3020370_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3020370~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3045171_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB3045171~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB3045645_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3046002_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB3051768_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3013531~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3020369~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3020370~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3013531_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB3013531~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB3020369_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3020369~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3020370_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3020370~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3045645_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3045645~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3046002_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3046002~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3051768_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3051768~31bf3856ad364e35~amd64~~6.1.1.0.mum
│
51 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.
Is there a a simple way to replace these files manually w/o a fresh Win 7 install ? I am only a little computer tech savvy. I may update to Win 10 as I have on my other laptop. But I feel Win 7 is cleaner and easier to use. I'm trying to hold off on Win 10 for now.
Thanks for your help !
Steve
Boggin:
Julian will upload those for you and show you how to install them - but probably not until tomorrow unless Shane has time to pop in as he's been quite busy updating his programs.
oboist1:
Great, thanks for your quick reply.
No hurry at all.
I am concerned a virus may have disabled the updates to maintain "control". So, I have run several anti-virus programs including Bitdefender, Malwarebytes and MSE (Windows Defender). BitDefender is the only program that found "viruses". It claimed that the "infections" are harmless.
Steve
Julian:
I found the files for you and uploaded them here is a quote from one of Shane's previous posts on another thread about the steps to take to apply these files.
--- Quote from: Shane on August 11, 2015, 11:42:23 am ---
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 my pre-scan again, put a check on the box to have it add the cat files back to the database. :wink:
Shane
--- End quote ---
(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:
oboist1:
Julian,
That worked great, thanks. I no longer get "shut-down" requests followed by "one update".
Now, I get a "Windows Update Error 80073712".
I Googled the error and it comes up with all kinds of Microsoft and third party suggestions.
I tried these:
Mr FixIt.
Windows Update Error Correction Tool (forgot the exact name).
Update Windows via disk (not allowed because my PC is OEM - I get "your current op system is more up to date than disk copy" and shuts down.
Clearing the update cache.
And a few I cannot remember.
Nothing works.
Any suggestions ?
Thanks,
Steve
Navigation
[0] Message Index
[#] Next page
Go to full version