Network troubleshooting technician providing live chat help

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Home networking, Wi-Fi routers, channel width and interference, 2.4/5/6 GHz bands, Windows/macOS internet issues, DNS & IP configuration, ISP setup

Fix device not connecting after changing channel width — 20/40/80 MHz Wi-Fi compatibility

Technician avatar Technician
Hi! Let’s sort out why your device is not connecting after changing channel width so all your phones, laptops, and smart gadgets can get back on Wi-Fi.

When you changed the router’s channel width, did you adjust the 2.4 GHz band, the 5 GHz band, or both? For example, did you switch from 20 MHz to 40 MHz or 80 MHz?

Also, which devices are having trouble now — is it mostly older laptops, smart plugs, printers, or smart TVs, while newer phones still connect? And do the problem devices see the Wi-Fi network but fail to join, or has the Wi-Fi name (SSID) disappeared completely on some of them?

The more detail you can give me about your router model, channel width settings (20/40/80/160 MHz), and which band each device uses, the faster we can fix this “changed channel width, now devices won’t connect” situation.
Customer
I was trying to speed up our Wi-Fi and watched a YouTube video about “wider channels”. In my router (an ASUS dual-band model) I changed the 2.4 GHz channel width from 20 MHz to 40 MHz, and the 5 GHz channel width from 40 MHz to 80 MHz.

After that, my older laptop and a bunch of smart plugs stopped connecting. The laptop sees the 2.4 GHz network but gets stuck on “cannot connect to this network”, and some of the smart plugs don’t see the Wi-Fi at all. Newer phones and my work laptop connect fine to both bands. So basically, after changing the Wi-Fi channel width, some devices connect and some don’t.
Technician avatar Technician
That explains it perfectly. What you’re seeing is a classic device not connecting after changing channel width issue.

On the 2.4 GHz band, you typically have a choice of 20 MHz or 40 MHz channel width. While 40 MHz promises more speed, many older Wi-Fi adapters and IoT devices are picky or outright incompatible with 40 MHz on 2.4 GHz. They expect a standard 20 MHz channel and may refuse to connect, show odd errors, or drop off randomly.

On the 5 GHz band, going from 40 MHz to 80 MHz can also cause issues if a device only supports 20/40 MHz, doesn’t support the channel you picked, or doesn’t like the DFS channels your router chose automatically. That’s why newer phones are fine but older gadgets and smart home devices are not.

We’ll:
• Put your 2.4 GHz channel width back to 20 MHz for maximum compatibility.
• Make sure 5 GHz is using a channel and width your devices actually support.
• Clean up saved Wi-Fi profiles so devices reconnect cleanly after the channel width change.

Once we do that, we should stop this pattern where “I changed Wi-Fi channel width and now my device won’t connect”.
Customer
That makes sense. Right now, on 2.4 GHz I’m set to “Auto channel, 40 MHz” and on 5 GHz it’s “Channel 100, 80 MHz”.

The odd part is: my smart TV and printer can still see the 2.4 GHz Wi-Fi name, but they fail to connect or just loop asking for the password. One older Android phone doesn’t see the 5 GHz network at all anymore. So yeah, after changing channel width and channels, some devices see the network but won’t connect, and some don’t even see it.
Technician avatar Technician
Great detail, thanks. Let’s start with the 2.4 GHz band, because that’s where smart plugs, printers, and older laptops usually live.

Step A — Make 2.4 GHz friendly again (20 MHz, non-crowded channel)
1) Log in to your router’s web interface or app.
2) Go to the Wireless / Wi-Fi settings for the 2.4 GHz band.
3) Set the channel width to 20 MHz only (not Auto, not 20/40 MHz, not 40 MHz). This is the safest choice when a device will not connect after changing channel width.
4) Manually choose channel 1, 6, or 11 (whichever looks least crowded if you have a Wi-Fi analyzer). These are standard non-overlapping channels for 2.4 GHz.
5) Keep the wireless mode on something like “802.11 b/g/n mixed”, not “N-only” or “AX-only”, so legacy devices can connect.

After applying that, give the router a quick reboot. Then, on one of the problem devices (like the old laptop), forget the network and reconnect by typing the Wi-Fi password again. Tell me if it now connects once 2.4 GHz is back to a 20 MHz channel width.
Customer
I changed 2.4 GHz to 20 MHz and set the channel to 6, with b/g/n mixed mode. After a reboot and forgetting the network, the old laptop connects again and the smart plugs are coming back online one by one. So switching back from 40 MHz to 20 MHz on 2.4 GHz absolutely fixed those devices.

But the 5 GHz issue is still there. My older Android phone still doesn’t see the 5 GHz SSID since I set it to 80 MHz on channel 100. Newer phones see it and connect with great speed.
Technician avatar Technician
Perfect — that confirms the first half of the problem was 2.4 GHz set to 40 MHz. Now let’s fix the 5 GHz band so older devices can see and join it again.

A lot of older or budget devices:
• Don’t support all DFS channels (like 100+).
• Are happier with 40 MHz or 80 MHz on channels 36–48.
• May not scan the full 5 GHz range, so they “lose” the network if you move it too high.

Step B — Make 5 GHz visible to more devices
1) In the router’s 5 GHz settings, set the channel width to 40 MHz for now. This is a good balance between speed and compatibility when a device is not connecting after changing 5 GHz channel width.
2) Choose a fixed channel like 36, 40, 44, or 48 instead of “Auto”, and avoid DFS channels (100+).
3) Keep the wireless mode on “ac/ax mixed” or similar so modern devices still get high speeds.
4) Save, reboot the router, and then on that older Android phone, toggle Wi-Fi off/on and rescan.

If you want to chase every last megabit later, we can experiment with 80 MHz again. But first let’s get everything stable and connected at a friendly channel width.
Customer
I switched 5 GHz to a fixed channel 40 at 40 MHz width like you said. After the router rebooted, the older phone finally sees the 5 GHz network again and connects without errors. Speed is still pretty good.

The only remaining issue is one smart bulb that keeps dropping. It’s 2.4 GHz only. Sometimes it joins, sometimes the app says “device offline”. This all started after I first changed the channel width settings, so I’m guessing it’s related.
Technician avatar Technician
Smart bulbs and other IoT devices are extra sensitive to 2.4 GHz settings. Even after you fix channel width, they can still struggle if the network is too “fancy”.

Here’s how to make 2.4 GHz rock-solid for IoT after a channel width change:

Step C — Stabilize 2.4 GHz for smart home devices
• Keep channel width locked at 20 MHz on 2.4 GHz. This is strongly recommended by many vendors for HomeKit, Zigbee/Thread gateways, and cheap IoT gear.
• Stick with channel 1, 6, or 11. Avoid “Auto” so the SSID doesn’t jump around on devices that don’t rescan well.
• Ensure the security is WPA2-PSK (AES). Some bulbs and plugs still choke on WPA3 or mixed WPA2/WPA3 modes.
• If your router has an option like “AX only” or “Wi-Fi 6 only” on 2.4 GHz, turn that off and use b/g/n mixed instead — many IoT chips are 802.11n-only.
• If possible, create a dedicated 2.4 GHz IoT SSID with these conservative settings, so you don’t have to touch them again.

After applying those, remove the bulb from the app, factory-reset it, and add it back while standing close to the router. This usually solves the last edge cases of “device won’t reconnect after changing router channel width”.
Customer
I made a separate 2.4 GHz IoT network with 20 MHz width, channel 11, and WPA2 only. Then I reset the bulb and added it again. It’s been stable for 20 minutes, which is better than before when it kept going offline.

Overall it looks like changing the channel width caused all the weird behavior, and now that we’ve adjusted it properly, everything is working again. Is there a good rule of thumb for what channel width to use on 2.4, 5, and 6 GHz so I don’t break things next time?
Technician avatar Technician
Exactly — the moment you widen channels too aggressively, you can trigger a lot of subtle compatibility issues.

Step D — Channel width best practices
• 2.4 GHz: Use 20 MHz only almost always. It gives the best compatibility and is less likely to cause interference and “device not connecting after changing channel width” problems for legacy and IoT devices.
• 5 GHz: Start with 40 MHz. If your environment isn’t crowded and all devices are happy, you can try 80 MHz on channels 36–48 for more speed. If any device drops off, step back to 40 MHz.
• 6 GHz (if your router has it): Wider channels like 80 MHz or 160 MHz can work well because that band is typically less congested, but only very new devices support it.

In general, stability and compatibility beat raw speed. If changing channel width makes even one important device disappear or fail to connect, it’s better to use a narrower channel and keep everything online, especially for smart home and work-from-home setups.
Customer
That’s really clear. Now I understand why my device stopped connecting after I changed the Wi-Fi channel width. I’ve set 2.4 GHz to 20 MHz, 5 GHz to 40 MHz on channel 40, and left 6 GHz alone for now. Everything (laptops, phones, smart plugs, TV, bulb) is connected and stable.

Is there anything else I should write down or save in case I decide to tweak settings again and mess things up?
Technician avatar Technician
Great question — preventing another “device not connecting after changing channel width” incident is the real win.

Step E — Make today’s working setup easy to restore
• Take screenshots of your 2.4, 5, and 6 GHz settings (SSID, channel, channel width, security mode). Save them somewhere safe.
• If your router lets you export a configuration backup, do it now while everything works. That way, if a future experiment breaks Wi-Fi, you can restore the file and be back to these known-good channel widths in minutes.
• Turn on automatic firmware updates or check for updates regularly — vendors often improve how routers handle channel widths and DFS channels over time.
• Avoid changing multiple things at once (channel, width, security, band). If you do tweak something, write down what you changed so it’s easy to undo.

With that in place, you can safely experiment. And if you ever change channel width again and a device refuses to connect, you’ll know to first try reverting 2.4 GHz to 20 MHz and choosing a low, non-DFS 5 GHz channel.
Customer
Good idea. I just saved screenshots of all the Wi-Fi settings and downloaded a config backup. I feel much better about touching the router now that I know what channel width actually does and how it can make devices vanish.

Everything has stayed connected for the last hour, so I think we’re good. Thanks for helping me fix my Wi-Fi devices not connecting after changing channel width.
Technician avatar Technician
You’re very welcome — nice job working through each step.

Quick recap: If a device won’t connect after you change Wi-Fi channel width, do this:
• Put 2.4 GHz back to 20 MHz on channel 1, 6, or 11 with b/g/n mixed mode.
• Set 5 GHz to 40 MHz on channels 36–48 (avoid DFS until you’ve confirmed every device supports it).
• Use WPA2-PSK (AES) for broad compatibility, especially on IoT gear.
• Forget and reconnect Wi-Fi networks on problem devices to clear old settings.

If at any time you change channel width and suddenly laptops, TVs, or smart home devices stop connecting, you can open a chat with an expert and we’ll walk through the channel width, band, and compatibility checks live with you.
Customer
That summary is super helpful. I’ll keep those settings in mind and call for help if I get adventurous again. For now everything is stable and fast. Thanks a ton for the detailed walkthrough!
Technician avatar Technician
Anytime! If a friend says their device stopped connecting after they changed the router’s channel width, you can share this checklist — 20 MHz on 2.4 GHz, sensible 40/80 MHz on 5 GHz, no weird DFS surprises, and simple security settings.

And if you’d rather have someone click through the router menus with you, just start a chat with an expert and we’ll handle the channel width and Wi-Fi tuning together.

Quick answer: the accepted fix

Accepted fix when a device is not connecting after changing channel width: set the 2.4 GHz band back to 20 MHz on channel 1, 6, or 11, use mixed b/g/n mode, and keep security on WPA2-PSK (AES). On 5 GHz, choose a non-DFS channel (36–48) at 40 MHz, then forget and reconnect Wi-Fi on affected devices so they pick up the new channel width and band settings.

Why devices stop connecting after you change Wi-Fi channel width

When you change the Wi-Fi channel width from 20 MHz to 40/80/160 MHz, you’re widening the “road” your data uses. That can increase speed for compatible devices, but it also changes how your router uses the 2.4 GHz and 5 GHz spectrum. Older adapters, budget smartphones, and many smart home devices are designed and tested assuming a 20 MHz channel width, especially on 2.4 GHz, so they can fail to connect, randomly disconnect, or stop seeing the network after you widen the channel.

Some devices don’t support certain 5 GHz channels or DFS channels at all, and others only support up to 40 MHz. As a result, if you move your 5 GHz SSID to an 80 MHz-wide DFS channel, it’s common for at least one older phone, TV, or laptop to “lose” that network. That’s why a common fix for device not connecting after changing channel width is simply going back to 20 MHz on 2.4 GHz and a moderate 40 MHz width on a low 5 GHz channel.

How to check if the problem is channel width, band, or the device itself

To quickly diagnose device not connecting after changing channel width issues, answer three questions:

First, does the problem device still connect when you temporarily switch 2.4 GHz back to 20 MHz on channel 1, 6, or 11? If yes, its adapter simply doesn’t like 40 MHz on 2.4 GHz. Second, can it see and join a 5 GHz network set to 40 MHz on channels 36–48 but not on 80 MHz DFS channels? That points to 5 GHz channel and width compatibility. Third, does forgetting the Wi-Fi network and reconnecting fix it while other devices are fine? In that case, the router is OK and it’s the device’s saved settings or driver that needs attention.

Device not connecting after changing channel width — quick tips

Use safe channel widths first, then tune for speed once everything connects.

Fast path: put 2.4 GHz on 20 MHz at channel 1, 6, or 11 → set 5 GHz to 40 MHz on channels 36–48 → keep security to WPA2-PSK (AES) → reboot the router and forget/reconnect Wi-Fi on problem devices. Once all devices connect reliably, you can experiment with wider channels on 5 GHz or 6 GHz. If any important device disappears or shows “can’t connect to this network” right after a change, step back to the previous channel width.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router model, Wi-Fi adapters, and smart devices, please consult a verified expert on Whizz-Tech before making decisions.

Getting Started Is Easy

Ask for help, 24/7

Members enjoy round-the-clock access to 12,000+ verified Experts for device not connecting after changing channel width, Wi-Fi network not showing, 2.4 GHz / 5 GHz band issues, and more.

Expert will respond in minutes

We match you with a networking specialist who understands 2.4/5/6 GHz bands, 20/40/80/160 MHz channel widths, interference, and device compatibility for all major router brands.

Save time & money

Stop guessing between 20 MHz and 40/80 MHz or factory-resetting your router every time a device drops. Get a clear step-by-step Wi-Fi channel width fix in chat and get all your devices back online quickly.

FAQ

Why did my device stop connecting after I changed channel width?

Changing from 20 MHz to 40/80/160 MHz can push your network outside what some adapters support, especially on 2.4 GHz. Older laptops, phones, and smart home devices may only be tested with 20 MHz and can fail to connect, loop on password prompts, or stop seeing the SSID. Putting 2.4 GHz back to 20 MHz and using a moderate width on 5 GHz usually restores compatibility.

What channel width should I use on 2.4 GHz Wi-Fi?

For most homes, 20 MHz on 2.4 GHz is the safest choice. It provides the broadest device support and minimizes interference with neighboring networks and Bluetooth devices. Using 40 MHz on 2.4 GHz often causes connection and reliability issues, especially with older or cheaper Wi-Fi and IoT hardware.

What channel width is best for 5 GHz Wi-Fi?

Start with 40 MHz on a fixed channel like 36, 40, 44, or 48. If the environment is not crowded and all devices still connect reliably, you can try 80 MHz for extra speed. If a device disappears or fails to connect after you widen the channel, step back to 40 MHz or choose a different non-DFS channel.

How do I fix smart devices that won’t reconnect after changing channel width?

Put 2.4 GHz back to 20 MHz on channel 1, 6, or 11, use WPA2-PSK (AES), and set the wireless mode to b/g/n mixed. Then factory-reset the smart device, make sure you connect it to the 2.4 GHz SSID only, and complete setup while standing close to the router. Many smart plugs and bulbs require these conservative settings to connect reliably.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.