Computer Help forum


windows sockets initialization failed/winsock problem.

by moceanu / August 9, 2012 9:33 AM PDT

Hi, my problem is that when I turn on my computer and get to my login screen, everything is noticeablly oversized. When I log in, I initially get a blank silver screen and eventually a window pops up that says "Windows sockets initialization failed" After I click okay, my desktop shows up but again everything is larger than normal and I can't connect to the internet.

I've tried entering netsh winsock reset catalog/netsh int ip reset reset.log from the command prompt but when I do I get "Initialization function InithelperDll in NSHHTTP.DLL failed to start with error code 101007"

Any help would be appreciated!

Answer This Ask For Clarification
Discussion is locked
You are posting a reply to: windows sockets initialization failed/winsock problem.
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: windows sockets initialization failed/winsock problem.
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Clarification Request
Have you checked prior discussions? Example at link.
by R. Proffitt Forum moderator / August 9, 2012 10:05 AM PDT
Collapse -
by moceanu / August 9, 2012 10:19 AM PDT

I've checked countless forum posts and responses over the last two days to try and find a fix and nothing has worked. Also running scans isn't possible because I have no internet access on that computer.

Collapse -
How you run scans when there is no Internet.
by R. Proffitt Forum moderator / August 10, 2012 12:45 AM PDT
In reply to: Yes
Collapse -
Clarification Request
Can you tell us more ...
by Edward ODaniel / August 9, 2012 12:13 PM PDT

about WHEN the problem started (such as - I first noticed the problem just after removing some malware called ----------"

Have you tried a system restore to a time BEFORE the problem came up?

Did you install or uninstall any apps or drivers immediately before the problem started?

What all have you attempted to resolve your problem?

You have to help us help you by providing ALL the pertinent or possibly pertinent information regarding the problem.

The actual version of Windows would be nice too as I don't recall similar messages in Windows 1.6 or 3.0 or 3.1x or even in NT 3.1 or 3.5.

All Answers

Collapse -
windows sockets initialization failed/winsock problem.
by ceewizard / August 14, 2012 4:13 PM PDT

The Windows Sockets consists of these things called "LSP"'s (Layered Service Providers)., and they're linked together like a chain. If for any reason the chain is broken or can't be "reset", you won't be able to connect to the internet. Try WinXP Fix, it might resolve the issue. It has the option to backup your registry, I suggest you exercise that option.

Popular Forums
Computer Help 49,613 discussions
Computer Newbies 10,349 discussions
Laptops 19,436 discussions
Security 30,426 discussions
TVs & Home Theaters 20,308 discussions
Windows 10 360 discussions
Phones 15,802 discussions
Windows 7 7,351 discussions
Networking & Wireless 14,641 discussions


Big screens for the big game

Still looking for the best TV deals ahead of Sunday's game? Here are our top three big screen picks.