Error 10093 windows vista

Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system that is, the protocol stack that the Windows Sockets DLL runs over , the network interface, or the local network itself. Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.

Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. Software caused connection abort. An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error. Connection reset by peer. An existing connection was forcibly closed by the remote host.

This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. No buffer space available.

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Socket is already connected. A connect request was made on an already-connected socket. Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and when sending on a datagram socket using sendto no address was supplied.

Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued. Too many references. Too many references to some kernel object.

Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond. Connection refused.

No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.

Cannot translate name. Cannot translate a name. Name too long. A name component or a name was too long. Host is down.

A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. No route to host. A socket operation was attempted to an unreachable host.

Directory not empty. Cannot remove a directory that is not empty. Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached. User quota exceeded.

Ran out of user quota. Disk quota exceeded. Ran out of disk quota. Stale file handle reference. The file handle reference is no longer available.

Item is remote. The item is not available locally. Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded.

The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Successful WSAStartup not yet performed. The application may be accessing a socket that the current active task does not own that is, trying to share a socket between tasks , or WSACleanup has been called too many times.

Graceful shutdown in progress. No more results. Call has been canceled. The call has been canceled. Procedure call table is invalid. 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 someone else help me spread the word? I'll try to comment in a few "efe" threads a night, time permitting.

That will leave the other error threads without any help though - unless the experts could recognize this as fixing more symptoms than just efe. Thanks in advance. Thanks a lot, the kasperski solution for the error efe works very well. It removed the trojan and the system is updating as normally as ever. Brilliant charlie, ive spent a whole week tryin to sort efe problem, explorer.

After reading your post and following instructions my laptop seems perfect and it only took 10 mins and 4 clicks!!!!!! Office Office Exchange Server.

Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows Vista Setup. For deployment issues, please use the Windows Vista Deployment and Imaging forum.

Sign in to vote. Recently I had a problem with Vista where I could not connect to any Microsoft website, including hotmail, msn messenger and live update. In order to fix the problem I finally decided to do a fresh install which I have done, however I still get the same problems, unable to connect to any microsoft website, messenger, hotmail. Windows update gives me the error EFE.

I did not install any programs after the fresh install, I tried to update windows right away. Please help I've scoured the net for any help regarding this and everything I turned up hasn't helped. Thursday, January 24, PM. Spread the word if it worked for you too. This is not getting the credit it deserves, and the result of that is alot of wasted time going around the problem through complex windows settings that dont remedy the trojan.

The following list describes system error codes errors to They are returned by the GetLastError function when many functions fail. The zone does not have enough signing keys. One or more of the signing keys for a zone are not accessible to the DNS server. Zone signing will not be operational until this error is resolved. An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved. The DNS server encountered a signing key with an unknown version.

This operation could not be completed because the DNS server listed as the current key master for this zone is down or misconfigured. Resolve the problem on the current key master for this zone or use another DNS server to seize the key master role. The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone.

This operation could not be completed because the XML stream received is empty or syntactically invalid. This operation completed, but no trust anchors were added because all of the trust anchors received were either invalid, unsupported, expired, or would not become valid in less than 30 days. Hash collision detected during NSEC3 signing. Specify a different user-provided salt, or use a randomly generated salt, and attempt to sign the zone again. Choose a different algorithm or use NSEC3.

The record could not be created because this part of the DNS namespace has been delegated to another server.