When you've changed broadband WiFi still works on all your devices, and that's actually the problem. The WiFi connection is fine. The internet behind it isn't. These are two completely separate things, and Windows doesn't always make that obvious. What you're seeing isn't a glitch or a sign that something is seriously broken. It's a predictable result of how routers, Windows network profiles, and ISP provisioning interact. Understanding that is half the battle.
TL;DR
When you've changed broadband WiFi still works because your router keeps broadcasting the same network name and password regardless of what's happening on the internet side. The fix depends on where the fault actually sits: a stale Windows profile, wrong router WAN settings, a dodgy DNS cache, or an ISP line that isn't fully active yet. Work through the solutions below in order and you'll find it.
Key Takeaways
- Changed broadband WiFi still works because the router's local network is independent of the internet connection behind it.
- The most common fix is forgetting the WiFi network on Windows and reconnecting fresh.
- If every device has no internet, the fault is in the router WAN settings or the ISP line, not your PC.
- Running netsh winsock reset and flushing DNS clears stubborn Windows-side issues.
- Always test a wired connection directly on the modem before calling your provider.
At a Glance
- Difficulty: Intermediate
- Time Required: 15 to 30 mins
- Success Rate: 85% of users
What Actually Causes Changed Broadband WiFi Still Works?
Here's the thing: your router does two completely separate jobs. First, it creates a local wireless network in your home. Second, it connects that local network to the internet via your ISP's line. When you change broadband provider, job one carries on without any interruption. The router keeps broadcasting the same SSID and accepting the same password. Every device in the house reconnects automatically. Windows sees a familiar network and reports it as connected. But job two, the actual internet path, might be broken, misconfigured, or not yet active at all.
So when people say changed broadband WiFi still works but there's no internet, what they're really describing is a disconnect between those two layers. The local network is fine. The WAN side is not. The reasons vary, and they stack up in different combinations depending on your setup.
The most common culprit is a stale Windows WiFi profile. Windows caches network profiles including credentials, DNS settings, and connection behaviour. If the new router uses a different password, a different IP range, or different DNS servers, Windows might be trying to connect using old data. It joins the network but can't get a proper IP lease or resolve any addresses.
Second most common: the router itself is still configured for the old ISP. If you've kept your old router and plugged it into the new provider's line, the WAN settings almost certainly need updating. Different ISPs use different connection types. FTTP connections often use PPPoE with ISP-supplied credentials. Some use DHCP. If the router is still trying to authenticate with the old provider's settings, it simply won't get a working WAN connection, and no device in the house will have internet regardless of how good the WiFi signal is.
There's also the DNS and TCP/IP stack angle. Windows maintains a DNS resolver cache and a Winsock catalogue. After an ISP change, these can hold stale entries that point at the old provider's infrastructure. The result is that pages fail to load even when the connection itself is technically working. And then there's the possibility that the new line simply isn't active yet, or has been misprovisioned on the ISP's side. That one's out of your hands, but it's easy to rule out.
Finally, some users have static IP addresses or manual DNS entries set on their adapter, left over from a business setup or a previous fix. Those won't update automatically when you change provider and will cause connection failures that look identical to everything else on this list. For more on how Windows handles network adapter settings, our guide on WiFi connected but no internet on Windows covers the adapter properties side in detail.
Changed Broadband WiFi Still Works: Quick Fix
Start here. This covers the majority of cases and takes under ten minutes. The logic is simple: force Windows to forget everything it thinks it knows about the network and start from scratch.
Forget the Network and Reconnect Easy
- Open WiFi settings
Go toSettings > Network and internet > WiFi > Manage known networks. You'll see a list of every network Windows has ever connected to. - Forget the affected network
Find your home network name in the list and clickForget. Windows deletes the saved profile including any cached credentials, IP settings, and DNS configuration. - Power-cycle the router
Turn the router off at the wall. Wait a full 30 seconds. Turn it back on and give it two minutes to fully boot before you try to reconnect. This is not optional. A quick off-on doesn't clear the DHCP lease table properly. - Reconnect and re-enter the password
Click the WiFi icon in the taskbar, select your network, and enter the new router's password. If you're not sure what it is, check the label on the back of the router. - Verify
Open a browser and try loading a page. If it works, you're done. If you get a connected but no internet warning, move to the next solution.
More Changed Broadband WiFi Still Works Solutions
If the quick fix didn't sort it, or if every device in the house has no internet, these intermediate steps cover the router side and the Windows settings that survive a simple network forget.
Check Router WAN Settings for the New Provider Intermediate
- Log into the router admin page
Open a browser and type192.168.1.1or192.168.0.1into the address bar. The correct address is usually printed on the router label. Log in with the admin credentials (also on the label if you haven't changed them). - Find the WAN or Internet section
This is labelled differently on every router. Look for WAN, Internet, Broadband, or Connection. You want the page that shows how the router connects to the outside world, not the local WiFi settings. - Check the connection type
FTTP (full fibre) connections typically use PPPoE and require a username and password supplied by the new ISP. FTTC (part fibre, part copper) may use PPPoE or DHCP depending on the provider. If the connection type or credentials still show the old ISP's details, update them now. Your new provider's welcome letter or app will have the correct values. - Save and reboot the router
Apply the changes and let the router reboot. Give it two minutes, then check the WAN status page again. It should show a connected status with a public IP address assigned. - Reuse or replace?
Some providers require their own gateway hardware and won't support third-party routers at all, or only support them in bridge mode. If your new ISP sent you a router, use it. If you want to keep your own router, check whether bridge mode is needed and whether your ISP supports it.
Check for Manual DNS or Static IP on the Windows Adapter Intermediate
- Open adapter properties
Go toSettings > Network and internet > Advanced network settings. Find your WiFi adapter and clickView additional properties, or right-click the adapter and choose Properties from the old Control Panel view. - Check IPv4 settings
SelectInternet Protocol Version 4 (TCP/IPv4)and click Properties. If the radio buttons are set to a specific IP address or specific DNS server addresses rather than Obtain automatically, that's your problem. Old manual entries from a previous setup won't update when you change ISP. - Switch to automatic
Set both options toObtain an IP address automaticallyandObtain DNS server address automatically. Click OK, then close the adapter properties. Disconnect and reconnect to WiFi.
Windows Network Reset Intermediate
- Open Network reset
Go toSettings > Network and internet > Advanced network settings > Network reset. This is near the bottom of the page. - Run the reset
ClickReset nowand confirm. Windows will remove all network adapters and reinstall them, clearing all saved profiles, VPN configurations, and adapter settings. The PC will restart automatically. - Reconnect after restart
After the reboot, reconnect to your WiFi network and re-enter the password. You'll also need to reinstall any VPN clients or custom network software you use, as those get wiped too.
For reference, our Windows network reset walkthrough covers what gets removed and what to reinstall afterwards, which is useful if you run any VPN software or have custom DNS configurations you want to restore correctly.
Advanced Changed Broadband WiFi Still Works Fixes
These are the fixes for when the above hasn't worked, or when you want to go straight to the nuclear option on the Windows TCP/IP stack. The command-line approach is what I reach for on remote support sessions when the GUI fixes haven't stuck. This one often needs a second reboot before it sticks, so don't skip that step.
Reset the TCP/IP Stack and Flush DNS Advanced
- Open Command Prompt as administrator
Press the Windows key, typecmd, right-clickCommand Promptin the results, and chooseRun as administrator. You need admin rights for these commands or they'll fail silently. - Run the reset commands in order
Type each of these and press Enter after each one. Wait for each to complete before running the next:netsh winsock resetnetsh int ip resetipconfig /releaseipconfig /renewipconfig /flushdns
The first two commands reset the Winsock catalogue and the TCP/IP stack respectively. These are the Microsoft-recommended commands for clearing corrupted network state on Windows. The ipconfig commands release your current IP lease, request a fresh one, and clear the DNS cache. - Restart the PC
Don't skip this. The Winsock reset in particular doesn't fully apply until after a reboot. Close everything and restart. - Test after restart
Reconnect to WiFi if it doesn't reconnect automatically and try loading a page. If it works, great. If not, continue below.
Delete the WiFi Profile from the Command Line Advanced
- List saved profiles
In an administrator Command Prompt, runnetsh wlan show profiles. This lists every WiFi network Windows has saved. Find your network name in the list. - Delete the specific profile
Runnetsh wlan delete profile name='YourNetworkName'replacing YourNetworkName with your actual SSID exactly as it appears in the list. This is more thorough than using the Settings GUI Forget option, as it removes the underlying XML profile file rather than just clearing the password. - Disable and re-enable the adapter
Open Device Manager (devmgmt.msc), expand Network adapters, right-click your WiFi adapter, choose Disable device, wait five seconds, then right-click again and choose Enable device. This forces a fresh initialisation of the adapter driver. - Reconnect from scratch
Click the WiFi icon in the taskbar, select your network, enter the password, and verify internet access.
Test Directly on the Modem or ONT Intermediate
- Connect via Ethernet cable
Plug a laptop directly into the modem or ONT (the box your ISP installed on the wall, not your router) using an Ethernet cable. Bypass the router entirely. - Check for internet access
Open a browser and try loading a page. If you get internet access this way, the problem is in your router configuration, not the ISP line. Go back to the router WAN settings fix above. If there's still no internet, the ISP line is the problem. - Contact your provider
If the direct connection has no internet, call your new provider and ask them to check line activation and provisioning status. Give them the MAC address of the device you tested with if they ask for it. This is a common issue in the first 24 to 48 hours after a provider switch.
Preventing Changed Broadband WiFi Still Works Problems Next Time
Most of this is avoidable with a bit of preparation before the switch happens. Here's what actually makes a difference, in order of importance.
Test a wired device first. Before you start troubleshooting WiFi or Windows, plug a laptop directly into the new router with an Ethernet cable. If that works, the ISP line is fine and you're dealing with a WiFi or Windows issue. If it doesn't work, you need to sort the router WAN settings or call the provider before anything else. Doing this first saves a lot of time going in circles.
Update the router WAN settings immediately. The moment the new provider's equipment or line is active, log into the router admin page and update the connection type and credentials to match the new ISP. Don't wait to see if it works on its own. It won't, if the settings are wrong.
Record the old SSID and password before switching. If you want to keep the same network name and password on the new router (which means your devices reconnect automatically without needing to be updated), write them down before you change anything. Match them exactly on the new router's WiFi settings. Case-sensitive. No trailing spaces.
Avoid manual DNS and static IP settings unless you have a specific reason for them. Automatic addressing (DHCP) handles ISP changes cleanly. Manual settings don't update themselves and will cause exactly the kind of fault described in this guide every time your network infrastructure changes. If you do use custom DNS servers like 1.1.1.1 or 8.8.8.8, those are fine to keep as they're not tied to any specific ISP. It's only ISP-specific manual settings that cause problems.
Restart the router after the provider change before you start troubleshooting any client devices. A router that's been reconfigured but not rebooted can behave oddly. Give it a full power cycle and two minutes to stabilise. Then test. For more on keeping your home network healthy after changes like this, our home network setup guide covers router placement, firmware updates, and DNS configuration in more detail.
Keep router firmware updated. Outdated firmware can cause compatibility issues with new ISP equipment, particularly on FTTP connections where the ONT firmware and router firmware need to work together. Check the manufacturer's admin page or app every few months. It takes five minutes and prevents a lot of problems. The HowToGeek guide on managing Windows WiFi profiles is also useful reading if you want to understand how Windows handles saved networks and why forgetting them properly matters.
Changed Broadband WiFi Still Works: Summary
When you've changed broadband WiFi still works because the router's local network is completely separate from the internet connection behind it. The fix depends on where the fault actually sits. For most people it's either a stale Windows profile (fix: forget the network and reconnect) or wrong router WAN settings (fix: update them in the admin page to match the new ISP). If every device has no internet, focus on the router and ISP line first before touching Windows. If only one device is affected, the Windows TCP/IP reset commands will usually clear it. Work through the solutions in order, test after each one, and you'll find it. And if you don't, remote support is there for exactly this kind of thing.