Author Topic: Windows Package files corrupt  (Read 3235 times)

0 Members and 1 Guest are viewing this topic.

Offline singularityrs

  • Newbie
  • *
  • Join Date: Aug 2015
  • Posts: 1
  • Karma: 0
    • View Profile
Windows Package files corrupt
« on: August 10, 2015, 09:28:14 AM »
I've been having issues with enabling IE11 lately, so I opened Windows repair and did a pre-scan. It found 124 corrupt files within the Windows Packages folder.

Results:

Code: [Select]
These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 124)
C:\Windows\servicing\Packages\Package_38_for_KB3021952~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_39_for_KB3021952~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3049563_RTM~31bf3856ad364e35~amd64~~11.2.1.0.cat
C:\Windows\servicing\Packages\Package_104_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_105_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_106_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_107_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_108_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_111_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_112_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_113_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_114_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_115_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.10.5.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.12.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3021952~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3036493~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3038314~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3049563~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3058515~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3065822~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2519736~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2536276~31bf3856ad364e35~amd64~~6.1.2.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB2706045~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3032323~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3036493~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3038314~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3046306~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3049563~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_2_for_KB3065822~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3077657~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_37_for_KB3021952~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_37_for_KB3058515~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_38_for_KB3058515~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2706045~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.10.5.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.12.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3032323~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB3038314~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3046306~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_3_for_KB3065822~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB3077657~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_40_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_40_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_40_for_KB3021952~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_40_for_KB3058515~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_41_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_41_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_42_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_48_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_4_for_KB3032359~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_51_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_52_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_53_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_54_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_5_for_KB3032359~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB3038314~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB3049563~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_5_for_KB3065822~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_6_for_KB3032359~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_78_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_78_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_79_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_79_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_79_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_7_for_KB3032359~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_80_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_80_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_81_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_81_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2519736_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2519736~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2536276_SP1~31bf3856ad364e35~amd64~~6.1.2.1.mum
C:\Windows\servicing\Packages\Package_for_KB2536276~31bf3856ad364e35~amd64~~6.1.2.1.mum
C:\Windows\servicing\Packages\Package_for_KB2706045_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2706045~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2909210_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2909210~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2918614_SP1~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB2918614~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.10.5.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.12.0.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.13.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.10.5.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.12.0.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.13.2.mum
C:\Windows\servicing\Packages\Package_for_KB2978668_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2978668~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2994023_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3008627_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3008627~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3021952~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3032323_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3032323~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3032359_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3032359~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3036493_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3036493~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3038314_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3038314~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3046306_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3046306~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3049563_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3049563~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3057839_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3057839~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3058515_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3058515~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3065822_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3065822~31bf3856ad364e35~amd64~~11.2.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3067505_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3067505~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB3077657_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3077657~31bf3856ad364e35~amd64~~6.1.1.0.mum

How would I go about replacing these?

Offline Shane

  • Top Geek, err uh Dog.
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9280
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Re: Windows Package files corrupt
« Reply #1 on: August 10, 2015, 11:46:58 AM »
I will work on getting those files, but those files wouldn't affect IE from working, it would only affect any updates for it.

have you ran the repairs yet and made sure to run them in safe mode?

Shane
PLEASE EDIT YOUR TOPIC AND PUT (SOLVED) IF YOU ARE ALL FIXED.

(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com