Are you frustrated by getting “no internet” or “limited access” messages on your Windows 10 machine, while you are actually connected to your home/work/public WiFi point? Are you getting ERR_NETWORK_CHANGED message in Chrome? Try the following steps to possibly fix your problem.
Anyone who knows me, knows that I barely touch Windows OS, unless I have to! So a while ago I had to do some .NET work for a customer in VisualStudio…So I grabbed Windows 10 Education using my university credentials (lucky me!) and Installed it on my old laptop. Everything was fine for about one or two hours after installation…but as soon as Windows updated itself to build version 1511…suddenly my WiFi connection was not working anymore… by not working I mean it was obviously connected to the WiFi point, but its icon had this weird warning icon and it popped up the message “Connected, No Internet”. And the Chrome browser also did not load any webpage, displaying ERR_NETWORK_CHANGED message. My laptop WiFi module is a relatively old one, Intel WiFi Link 5300, I am pretty sure before update to build 1511 it was working fine…
I traced down the problem to the file vwifibus.sys in the windows\system32\drivers folder. But anyways…enough with story time…lets get to the point.
FIX – Step 1
Open up your Device Manager. Then browse to the Network Adapters node and expand it:
Right click on the WiFi module (it will be likely a different brand/model in your case!) and select Properties. In the new popped up window, click on the Advanced tab:
Here we will do the work…we have to change some of the default options in this page. I configured my WiFi module with following options. You have to try the same:
- 802.11.n Channel Width for band 2.4
- 802.11.n Channel Width for band 5.2
- 802.11.n Mode
- Fat Channel Intolerant
- Preferred Band
- Set this to 2.4 GHz…unless you are sure that your WiFi us 5.2 GHz!
- Roaming Aggressiveness
- Transmit Power
- Wireless Mode
Hit OK and I am quite sure you will get access to internet right away! if not, restart your computer and see if it is working or not.
FIX – Step 2
If the step 1 did not fix your problem. It might be that your TCP/IP stack has got corrupted. To reset it, open a command prompt with administration access, and type the following commands
- Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
- Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset c:\reset-4.log
- Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset c:\reset-6.log
Restart your computer and hope for the best!
FIX – Step 3
If the step 2 did not help as well, then something is terribly wrong…open the command prompt with admin access again and type in this command: sfc /scannow
It will check for integrity of the Windows files and will fix the problems (hopefully).
FIX – Step 4
If even step 3 did not fix your problem, screw this, install a GNU/Linux operating system and enjoy!