Show Posts
1
General Computer Support / missing 60 windows packages
« on: July 16, 2015, 02:21:31 pm »
Have 60 packages that are missing. Have previously run tweaking and sfc still missing all the packages. Windows update kept showing I had good updates but then would show that the same ones need downloading and installation. I think this is the result of those downloads. Need help in fixing before I run tweaking again. Thanks
Pre-Scan
Computer: JOHN-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
Started at (7/16/2015 5:01:31 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (7/16/2015 5:01:31 PM)
These Files Are Missing: (Total: 60)
C:\Windows\servicing\Packages\Package_116_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_116_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_117_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_117_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_13_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_13_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_142_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_142_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_143_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_143_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_144_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_144_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_145_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_145_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_146_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_146_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_148_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_148_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_149_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_149_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_14_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_14_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_150_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_150_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_151_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_151_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_152_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_152_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_38_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_38_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_58_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_58_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_59_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_59_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_73_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_73_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_74_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_74_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_84_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_84_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_85_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_85_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_86_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_86_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_87_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_87_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_88_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_88_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_89_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_89_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3050265_SP1~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_for_KB3050265_SP1~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_for_KB3068708_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3068708_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
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: 4,697
Done (7/16/2015 5:03:32 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (7/16/2015 5:03:32 PM)
No problems were found with the Reparse Points.
Files & Folders Searched: 553,245
Reparse Points Found: 113
Done (7/16/2015 5:07:27 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (7/16/2015 5:07:27 PM)
This folder in the 'Path' variable doesn't exist: C:\Program Files (x86)\AMD APP\bin\x86_64
Problems were found with the Environment Variables.
You can use the Repair Environment Variables Tool at the bottom of this Window to try and fix these problems.
Done (7/16/2015 5:07:27 PM)
--------------------------------------------------------------------------------
Done (7/16/2015 5:07:27 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Done (7/16/2015 5:07:27 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.
If you need help fixing any of the items in the log, just post in the forums at Tweaking.com for help.
Pre-Scan
Computer: JOHN-PC (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
Started at (7/16/2015 5:01:31 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (7/16/2015 5:01:31 PM)
These Files Are Missing: (Total: 60)
C:\Windows\servicing\Packages\Package_116_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_116_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_117_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_117_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_13_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_13_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_142_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_142_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_143_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_143_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_144_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_144_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_145_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_145_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_146_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_146_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_148_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_148_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_149_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_149_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_14_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_14_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_150_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_150_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_151_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_151_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_152_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_152_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_38_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_38_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_58_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_58_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_59_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_59_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_73_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_73_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_74_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_74_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_84_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_84_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_85_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_85_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_86_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_86_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_87_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_87_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_88_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_88_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_89_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_89_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3050265_SP1~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_for_KB3050265_SP1~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.cat
C:\Windows\servicing\Packages\Package_for_KB3050265~31bf3856ad364e35~amd64~~6.1.1.9.mum
C:\Windows\servicing\Packages\Package_for_KB3068708_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3068708_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.mum
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: 4,697
Done (7/16/2015 5:03:32 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (7/16/2015 5:03:32 PM)
No problems were found with the Reparse Points.
Files & Folders Searched: 553,245
Reparse Points Found: 113
Done (7/16/2015 5:07:27 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (7/16/2015 5:07:27 PM)
This folder in the 'Path' variable doesn't exist: C:\Program Files (x86)\AMD APP\bin\x86_64
Problems were found with the Environment Variables.
You can use the Repair Environment Variables Tool at the bottom of this Window to try and fix these problems.
Done (7/16/2015 5:07:27 PM)
--------------------------------------------------------------------------------
Done (7/16/2015 5:07:27 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Done (7/16/2015 5:07:27 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.
If you need help fixing any of the items in the log, just post in the forums at Tweaking.com for help.