Edge: "Unable to connect to the Internet" error

Si Microsoft Edge It shows you the message "cannot connect to the Internet", You are facing a symptom that may be due to your network adapter or Windows as to the Wi‑Fi settings, the router, firewall rules or, in professional environments, to parameters of virtualized networks such as Hyper‑V and Azure IoT Edge to Linux on Windows (EFLOW). In this practical guide, we've compiled all the proven and documented approaches from vendors and Microsoft itself so you have a single, comprehensive, and actionable resource.

The goal is to identify the most likely cause and take the appropriate steps: from reconnecting to a Wi-Fi network with a good signal, updating drivers and firmware, running Windows and Dell diagnostics, to checking DNS, opening necessary ports, or reconfiguring your EFLOW virtual network if you're working with IoT Edge. We also include community notes about real-life situations in Windows 7 and certificates, and how to proceed when Edge or .NET won't install due to signing or support issues.

Common causes and first quick check-up

Before you touch anything complex, confirm that the network you're connecting to is working and that you're not in Airplane Mode or with Wi-Fi turned off. Aside from Edge, check if other apps access the Internet; if they don't, the problem is a general connectivity issue, not a browser issue.

If you're using an Ethernet cable, check that the network icon isn't displaying any warnings, that the cable is firmly in the port, and that your router has an internet connection. If you're using Wi-Fi, make sure you're connecting to the network with the best signal and the correct password. A simple password failure or low coverage are very common causes of the Edge message.

Wi-Fi connection in Windows: securing signal, password, and basic settings

• Check and connect to the network with the best coverage from the network icon in the taskbar or hidden icons area. Find the list with the most white bars, select it, and tap Connect. If prompted, enter the network security key and continue.
• If the Wi-Fi switch remains gray, toggle it to blue; if it doesn't, check your wireless network options and make sure Airplane Mode isn't active. On some devices, the interface displays a panel with icons; switch to the tab that matches your device's icon to see the correct switch.
• On Dell computers, you can use the Optimize Network option (in SupportAssist) to have the system attempt to automatically repair common settings; once it's 100% complete, check the History tab to see what's been fixed. If you don't have this app, you have alternatives below with Windows tools.
• Keep drivers, BIOS Up-to-date router hardware and firmware: Network drivers are usually found in the Network section of the PC manufacturer's support, and router firmware is found on the router manufacturer's website. To update your router, you'll need a device connected to it (wired or Wi-Fi); consult your provider's instructions.
• Log in to your router to check the SSID and security if you have any concerns about your settings: In Windows, open Details for your Ethernet or Wi-Fi connection, locate the IPv4 Default Gateway, and open the browser with the address https://[GATEWAY]. Use the manufacturer's credentials; if you don't know them, check the manufacturer's documentation or device labels.
• Avoid outdated encryption like WEP: Although WEP key generators exist, they are currently discouraged for security reasons; opt for WPA2 or WPA3 for stability and compatibility. If you change the network name (SSID) or password, make a note of them and reconnect from Windows.

Windows Troubleshooter and Dell Diagnostics

Windows includes a Network Troubleshooter that can automatically detect and fix common problems. In the search box, type troubleshoot, open Troubleshoot (Control Panel) > Network and Internet > Network Adapter, and click Next to follow the prompts.

On Dell computers, you have two additional options: SupportAssist (Troubleshooting tab, I'm having Internet problems, Run now) and the network adapter diagnostics on the Dell support site. These utilities check settings, drivers, and even tune the adapter's performance.

If Airplane Mode is stubborn, try this setting on the Device administrator: Run devmgmt.msc (Windows+R) and under User Interface Devices disable and re-enable Airplane Mode Switch Collection. Reboot and check if you can now turn Airplane Mode on/off successfully.

To avoid power outages, in Device Manager open the Wi‑Fi adapter Properties (Power Management tab) and uncheck Allow the computer to turn off this device to save power. Apply, Accept and restart the PC.

Network Adapter Drivers: Clean Reinstall When All Else Fails

If your connection is broken after recent changes to Windows or the manufacturer and Edge won't browse, a clean reinstall of the network driver usually fixes the conflicts. First of all, download the latest driver from the PC manufacturer's website on another computer and save it to a memory stick. USB.

Back up your drivers if you consider it necessary, note the manufacturer and exact model of your device, and only then proceed to uninstall the current driver. This minimizes risks if Windows does not automatically find the correct driver upon restart.

1. Open Device Manager from the taskbar search and go to the Network Adapters section.
2. Locate your adapter (Wi‑Fi or Ethernet), right-click and choose Uninstall device; select Try to remove the driver for this device and confirm with Uninstall.
3. Restart the computer from Start > Power > Restart; upon startup, Windows will automatically attempt to install the appropriate driver.

If Windows doesn't install anything or the adapter doesn't work properly, manually install the driver downloaded from USB. Then check if Edge is already accessing the Internet.

DNS, ports, and firewall: Critical settings that block Edge without seeming to

An inaccessible or misconfigured DNS can leave Edge without browsing even when you're connected; check your configured DNS servers and test connectivity with ping if your environment allows it. If your network blocks public DNS like 8.8.8.8 and 8.8.4.4, use your organization's or carrier's DNS.

In environments with strict policies, the firewall can prevent outgoing traffic from Edge or auxiliary services; as a general rule, outgoing HTTPS (443) should be open, and incoming connections to your computer should be blocked except in very specific cases. If you can't open protocols other than HTTPS, Edge and many services work over WebSockets over 443 without issue.

Azure IoT Edge for Linux on Windows (EFLOW): When the virtual network is the problem

If you are using IoT Edge on EFLOW (applies to IoT Edge 1.5) and notice no traffic to the Internet or Azure services, the cause could be four things: IP addressing, DNS, firewall/ports, or other components. EFLOW depends on the Windows host network and Hyper‑V configuration, so any mismatch results in disconnections.

Checking IP addresses in EFLOW

Open a session of PowerShell as administrator and get the IP that EFLOW has registered for your VM. Use the cmdlet Get-EflowVmAddr and write down the IP.

Connect to the EFLOW VM Connect-EflowVm and check the interface eth0 ifconfig eth0; check that the inet address is not blank and matches the expected one.

If the IP is invalid or null, check the virtual switch type (external, default, or internal) and the allocation method (static or DHCP) to apply the appropriate correction. In statics, define correctly ip4Address, ip4GateWayAddress e ip4PrefixLength; in DHCP, verify that a DHCP server exists and that there are no policies MAC that block the VM.

Switch	Assignment	What to check
External	Static	Configure the IP, gateway, and prefix correctly; make sure the IP address is not duplicated on the network. You can check the configuration in the files. /etc/systemd/network/.
External	DHCP	There must be a DHCP server on the network; if there are lists by MAC, get the MAC from EFLOW with Get-EflowVmAddr.
Predetermined	DHCP	When it fails, it's usually the default switch; restart the host Windows. If it persists, disable and enable Hyper‑V.
Internal	Static	Configure the IP address, gateway, and prefix correctly; to access the Internet, create a NAT table on the Windows host following the EFLOW virtual switch guide.
Internal	DHCP	A DHCP server must exist on the internal network; if not, use a static IP address and configure NAT on Windows Server according to the documentation.

If the problem persists, create another VM (Windows or Linux) using the same switch and configuration. If that also fails, the cause isn't EFLOW, but the virtual network or IP configuration itself. This isolates the cause at the Hyper‑V or host level.

DNS in EFLOW

EFLOW uses systemd-resolved for DNS resolution; you can set specific servers with the cmdlet Set-EflowVmDnsServers. Check out /etc/systemd/resolved.conf and the service with sudo systemctl status systemd-resolved.

If your organization limits DNS access to allowlists, first validate that the Windows host can reach DNS and, if applicable, ask your network team to add the EFLOW IP to the allowlist. On networks that block public DNS, configure corporate DNS and test it from the VM with ping if ICMP traffic is allowed.

Ports and firewall in EFLOW

IoT Edge communicates with Azure IoT Hub using MQTT, AMQP, and HTTPS, ensuring that the firewall respects outbound requirements and keeps inbound access blocked, except in justified cases. Practical detail by protocol:

Dance	Port	Tickets	Departure from	Notes
MQTT	8883	Blocked (pred)	Blocked (pred)	Open it outbound if MQTT is your protocol. 1883 is not supported on IoT Edge. Keep inbound blocked.
AMQP	5671	Blocked (pred)	Open (pred)	This is the default protocol. 5672 is not supported. Block it if you're using another IoT Hub protocol.
HTTPs	443	Blocked (pred)	Open (pred)	Required for outbound provisioning or with DPS. Inbound only in two cases: transparent gateway (limited to the internal network) and C2D scenarios. WebSockets also use 443 when other protocols are not allowed.

To view current rules within the EFLOW VM, connect with Connect-EflowVm and run sudo iptables -L; to accept incoming traffic on a specific port, add the rule with sudo iptables -A INPUT -p <tcp|udp> --dport <puerto> -j ACCEPT and save with sudo iptables-save | sudo tee /etc/systemd/scripts/ip4save. Ensures consistency between host and VM.

Other network settings in EFLOW

The VM doesn't respond to ping by default because the firewall blocks ICMP; if you need to enable it, run the following command in EFLOW via the host's PowerShell: Invoke-EflowVmCommand "sudo iptables -A INPUT -p icmp --icmp-type 8 -s 0/0 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT".

For multicast detection, use an external switch in Hyper‑V and configure the IoT Edge module with NetworkMode host in the container creation options to use the host network. Example: { "HostConfig": { "NetworkMode": "host" }, "NetworkingConfig": { "EndpointsConfig": { "host": {} } } }.

If traffic is not arriving after adding rules, temporarily disable the VM firewall to avoid blockages: sudo iptables -F, sudo iptables -X, sudo iptables -P INPUT ACCEPT, sudo iptables -P OUTPUT ACCEPT, sudo iptables -P FORWARD ACCEPT. Restart the VM (Stop-EflowVm / Start-EflowVm) to restore the normal state.

In multi-NIC scenarios, a lack of internet access is often due to routing; configure static routes according to the Industrial IoT & DMZ guide for EFLOW. Also check NAT if you are using internal switches.

Router and gateway checks

From the Windows Network and Sharing Center, check your Connection Details to find the IPv4 Gateway and access its web interface. Verify that the router's WAN connection is active, the SSID is as expected, and the security setting is WPA2/WPA3. If you change parameters, apply and restart the router if indicated by the manufacturer.

If you don't remember your router's username/password, check the manufacturer's default credentials or the device's label; if they don't work, they may have been changed during installation. In that case, contact the person who set it up or make a reset with full knowledge of the consequences.