New
#31
this should give us clues... i was able to update security essentials today, after running the dotntfix but now i get this...
this should give us clues... i was able to update security essentials today, after running the dotntfix but now i get this...
im really suprised someone doesnt know something about this.. isnt that the point of the unique error codes?? doesnt this help?
0x80244004 WU_E_PT_SOAPCLIENT_CONNECT Same as SOAPCLIENT_CONNECT_ERROR - SOAP client failed
i have no idea what a SOAP client is, does what is for..
i am clueless with all of this really...
im just suprised someone doesnt see that error code, see it is a soapclicent connect error.. and poof, say here is what is wrong. do this and this
instead, i have been going round and round and round, for 6 days straight!!
i appreciate your help! i really do.
im just confused, what is the point of the unique errors. what doesn't it just windows update error. why give us that code?
someone has got to know what this is. what a soap connect error is. is it bad credentials/certificates that cause this?
dns issues, network issues, UAC, admin/standard user, what?
im so tired of this damn error code!
Unfortunately, there is almost no such thing as a 'unique' error in any OS - the inter-relationships of various systems are such that diving straight at an error can lead you totally in the wrong direction.
SOAP is effectively the Windows interface to Web services, if I understand it right. SOAP - Wikipedia, the free encyclopedia
Interesting that you've reset the WINSOCK Catalog without resetting the HTTP as well....
Please run the following commands in an Elevated Command prompt
NETSH WINSOCK RESET
NETSH WINHTTP RESET PROXY
NETSH WINHTTP RESET TRACING
You'll be advised that you need to reboot - do so, and then test WU again
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>NETSH WINSOCK RESET
Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.
C:\Windows\system32>NETSH WINHTTP RESET PROXY
Current WinHTTP proxy settings:
Direct access (no proxy server).
C:\Windows\system32>NETSH WINHTTP RESET TRACING
Current WinHTTP Tracing settings:
Tracing is not enabled.
Trace File Prefix: (none)
Trace Output: file
Trace Level: default (headers and top-level APIs only)
Network Traffic Format: ansi
Maximum size of trace file (in bytes): 65535
C:\Windows\system32>
ok
ok, one minute, on the phone with a microsoft tech support assistant
restarted. same error. advanced tech support are calling me back tomorrow, tier one was unable to help (pretty much offered everything that i have done myself)
so.. we will see... fingers crossed
p
I'll leave you to their tender mercies then :)
Please let us know if and how they manage to fix it (on past experience, they will end up recommending at least a repair install)