Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: Shane on April 11, 2013, 01:54:26 pm
-
8024402c means it had trouble talking to the windows update servers. And I have always found it to be DNS related.
My fix is to have the system use the google dns servers 8.8.8.8 and 8.8.4.4
This bug is on my own ISP. When I used their DNS every single machine in my house and office would fail with this error. As soon as I changed dns servers they all worked. I tried to let my ISP know but they just ignored me lol
To make changing your DNS servers easier I made a program that will do it for you :-)
http://www.tweaking.com/content/page/tweaking_com_change_dns_servers.html
So try the dns trick and see how it does :wink:
Shane
-
cool..
-
Hello once again,and thank you for your answer
i got this error, i reboot the pc, but still, same error
Extracting files to C:\Users\Dora\SkyDrive\Documentos\Programas folder
Cannot create Tweaking.com - Change DNS Servers\Change_DNS_Servers.exe
i put the first dns 8888 and 2nd 8884, manualy, but didn´t work either, i´m on a company network...
any ideas?
Thank you in advance
-
ok i manage to start the application, i "use google dns" enable it, same error, and when i used open dns, enable it, and nothing happen, same error
now i haven´t got any ideas...
-
hello again, well i try every single possible fix, for this, and i can´t be successful
1st - delete softwaredistribution folder - nothing
2nd - delete all *.net updates - nothing
3rd - windows self updater - nothing
4th - tweaking windows - nothing
5th - Microsoft fix it - nothing
6th - tweak dns - nothing
7th - removing windows malicious software - nothing and 0 threats
8th - anti virus scan - nothing to report
9th - TDSKILLER - nothing to report
10th - turn of firewall - nothing
please help! :) sorry guys...and thank you in advance
-
ok ppl i solved my problem installing again. net framework versions - 1, 2 (not compatible with vista), 3.5, 4 (gave me an error), 4.5 and finally worked.
Thanks either way
-
That solved the problem for me. Thank you for the great help!
-
It's also possible that the elevated command of netsh winsock reset will resolve it as well.
-
:cheesy:
Shane,
again thx for the solution.
i used the DNS from open DNS.
untill now never had any problem.
grz
Peter
-
Hello,
I am having the same issue, but need more files. Can anyone help. Running win7 64bit.
Tony
Tweaking.com - Windows Repair v3.2.2 - Pre-Scan
Computer: DEVELOPMENT-PC (Windows 7 Professional 6.1.7601 Service Pack 1) (64-bit)
Started at (22/06/2015 6:39:30 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Windows Packages Files.
Started at (22/06/2015 6:39:30 PM)
These Files Are Missing: (Total: 306)
C:\Windows\servicing\Packages\Package_102_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_102_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_103_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_103_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_103_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_103_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_104_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_104_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_105_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_105_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_108_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_108_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_109_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_109_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_109_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_109_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_110_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_110_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_110_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_110_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_111_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_111_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_112_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_112_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_113_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_113_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_113_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_113_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_114_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_114_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_114_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_114_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_116_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_116_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_117_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_117_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_118_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_118_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_119_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_119_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_120_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_120_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_122_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_122_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_123_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_123_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_124_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_124_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_125_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_125_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_126_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_126_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_134_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_134_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_135_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_135_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_136_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_136_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_137_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_137_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_138_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_138_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_139_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_139_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_140_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_140_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.mum
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
C:\Windows\servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
C:\Windows\servicing\Packages\Package_1_for_KB3001554~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_1_for_KB3001554~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_1_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_1_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_1_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_21_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_21_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_29_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_29_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_29_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_29_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_2_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_2_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_2_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_2_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_2_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_2_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_2_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_2_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_2_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_30_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_30_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_30_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_30_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_31_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_31_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_31_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_31_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_32_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_32_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_32_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_32_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_33_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_33_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_33_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_38_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_38_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_39_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_39_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_39_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_39_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
C:\Windows\servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
C:\Windows\servicing\Packages\Package_3_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_3_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_3_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_3_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_3_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_3_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_3_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_3_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_3_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_40_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_40_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_45_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_45_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_49_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_49_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_49_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_49_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_4_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_4_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_4_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_4_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_50_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_50_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_50_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_50_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_51_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_51_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_51_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_51_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_52_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_52_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_56_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_56_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_56_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_56_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_57_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_57_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_57_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_57_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_57_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_57_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_58_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_58_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_58_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_58_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_58_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_58_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_59_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_59_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_59_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_59_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_59_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_59_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_60_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_60_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_61_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_61_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_62_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_62_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_63_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_63_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_6_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_6_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_6_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_6_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_73_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_73_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_74_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_74_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_74_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_74_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_75_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_75_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_76_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_76_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_76_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_76_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_77_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_77_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_7_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_7_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_90_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_90_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_90_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_90_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_91_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_91_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_91_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_91_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_92_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_92_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_93_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_93_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_94_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_94_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_95_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_95_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_for_KB2949927_SP1~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_for_KB2949927_SP1~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.cat
C:\Windows\servicing\Packages\Package_for_KB2949927~31bf3856ad364e35~amd64~~6.1.1.5.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.7.4.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.7.4.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.8.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.8.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.9.6.cat
C:\Windows\servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.9.6.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.6.1.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.7.4.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.8.2.mum
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
C:\Windows\servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
C:\Windows\servicing\Packages\Package_for_KB2984976_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB2984976_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.cat
C:\Windows\servicing\Packages\Package_for_KB2984976~31bf3856ad364e35~amd64~~6.1.1.3.mum
C:\Windows\servicing\Packages\Package_for_KB2998527_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB2998527_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB2998527~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3001554_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3001554_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3001554~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3001554~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3002885_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3002885_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3002885~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3004394_SP1~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB3004394_SP1~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.cat
C:\Windows\servicing\Packages\Package_for_KB3004394~31bf3856ad364e35~amd64~~6.1.2.0.mum
C:\Windows\servicing\Packages\Package_for_KB3005607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3005607_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3005607~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3006226_SP1~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_for_KB3006226_SP1~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_for_KB3006226~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB3009736_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3009736_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3009736~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3013126_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3013126_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3013455_SP1~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_for_KB3013455_SP1~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_for_KB3013455~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_for_KB3023266_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3023266_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3023266~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3023562_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3023562_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.cat
C:\Windows\servicing\Packages\Package_for_KB3023562~31bf3856ad364e35~amd64~~6.1.1.2.mum
C:\Windows\servicing\Packages\Package_for_KB3029944_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3029944_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3029944~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3031432_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3031432_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB3031432~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Package_for_KB3035131_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3035131_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
C:\Windows\servicing\Packages\Package_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.cat
C:\Windows\servicing\Packages\Package_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1.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,543
Done (22/06/2015 6:41:46 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Scanning Reparse Points.
Started at (22/06/2015 6:41:46 PM)
No problems were found with the Reparse Points.
Files & Folders Searched: 304,707
Reparse Points Found: 47
Done (22/06/2015 6:43:38 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Checking Environment Variables.
Started at (22/06/2015 6:43:38 PM)
No problems were found with the Environment Variables.
Done (22/06/2015 6:43:38 PM)
--------------------------------------------------------------------------------
Done (22/06/2015 6:43:38 PM)
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Done (22/06/2015 6:43:38 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.
-
anthonyjcan, please dont hijack another users thread, start a new thread for your self and I will help you there :-)
Shane
-
But Shane........most people are behind a router........my computer just aims at the router and the router does all the DNSing........so does this also change the routers DNS? I say this because I have Asus AC-RT68P and you can set your DNS all day long on my computer to whatever you want.........but my router will only let everyone on my home network the DNS I have applied to the Router. Regardless of what the computer has set as its DNS. OR am i missing something?
-
When you change the DNS servers in the computer, that overrides the default servers for just that machine - every other device gets the servers that are in the router.
To change to your preferred DNS, then you can set the router to those so that all machines will use that DNS.
-
This is common in Windows 10, 8.1, 7, Server 2012 and 2008
The following are some of the solutions for Windows Update Error Code 8024402c.
1. You need to have some Microsoft sites whitelisted or unblocked in your Windows Firewall.
2. One needs to make changes in the LAN Settings option of "Internet Options" (Win 10) > Connections in Internet Explorer.
3. Somtimes VPN (Virtual Private Network) can be the error.
4. Another cause is the ISA Server in the third-party Firewall settings.
5. Viruses, trojans, malware, adware can be another reason.
6. A simple solution in the form of "Update Troubleshooter" provided by Microsoft is available.
7. Proxy settings under "Internet Properties (Win 7)" > Connections can be another cause.
8. Windows Update components can be another cause.
9. UseWUServer option in the registry editor can be another cause.
10. Wrong update server can be another reason.
11. Windows update services accessing the internet can be another reason.
12. Settings of DNS errors under Network and Internet can be another reason.
13. SoftwareDistribution folder can be another reason.
As you can see above the number of reasons are many and the very common solution provided by many sites is only the registry check.
https://www.pallareviews.com/5203/fix-error-code-8024402c-windows-10-8-1-7-server-2012-2008/ (https://www.pallareviews.com/5203/fix-error-code-8024402c-windows-10-8-1-7-server-2012-2008/)
-
Hi Shane, all good to know. Have you seen or heard of Quad 9?? they offer fee dns but on a more secure footing ..
been using it for about 2 weeks and it seems ok ..
https://www.quad9.net/
not sure if the info will interest or help anyone ..
glenn