- Mar 25, 2001
- 5,287
- 6
- 81
Vista's program manager should be fired...
Trying to fix the winsock corruption in Vista Home Premium and nothing works...
netsh winsock reset returns an error, and the system restore does not work...
With XP there was at least a manual way of resetting the winsock by removing the winsock and winsock2 registry entries from HKLM hive and reinstalling the TCP/IP from the windows/inf catalog...
That is NOT the case in Vista....
Pondering my next step. I do not want to just reinstall because that is an easy way out...
Then, there is this Vista VPN support gem too:
MS KB Article
Translation: If you use VPN dialer on your Vista based PC and you are behind a router, most likely you will have a lot of problems with the connection so prepare for a lot of computer troubleshooting - even though your XP based PC is working fine wit a VPN dialer...
I am loosing money on clients that are using Vista based PC all the time...
Grrrr
Edit: Solution:
In case anyone whats to know, here is what I did to fix the problem:
I have determined that the winsock and winsock2 registry keys that are located in the HKLM/System/CurrentControlSet/Services are corrupted.
The system restore service also got corrupted (the system restore service was not even listed in the list of Windows Services (?)).
The command that is listed in MS KB that "should" reinstall the corrupted winsock keys
netsh winsock reset
would return an error
Initialization Function InitHelperDll in NSHHTTP.DLL failed to start with error code 11003
Of course, the netsh winsock reset command was run from a command prompt with an elevation (run as administrator).
What to do?
In Windows XP there is an option of removing the corrupted winsock and winsock2 registry keys from the HKLM registry hive and reinstalling the TCP/IP protocol from the Windows/inf folder. That is not the case in Windows Vista, because some Microsoft jenious decided to mess with this function.
But, what worked for me is this:
I have logged on to other, healthier PC that runs the same version of Windows Vista Home Premium.
I have exported the winsock and winsock2 registry keys only from HKLM/System/CurrentControlSet/Services to a flash drive.
I have connected the flash drive to the corrupted Windows Vista and merged the exported winsock and winsock2 registry keys with the original and broken versions.
Finally I have rebooted the computer.
Upon reboot the corruption was gone.
Finally the missing system restore service was fixed as well by running the sfc /scannow command (elevation required).
Cliffs:
Winsock keys and TCP/IP stack in general seem to be an integral part of many critical system services in Windows Vista. When these will go corrupted, Vista will have problems functioning properly.
When everything fails, export the winsock and winsock2 registry keys from other computer that runs the same version of Windows Vista and merge them into the corrupted keys on the broken Windows Vista OS...
Trying to fix the winsock corruption in Vista Home Premium and nothing works...
netsh winsock reset returns an error, and the system restore does not work...
With XP there was at least a manual way of resetting the winsock by removing the winsock and winsock2 registry entries from HKLM hive and reinstalling the TCP/IP from the windows/inf catalog...
That is NOT the case in Vista....
Pondering my next step. I do not want to just reinstall because that is an easy way out...
Then, there is this Vista VPN support gem too:
MS KB Article
Translation: If you use VPN dialer on your Vista based PC and you are behind a router, most likely you will have a lot of problems with the connection so prepare for a lot of computer troubleshooting - even though your XP based PC is working fine wit a VPN dialer...
I am loosing money on clients that are using Vista based PC all the time...
Grrrr
Edit: Solution:
In case anyone whats to know, here is what I did to fix the problem:
I have determined that the winsock and winsock2 registry keys that are located in the HKLM/System/CurrentControlSet/Services are corrupted.
The system restore service also got corrupted (the system restore service was not even listed in the list of Windows Services (?)).
The command that is listed in MS KB that "should" reinstall the corrupted winsock keys
netsh winsock reset
would return an error
Initialization Function InitHelperDll in NSHHTTP.DLL failed to start with error code 11003
Of course, the netsh winsock reset command was run from a command prompt with an elevation (run as administrator).
What to do?
In Windows XP there is an option of removing the corrupted winsock and winsock2 registry keys from the HKLM registry hive and reinstalling the TCP/IP protocol from the Windows/inf folder. That is not the case in Windows Vista, because some Microsoft jenious decided to mess with this function.
But, what worked for me is this:
I have logged on to other, healthier PC that runs the same version of Windows Vista Home Premium.
I have exported the winsock and winsock2 registry keys only from HKLM/System/CurrentControlSet/Services to a flash drive.
I have connected the flash drive to the corrupted Windows Vista and merged the exported winsock and winsock2 registry keys with the original and broken versions.
Finally I have rebooted the computer.
Upon reboot the corruption was gone.
Finally the missing system restore service was fixed as well by running the sfc /scannow command (elevation required).
Cliffs:
Winsock keys and TCP/IP stack in general seem to be an integral part of many critical system services in Windows Vista. When these will go corrupted, Vista will have problems functioning properly.
When everything fails, export the winsock and winsock2 registry keys from other computer that runs the same version of Windows Vista and merge them into the corrupted keys on the broken Windows Vista OS...