Then in device manager I was poking around with the settings and found an option to unhide all. I went from 4 listed under network adapters, to 17. Which now makes sense why I had 17 folders in the registry. I viewed the properties on each of these 17 network adapter devices, 3 of them currently say in the device status box:
"Currently, this hardware device is not connected to the computer. (Code 45) To fix this problem, reconnect this hardware device to the computer."
My wifi is not working at this moment (typing from mobile). The 3 "network adapters" that are listed as not connected are:
-Microsoft ISATAP Adapter
-Microsoft WiFi Direct Virtual Adapter
-Teredo Tunneling Pseudo-Interface
The other 14 all SAY in the device status box that they are working. Unfortunately I don't have another PC at the moment to check this against, as all other pc's here are running the same version of Windows 10.
Unfortunately you lost me at the part about getting rid of old network files... as Im not sure if any of these 17 are considered old.
You sound like you know what you're talking about though, do you have any other ideas with the new info I just found?
The very first thing I tried was to swap ethernet cable between computer and switch. No change. And I had other computers on the same switch with the same cables that worked fine. And the cable/switch worked fine 20seconds earlier, before the reboot with updateds being installed.
Just to try something, I pulled out an old Netgear FS108 switch and connected everything with the same cables as before. AND NOW I HAVE NETWORK CONNECTIVITY AGAIN.
And I still have a file server connected to the faulty switch and its still online and working fine. And this problem DID materialize after a reboot. And I did scrap my installation for nothing, my bad.
So, my two cents - check and re-check your network hardware.
Last edited by MathiasS; 12 Jan 2016 at 17:32.
I had the same problem for two days. I suddenly couldnt connect to thw internet via wifi or ethernet after the recent Windows 10 upgrade.
I tried everything I found online to no avail.
1. Resetting winsock and ip through command prompt.
2. Uninstalling and installing the network adapter
3. Updating the driver software
4. Sytem restore
5. Restoring to previous build
The only thing that worked for me is reverting the OS back to Windows 8.1. My PC and laptop were affected. I reverted to 8.1 on my PC then copied the Winsock and Winsock2 registry to my Windows 10 laptop.
I restarted my router just to make sure and voila! Internet's back on both computers.
I am not updating my PC to Windows 10 just yet until this bug is addressed by Microsoft.
Hope this will help anyone still experiencing the problem.
What if you had re-booted the router earlier in the process....?
I did that too in combination with the solutions I found online with no luck. I did a lot of things on my computer so it's possible that any of those helped in one way or another.
But the internet only came back when I copied the Winsock and Winsock2 registry files from a non-Windows 10 PC. It's still definitely worth a try if the problem still persists.
wish i could do system restore QQ
I too had this problem happen all of a sudden this past Friday (01. 22. 2016) morning. I scoured the Internet using the hotspot on my smartphone and found a solution to this problem over at Kapril Arya. An individual named "Nate J" offered the following solution. I applied that solution and I have outlined the steps I took to get my machine back to full connectivity.
- Look for a Windows 7 or 8.1 OS machine and export the Winsock and Winsock 2 registry keys to a thumb drive or backup harddrive. Be sure to export a 32-bit registry key if you have a 32-bit system; export a 64-bit registry key to a 64-bit system. If you do not have access to either, here is at least a link to Winsock from a Windows 8.1 64-bit machine; here is also a link to Winsock 2 from the same machine. These files came from Mr. Arya's machine.
- First, you may want to set up a Restore Point on your machine before you start tinkering with the Registry just in case.
- Next, back up your registry by pressing the Windows and X keys together to bring up the Run command line item. Click on it and it will bring up the Run command line.
- Type in regedit. When the dialog box appears click OK. When the User Account Control box appears, click the Yes button.
- When the Registry Editor appears, look under the File menu for the Export menu item.
- When the Export Registry File box appears, look for a location to save the files in, create a folder named Win 10 Registry Back Up or something similar on either a thumb drive or a back up hard drive.
- Return to the Registry Editor and look for the Winsock folder under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
- When you are copying the Winsock and Winsock 2 folders from a Windows 7 or 8.1 machine if you decide not to use the links above, simply use the Export function described in bullet point 6 in order to save those two keys for later import into the Windows 10 registry.
- Return to the Windows 10 Registry Editor to the Winsock and Winsock 2 keys repectively and right-click on each Winsock Key Folder to select Delete. Answer Yes and close the Registry Editor.
- Reopen the Registry Editor, return to the File menu item and look for the Import function. Ensure that the hive is still open under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services.
- The Import Registry File box will open to the location where you saved the Winsock and Winsock 2 keys on your thumb drive or backup harddrive.
- Click on Winsock first. Winsock 2 may show up too after the import. If it does, right-click on it to delete it. Return to the Import Registry File box to import the Winsock 2 folder.
- Once both of the keys have been imported into their place in the registry, close the Registry Editor.
- Next, press the Windows and X keys to bring up the Command Prompt (Admin) menu item. Type in "Ping 192.168.1.1." - usually your router's IP Address. If it responds and returns with 0% packet loss then you have communications with your router. "Nate J" suggested that it may be necessary to type in the "netsh winsock reset" command and then reboot if the Windows version of your PC is an earlier version than the files you are replacing the Winsock files with.
- Next, type "Ping Google.com." If you also receive a response with 0% loss then you should be able to connect to the Internet without a reboot. To properly close the Command Prompt, type in exit, and it will close.
- Check through your router's login gateway to see if it will connect your machine to the Internet. Your router may change its IP address in order to avoid a conflict with your ISP's IP address. It should connect after that.
It worked for me. Hopefully it will help you too! My thanks goes to Mr. Kapril Arya on his blog and "Nate J" another commenter on his blog for publishing these insightful assists - which helped me and my business get back to work.