- Category: Wi-Fi and Bluetooth Troubleshooting
- Last Updated: 17 January 2019
- Hits: 737
No Internet Access When Connected
Some users may encounter an issue where they are unable to use the Internet even though they appear to be connected through either Wi-Fi or Ethernet. Restarting the computer will, in some cases, fix the problem temporarily.
Update January 11, 2019 - With machines running Windows 10 1809, the fix detailed below may or may not resolve the issue. There seems to be a completely different issue with 1809, which is a bug that Microsoft has yet to address. You can find out which version of Windows 10 that you are running by clicking Start, then type winver and press Enter. You will see "Version" followed by your Windows 10 version number. If you are using Windows 10 1809, the only potential fixes, at this time, seem to be enabling IPV6, and setting your network connection to "Public" instead of "Private." This a Windows 10 issue and not an issue with any specific network adapter or brand. You can find information about the issue, as well as Microsoft's suggested fixes, by clicking here. Although Microsoft Store applications are specifically mentioned, most users that experience this problem are experiencing it with multiple applications from multiple sources.
If your Windows version is 1803 or earlier, the below fix will often resolve it for you. It may also resolve the issue on some Windows 10 1809 machines, but that seems to be more hit-or-miss.
This has been confirmed to be an issue with Windows 10 which has surfaced with recent updates. These recent updates have removed entries from the Windows 10 registry which instructed the operating system to release used ports when all ports are exhausted. This has the effect of being connected to an Internet connection without the operating system having the ability to open new ports. Applications and services which were already connected may still continue to function, while the user will be unable to browse the Internet, or connect to anything else.
We have confirmed that this can be resolved by replacing these registry entries. Here is a step-by-step guide:
- Click Start
- Type regedit and press Enter
- Click File > Export... and then save the file to a place you will remember. This is your backup. If anything goes wrong, you can double-click this file from your machine and it will restore your current registry settings. The export may take a moment.
- Once the export is finished, copy this line - HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters - and paste it into the white space directly below File - Edit - etc, and press Enter. This should navigate you to the correct location in the registry, as seen below (right-click on the image and open image in new tab to expand):
- With Parameters remaining highlighted on the left side, right-click the empty white space on the right and click New > DWORD
- Name it TcpTimedWaitDelay and press Enter.
- Double-click TcpTimedWaitDelay and change the Value to 0000001e. Leave the Base setting as Hex. It should look like the below screenshot.
- Click OK.
- Repeat steps 5-8, creating the following keys -
REG_DWORD: 0000fffe (hex)
REG_DWORD: 00fffffe (hex)
REG_DWORD: 00000005 (hex)
- Click File > Exit
- Restart by clicking Start > Power > Restart and test.