Suddenly your Vista computer decides to go on strike. Network connections don’t work, wierd failure messages pop up, and you can’t even open up event viewer to see what the problem is! You try to start Event logging or other services that should be started but aren’t and you get a “Error 1747: The authentication service is unknown” mesage. You try other things and your get the fabulous “Error 10107: A system call that should never fail has failed” mesage. (go figure - Microsoft can take the time to create an error mesage the shouldn’t ever happen, but can’t take the time to actually fix the problem!) Anyway the problem, believe it or not, is likely to be a messed up Winsock stack. TCP/IP stack Winsock settings in Windows Vista may get corrupted, causing errors and problems with Internet connectivity. Corrupt Winsock or Windows sockets configuration can be due to a lot of reasons such as installation of a networking software, or due to virus, trojan or malware infection, or sometime even due to disinfection of spyware by security software.
When Winsock corrupts, the networking errors that you may face include unable to surf the Internet with “Page cannot be displayed” error message in Internet Explorer or AOL even though the DSL/ADSL/cable Internet connection is connected. Sometimes, Windows Firewall/Internet Connection Sharing (ICS) service is terminated as well.
To repair and reset the Windows Vista Winsock Stack:
- Click on Start button.
- Type Cmd in the Start Search text box.
- Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as Administrator. Allow elevation request.
- Type netsh winsock reset in the Command Prompt shell, and then press the Enter key.
- Restart the computer.
What netsh winsock reset command does is it resets Winsock Catalog to a clean state or default configuration. It removes all Winsock LSP (Layered Service Providers) previously installed, including the potential malfunctioned LSP that causes loss of network packets transmission failure. So all previously-installed LSPs must be reinstalled. This command does not affect Winsock Name Space Provider entries.
Note: To check which LSPs installed on your Vista system, use netsh winsock show catalog command.
ds
#1 by bashu on April 24th, 2011 - 1:14 pm
Thank you very much. You manage to solve my problem error 10107 and1747……..im so kind of u..dear…..
#2 by Daniel on March 14th, 2011 - 6:22 pm
MUCHAS GRACIAS !!!!
#3 by kukucka on July 11th, 2010 - 3:38 am
I made backup and I was ready to reinstall windows. Thank you.
#4 by sss on June 19th, 2010 - 10:58 am
thanks a lot it’s really helpful
#5 by John on March 15th, 2010 - 6:25 pm
Thank you very much!!
#6 by Daniele Italy on February 13th, 2010 - 7:55 am
@Daniele Italy
Thanks also to Google that have found this page!
#7 by Daniele Italy on February 13th, 2010 - 7:50 am
Thank you very much. You manage to solve my problem error 10107
Wowwwwwwwwww………….
#8 by Yeyo on December 3rd, 2009 - 9:42 pm
I´m agree with Mark, MUCHAS GRACIAS AMIGO
#9 by fred on October 29th, 2009 - 6:15 am
Thank you very much. You manage to solve my problem error 10107 and1747
#10 by Stefan on October 16th, 2009 - 10:15 am
Thanks, you are my hero!
Worked perfectly, Vista german Home Premium with network problems and long startup.
bR, Stefan
#11 by AL on September 21st, 2009 - 10:52 am
Am receiving 10107 error when performing step 4 above (admin cmd prompt & trying to execute “netsh winsock reset”). No error message when performing “netsh int ip reset”.
#12 by Paul Cartlidge on March 7th, 2009 - 10:12 am
Dear Ds,
I have just read your article on minsock for vista. I am not getting a 10107 error BUT i can’t connect to the intrnet because a “winsock catalogue error” is causing a problem. Will the fix you describe work for xp? I don’t mind having a go but when I read check your LSP’s ? I stopped because I am not sure what this means, Sorry to appear a bit stupid but any help would be appreciated as it’s noe doing my head in! Paul
#13 by Abdul Khaliq on January 4th, 2009 - 7:57 am
I second Mark’s remarks. I found solution to errors 10107 and 1747 at a time when I was struggling with installation CD that was giving error message too. Your suggested solution rid all these errors in one click. Thanks for your valuable help. AK
#14 by Mark on September 4th, 2008 - 9:02 pm
ds, you are an amazing human being! I’m surprise that I’m the first to write that you are the only one I’ve found that can fix this 10107 error. Thank you very much. Keep up the good work. -mark