Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - LIGHTTY-1

Pages: [1]
1
Tweaking.com Support & Help / Re: TWEAKING IDENTIFIED AS A VIRUS & HOW ABOUT A BOOTABLE TWEAKING TOOL ???
« on: April 16, 2016, 06:36:37 pm »
Yes, I re-installed Windows Repair..I use FREE AVG AntiVirus- HIGHLY recommended by a Computer repair expert in Wisconsin.. Any other ideas ?? Event Viewer is not very helpful to me. It did show something about the UPnP device host & SSDP Discovery services not started but even after RESTARTING those & setting those to AUTOMATIC- Same issue- Can't go into ANY SAFE MODE ????? I've burndt ISO's onto CD's today which are  bootable Recovery Tools by SOPHOS, AVG, Kaspersky, COMBO FIX, etc. done Scans & nothings being found ??

The last 5 files I see loading in SAFE MODE before I get to the LOG-IN Page are AVG files ( last one being avgidsha.sys ), but thing is, my other Computer ALSO shows the exact same thing but that one gets me into SAFE MODE OK....

2
Tweaking.com Support & Help / TWEAKING IDENTIFIED AS A VIRUS & HOW ABOUT A BOOTABLE TWEAKING TOOL ???
« on: April 16, 2016, 12:54:41 pm »
I suspect a DEEPLY hidden infection on my MBR.. I ran a "bootable" SOPHOS Anti-Virus tool & it showed the "tweaking" program as a "Virus" today.. It apparently cleaned it up though- whichever file was "infected" because subsequent scans did not find it.. THe Tweaking programs I use are still on my desktop so it must've just been a file or files ??

Also, I can't get my computer to go into SAFE MODE with or without NETWORKING Anymore.. I went out of my way to do "Drive cleansing" via Seagate Disc Wizard ( DOD Standards & Quick ), ran Darin's Nuke & Boot a few times, reinstalled my Windows-7 Home Premium & still can't get into SAFE MODE.. I used Tweaking Repair - free version ) in NORMAL mode a few times & SELECTED "fix safe mode" but STILL can't get into SAFE MODE ???? Sometimes it will let me log into SAFE MODE then I see right after it shows "GROUP POLICY CLIENT", it immediately Re-Boots so the Computer starts in NORMAL Mode ???? YOU SHOULD CREATE AN ISO that can be burndt to CD so your program can launch from the DOS MODE for users who can't get into SAFE MODE !!!!

3
General Computer Support / Decompression Error when installing Newer version ???
« on: September 18, 2015, 09:08:33 am »
please see my attachment

4
Tweaking.com Support & Help / Re: 3 KB updates in Windows Packages files
« on: September 04, 2015, 08:30:49 pm »
http://www.tweaking.com/forums/index.php?topic=3600.new;topicseen#new

I did what you recommended per "Julian", but EXACT same issue manifesting ?????

Here's a copy & paste from the Tweaking program from "PRE-SCAN" again-

Scanning Windows Packages Files.
Started at (9/4/2015 8:17:58 PM)

These Files Are Missing: (Total: 84)
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_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_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_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_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_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_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_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_116_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_116_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_117_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_117_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_118_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_118_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_119_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_119_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_120_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_120_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_122_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_122_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_123_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_123_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_124_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_124_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_125_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_125_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_126_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_126_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.cat
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.mum
C:\Windows\servicing\Packages\Package_222_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_222_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_241_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_241_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_243_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_243_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.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_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_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_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_57_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_57_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_58_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_58_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_59_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_59_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_60_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_60_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_61_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_61_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_62_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_62_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_63_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_63_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.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_90_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_90_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_91_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_91_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_for_KB3004375_SP1~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_for_KB3004375_SP1~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.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_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.1.13.cat
C:\Windows\servicing\Packages\Package_for_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.1.13.mum
C:\Windows\servicing\Packages\Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.cat
C:\Windows\servicing\Packages\Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.mum

84 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.

THESE FILES DO NOT KEEP THE REPAIRS FROM WORKING; YOU MAY STILL RUN THE REPAIRS IN THE PROGRAM.

5
Tweaking.com Support & Help / 3 KB updates in Windows Packages files
« on: August 31, 2015, 09:27:12 pm »
I'm having wierd results when I run the "pre-scan" with Windows Repair tool.. Results are copy & pasted below-

The 3 KB Windows updates are NOT even showing in my "installed updates list"...

Scanning Windows Packages Files.
Started at (8/30/2015 10:15:04 PM)

These Files Are Missing: (Total: 84)
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_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_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_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_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_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_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_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_116_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_116_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_117_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_117_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_118_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_118_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_119_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_119_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_120_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_120_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_122_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_122_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_123_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_123_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_124_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_124_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_125_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_125_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_126_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_126_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.cat
C:\Windows\servicing\Packages\Package_1_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.mum
C:\Windows\servicing\Packages\Package_222_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_222_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_241_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_241_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_243_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_243_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.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_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_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_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_57_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_57_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_58_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_58_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_59_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_59_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_60_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_60_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_61_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_61_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_62_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_62_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_63_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_63_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.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_90_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_90_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_91_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_91_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_for_KB3004375_SP1~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_for_KB3004375_SP1~31bf3856ad364e35~amd64~~6.1.3.1.mum
C:\Windows\servicing\Packages\Package_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.cat
C:\Windows\servicing\Packages\Package_for_KB3004375~31bf3856ad364e35~amd64~~6.1.3.1.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_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.1.13.cat
C:\Windows\servicing\Packages\Package_for_KB3035583_RTM~31bf3856ad364e35~amd64~~6.1.1.13.mum
C:\Windows\servicing\Packages\Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.cat
C:\Windows\servicing\Packages\Package_for_KB3035583~31bf3856ad364e35~amd64~~6.1.1.13.mum

84 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.

6
General Computer Support / Windows Tweaking NOT helping me much...
« on: September 22, 2014, 11:06:20 am »
 One time a Microsoft tech was on the phone with me & he used Windows tweaking tool to try to repair a System Restore inoperability but it NEVER worked..

I been using it ALOT lately to look for errors on my drives & it seems to find errors alot & after rebooting to FIX disk check, the Errors STILL remain. I use Seagate hard drives alot & when I run Sea Tools for DOS or even Easeus Partition Home Master, those programs DON'T find errors on my drives ?? Also, Windows Tweaker does NOT help when I lose an internet connection & can't restart the Windows Firewall ( that's also the one where you get the "TCP Failed to query the host" thinggy whereby you do a Winsock Reset, & cmd prompt of netsh winsock reset, etc. ).... The control panel will also show 2 Network connections Icons in XP Control Panel !!!!! )...

Pages: [1]