• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 967
  • Last Modified:

Netsh winsock reset is nowhere near as effective as winsockfix, what are my other options?

Hey folks, everytime I sweep a system for malware, it usually leaves me with a buggered up Internet connection. On XP systems, winsockfix fixes the problems abput 95% of the time. With Windows Vista and 7 though, that tool does not work, and the only alternative I am aware of is the "netsh winsock reset" command which only seems to fix the problem maybe 10% of the time. Is there a tool out there along the lines of winsockfix that will work for WIndows Vista and 7?
3 Solutions
Thats odd..... My experience has used the built in netsh to be the opposite......

I would use it with 2 other netsh commands though.....

netsh winsock reset
netsh firewall reset
netsh int ip reset reset.log

Might be why I have better luck with that......

As to your actual question about a util for Vista and 7, Sorry.... Just wanted to add the above....
Hi, here is a utility for Win 7


Or give this a try:

Please click on Start and All Programs and then Accessories.

1. From the list select "cmd". Right click on "cmd" and then choose Run as administrator.
2. At the command prompt window, type the following commands:
3. netsh winsock reset catalog and hit Enter that resets WINSOCK entries to installation defaults.
4. netsh int ipv4 reset reset.log and hit enter that resets IPv4 TCP/IP stack to installation defaults.
5. netsh int ipv6 reset reset.log and hit enter resets IPv6 TCP/IP stack to installation defaults.
6. Restart the computer.

Microsoft has a fixit for you>xp + vista

For 7 its builtin>don't know how good that works!

Running Internet Explorer Troubleshooters

   1. Exit all programs.
   2. Click Start, and then click Control Panel.
   3. Under System and Security, click Find and Fix Problems.
   4. In the Task pane, click View All.
   5. Click Internet Explorer Performance.
   6. In the new window, click Next.
      Note The troubleshooter runs and fixes all identified issues automatically.
   7. Click Close.

Taken from http://support.microsoft.com/kb/936211
jfahlmanyahoocomAuthor Commented:
Those were all three great answers. I used the first one on two machines already and it solved my problems! If I run into deeper problems though, I would expect the other two answers would prove very helpful as well.
You're welcome :)

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now