New
#21
its always tough to know what actually was the solution, since most of us try a few different things, and then focus on the last thing tried as "the solution"(the fallacy of the straw that breaks the camels back).
I'm reluctant to suggest registry fixes, since they are risky, but in my case I also deleted my winsock entries,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2
[FIX] Windows Sockets Registry Entries Required For Network Connectivity Are Missing
I then used a winsock reset utility on majorgeeks. The utility claims to apply
Works with XP, Vista, 7, and 8 – and is fully portable!
per the author(Winsock Reset 1.2)
WinsockReset Foolish IT
so its a risk for W10, but I did it, and survived to tell this story. The error no longer occurs on my machine.
I ran the sequence of commands suggested earlier, but after I did this winsock reset.
I'm an older guy and make no claims to understanding any of this. I bought my first PC around 1984(10mb HDD and the ubiquitous 640k DOS) and been hacking my way through MS voodoo ever since.