Windows socket initilization failed

OK so I pushed ok and most everything seems to work anyway, but cannot get onto internet. Get error message re: sockets, cannot exactly remember. Also, right after the Windows Sockets init fail msg, then a progrom called Webhancer comes up saying has performed an illegal error and will be shut down.

So I say fine, i don't even know what that program is anyway, so I deleted that program thinking maybe was cause of socket problems. Well it wasn't. So I tried reinstalling windows, and still sockets initialization failed.

Do you know why this may have happened and how can I fix it. Please let me know what to do, Thanks!!! Rollin' Rog. Joined Dec 9, Messages 45, Webhancer may have been the cause, it alters winsock entries in the registry, and I believe also replaces the wsock I would suggest you immediately try restoring a registry which predates the problem.

Hopefully one or two of those still predate the issue. Just found out what webhancer is from your link to winsock2 fix, and am infuriated at these spies!!! My question is, which order should I do all this in? Should I try to fix the winsock, then remove Webhancer, or remove Webhancer first then fix the winsock. I am afraid to do it wrong and then I will not be able to use my computer at all. I am not sure what or where this is, and the action recommended in your link is to remove and reinstall it Then it says if does not work to contact vendor of 3rd party protocol stack's interface and verify stack is compatible Who is the vendor of 3rd party protocol stack interface--is it my ISP?

Am a little confused. Thanks for your help!!! Remove Webhancer first using Ad-aware; then if you are still having problems, follow the instructions provided by Del. Test afterwards. Thank you so much! Thanks for the nice blog. It was very useful for me. Keep sharing such ideas in the future as well. This was actually what I was looking for, and I am glad to came here!

Thanks for sharing the such information with us. Been scratching my head over this problem for a client's laptop for a week. Service were stuck in "starting Thanks much. Gave a Merry Christmas to someone when I fixed her computer just now! DLL failed to start with error code I think in my case it had something to do with disabling the Cisco VPN Client - re-enabling it still didn't fix things, until I happened across this easy answer.

Good work! Thanks, Blaine. Spent many hours trying to get the wireless to work. Was ready to give up and then I found your fix. Had leftover NLF sockets from bad norman security suite removal, removed registry winsock entries, your command finished the job.

Many thanks, was a vista pc. Worked for me Windows DLL failed to start with error issue. This helped me now greatly. Using Windows 8. Many thanks. Post a Comment. Popular Posts Unable to initialize windows sockets interface, error code Release and renew an IP address in Ubuntu WSUS doesn't report client status.

Intelide failes to start. Windows firewall is missing in Services. You have new unopened items missing in the taskbar.

Total Pageviews. Search This Blog. Run an application from a VB. About Me chaosMachine View my complete profile. Thursday, July 10, Unable to initialize windows sockets interface, error code On Vista?

So I go there. I have a look. User log on was taking minutes, welcome screen more. No IP address. No DNS server. What the hell? I had never seen something like this.

We have the greatest conversations this way. The service provider procedure call table is invalid. This is usually caused by one or more of the function pointers being NULL.

Service provider is invalid. The requested service provider is invalid. This error is also returned if the service provider returned a version number other than 2. Service provider failed to initialize.

The requested service provider could not be loaded or initialized. System call failure. A system call that should never fail has failed. This is a generic error code, returned under various conditions. Returned when a system call that should never fail does fail. Can indicate a service provider implementation error. Service not found. No such service is known. The service cannot be found in the specified name space.

Class type not found. The specified class was not found. Call was canceled. Database query was refused. A database query failed because it was actively refused. Host not found. No such host is known. The name is not an official host name or alias, or it cannot be found in the database s being queried.

This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database. Nonauthoritative host not found. This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. This is a nonrecoverable error. This indicates that some sort of nonrecoverable error occurred during a database lookup.

Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. QoS receivers. At least one QoS reserve has arrived. QoS senders. At least one QoS send path has arrived. No QoS senders. There are no QoS senders. QoS no receivers. There are no QoS receivers. QoS request confirmed.

The QoS reserve request has been confirmed. QoS admission error. A QoS error occurred due to lack of resources. QoS policy failure. The QoS request was rejected because the policy system couldn't allocate the requested resource within the existing policy.

QoS bad style. An unknown or conflicting QoS style was encountered. QoS bad object. A problem was encountered with some part of the filterspec or the provider-specific buffer in general. QoS traffic control error. This could be due to an out of memory error or to an internal QoS provider error. QoS generic error. A general QoS error. QoS service type error. An invalid or unrecognized service type was found in the QoS flowspec.

QoS flowspec error. An invalid or inconsistent flowspec was found in the QOS structure. Invalid QoS provider buffer. An invalid QoS provider-specific buffer. Invalid QoS filter style. An invalid QoS filter style was used. Invalid QoS filter type. An invalid QoS filter type was used. Incorrect QoS filter count. Invalid QoS object length.

An object with an invalid ObjectLength field was specified in the QoS provider-specific buffer. Incorrect QoS flow count. An incorrect number of flow descriptors was specified in the QoS structure. Unrecognized QoS object.

An unrecognized object was found in the QoS provider-specific buffer. Invalid QoS policy object. An invalid policy object was found in the QoS provider-specific buffer.

Invalid QoS flow descriptor. An invalid QoS flow descriptor was found in the flow descriptor list. Invalid QoS provider-specific flowspec.