Good morning Shane! Great site and stuff here...thank you so very much for all you do!!!
I have a Windows 7 64-bit system. Ran pre-scan once...found errors. Ran COMPLETE Scandisk f/r. Then system file check. Rebooted. Cleared prefetch, rebooted to Safemode/network with clean start.
Then ran Pre-Scan again. This is what I still have after above repairs (some accomplished) were done.
So, with great dignity and respect!, what is best to do now? Windows update is loading, and installing occasionally...but not "right". Otherwise my system is pretty danged clean. Wondering if others had problems with Windows Updates, starting about mid-April!!!
Tweaking.com - Windows Repair - Pre-Scan
Computer: GUURUU (Windows 7 Home Premium 6.1.7601 Service Pack 1) (64-bit)
Started at (5/26/2015 10:02:34 AM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (5/26/2015 10:02:34 AM)
These Files Are Missing: (Total: 66)
C:\Windows\servicing\Packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_102_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_102_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_102_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_103_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_103_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_103_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_104_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_104_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_104_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_105_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_105_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_105_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_108_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_108_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_108_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_109_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_109_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_109_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_110_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_110_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_110_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_111_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB2993958~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_2_for_KB2993958~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_49_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_49_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_49_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_49_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_50_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_50_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_50_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_50_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_51_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_51_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_51_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_51_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_52_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_52_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_52_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_52_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_77_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_77_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_77_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_77_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2993958_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2993958_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB2993958~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2993958~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3023607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3023607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3023607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3046049_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3046049_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3046049~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3046049~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: 3,605
Done (5/26/2015 10:04:45 AM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (5/26/2015 10:04:45 AM)
No problems were found with the Reparse Points.
Files & Folders Searched: 126,216
Reparse Points Found: 47
Done (5/26/2015 10:04:49 AM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (5/26/2015 10:04:49 AM)
No problems were found with the Environment Variables.
Done (5/26/2015 10:04:49 AM)
--------------------------------------------------------------------------------
Done (5/26/2015 10:04:49 AM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Done (5/26/2015 10:04:49 AM)
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.
