Wi-Fi security and WPA3 troubleshooting technician providing live chat help

Joe B.

Reviewed for technical accuracy

Specialities: Home networking, Wi-Fi 5/6/6E routers, WPA3 & WPA2 security, Windows/macOS Wi-Fi issues, driver updates, IoT and legacy device compatibility

Fix device not connecting to WPA3 network — WPA3-Personal errors, mixed WPA2/WPA3 mode, Wi-Fi 6 router issues

Technician avatar Technician
Hi! We’ll get your device not connecting to WPA3 network issue fixed and your Wi-Fi secure again. I just need a quick picture of your setup so we can target the right steps.

Which devices are having trouble — Windows laptop, MacBook, Android, iPhone, smart TV, printer, or IoT devices? What exact error do you see: “Can’t connect to this network”, “Incorrect password”, or it just spins and fails?

Also, what kind of router do you have (Wi-Fi 6 / Wi-Fi 6E, brand/model if you know), and in the Wi-Fi settings is security set to WPA3-Personal only, WPA2/WPA3 mixed mode, or something else? That will tell us whether this is a WPA3 compatibility issue or just a configuration glitch.
Customer
I just upgraded to a Wi-Fi 6 router that supports WPA3-Personal. I switched my main SSID from WPA2 to WPA3 only. Since then, my Windows 10 laptop and an older Android phone both refuse to join that Wi-Fi. They see the network, but Windows shows “Can’t connect to this network” and the phone just tries and fails. Newer devices (a Windows 11 laptop and my wife’s iPhone) connect to the WPA3 network fine. So it’s not that the Wi-Fi is completely broken, just certain devices won’t connect to the WPA3 network.
Technician avatar Technician
Got it, that actually fits a common pattern when people first enable WPA3 security.

When a device won’t connect to a WPA3 Wi-Fi network but newer devices work, it’s usually one of these:

• The device’s Wi-Fi adapter or OS doesn’t support WPA3 at all (often older Windows 10, older Android, smart TVs, and printers).
• The adapter technically supports WPA3, but you’re missing a driver or firmware update so it fails with “Can’t connect to this network”.
• The router is set to WPA3-Personal only or has Protected Management Frames (PMF) set to “Required” in a way that some clients don’t like.
• The SSID is in WPA2/WPA3 transition mode, but specific devices get confused by mixed security and constantly fail to complete authentication.

We’ll first confirm whether those devices can actually use WPA3, then decide whether to update drivers, change the router to WPA2/WPA3 mixed mode, or create a separate WPA2 network for older devices.
Customer
The problem devices are an older Windows 10 laptop and a budget Android phone. They both connected fine when the router was on WPA2-PSK before I switched to WPA3. Now with WPA3 only, they just won’t connect, even though I’m sure the password is correct. The router’s wireless security is set to WPA3-Personal (SAE) on both 2.4 and 5 GHz bands. There’s also an option for WPA2/WPA3-Personal mixed mode, but I wasn’t sure which to use.
Technician avatar Technician
Perfect detail. Let’s check whether that Windows 10 laptop truly supports WPA3, and then we’ll pick the best security mode for all your devices.

Step A — Confirm if the device supports WPA3
1) On the Windows 10 laptop, open Command Prompt as administrator.
2) Run this command: netsh wlan show drivers.
3) In the output, look for the “Authentication and cipher supported” section. See if it mentions WPA3-Personal, SAE, or similar. If you only see WPA2-PSK, then that adapter/driver combination doesn’t support WPA3.
4) While you’re there, also check if the driver is from the last year or two; if it’s very old, a driver or Windows update may add WPA3 support.

On the Android phone, WPA3 support is usually determined by the Android version and the phone’s Wi-Fi chipset. If it’s Android 9 or earlier, there’s a good chance it simply can’t connect to WPA3 Wi-Fi at all.

Let me know what you see for the Windows laptop’s supported authentication methods, and we’ll decide whether to stay with mixed WPA2/WPA3 or segment older devices onto a dedicated WPA2 network.
Customer
I ran that command. Under “Authentication and cipher supported” it lists WPA2-Personal, WPA2-Enterprise, but nothing about WPA3 or SAE. The driver is a few years old. Windows Update says I’m up to date. The Android phone is on Android 10 and also doesn’t mention WPA3 anywhere in the Wi-Fi settings. So I’m guessing those two devices just don’t support WPA3 networks.
Technician avatar Technician
Exactly — if the adapter doesn’t list WPA3-Personal in its capabilities, then that device simply cannot join a WPA3-only Wi-Fi network.

The fix is not to force WPA3 on everything, but to balance security and compatibility:

Step B — Pick the right WPA2/WPA3 mode on the router
• Log in to your Wi-Fi 6 router’s admin page or app.
• Go to the wireless settings for your main SSID.
• If your router offers WPA2/WPA3-Personal (mixed mode), that’s usually the best compromise. It lets newer devices connect with WPA3 while older ones fall back to WPA2-PSK securely.
• If “WPA3 only” is currently selected, change it to mixed mode or WPA2-Personal (AES) only, apply changes, then reconnect devices.
• On some routers, you can create a separate SSID: one secured with WPA3-Personal for newer devices and another with WPA2-Personal just for legacy devices like older laptops, phones, printers, and IoT gadgets.

After you switch to WPA2/WPA3 mixed mode or add a dedicated WPA2 SSID, we’ll have your older laptop and Android phone “forget” the network and reconnect with fresh WPA2 profiles.
Customer
I changed the main network to WPA2/WPA3-Personal mixed mode and rebooted the router. The newer devices reconnect fine and show WPA3 in their Wi-Fi details. The old laptop and phone still refuse to connect, though. I’ve tried forgetting the network and re-entering the password, but Windows still says “Can’t connect to this network”.
Technician avatar Technician
Good change — now we’ll make sure those older devices are actually allowed to fall back to WPA2 and aren’t stuck on a bad network profile.

Step C — Clean up Wi-Fi profiles and relax WPA3 options
1) On the Windows laptop, open Command Prompt as admin and run:
  • netsh wlan show profiles (note your Wi-Fi name).
  • netsh wlan delete profile name="YourNetworkName"
  Then reconnect from scratch, making sure you choose the main SSID and enter the password.

2) In the router’s advanced wireless/security section, look for options like “PMF” or “Protected Management Frames”. If it’s set to Required, change it to Optional/Capable. Some older clients fail WPA3 or mixed-mode handshakes when PMF is required.

3) If your router has separate 2.4 GHz and 5 GHz SSIDs, try connecting the older laptop and phone to the 2.4 GHz band first. Many legacy devices behave better on 2.4 GHz when WPA2/WPA3 is enabled.

4) Finally, in Windows Device Manager, open the Wi-Fi adapter’s properties and see if there’s a newer driver from the laptop or Wi-Fi card manufacturer’s website — they often fix weird
WPA3 and WPA2/WPA3 mixed mode issues.

After doing those, try connecting the laptop and phone again. If they still can’t join the mixed WPA3 network, we’ll create a separate pure WPA2-PSK SSID just for them while keeping WPA3 for newer devices.
Customer
I deleted the Wi-Fi profile on the laptop, set PMF to “Optional” on the router, and connected the laptop to the 2.4 GHz band. Now it finally joins the network, but sometimes it shows “No internet, secured” for a bit before it stabilizes. The Android phone also connects to 2.4 GHz now, but occasionally drops off when I move around the house.
Technician avatar Technician
Great — that proves the issue really was WPA3 compatibility and PMF, and those devices are now connecting via WPA2 on the same SSID. We just need to smooth out stability for them.

For older devices on a modern WPA3-capable router:
• Consider creating a second SSID on 2.4 GHz only, secured with WPA2-Personal (AES) and a strong password. Use that “legacy” network only for older laptops, phones, printers, and smart home devices that struggle with WPA3 or mixed mode.
• In the router’s settings, turn off aggressive roaming or “smart connect” features for that legacy SSID so it doesn’t force borderline devices to jump between bands or APs.
• On the Windows laptop, disable random hardware MAC addresses for that SSID and make sure IPv4 and DNS are set to automatic — that helps with “connected but no internet” glitches when roaming.

Your newer WPA3-compatible devices can stay on the main WPA3 or WPA2/WPA3 network for stronger security, and the older gear gets a stable, separate WPA2 network that it can reliably use.
Customer
I set up a separate 2.4 GHz SSID with WPA2-PSK just for older devices and moved the laptop and phone over to that. They connect instantly now and stay online. The main SSID is left on WPA2/WPA3 mixed mode for the newer stuff. Everything seems stable. My only concern is some smart plugs and a printer that still refuse to connect when WPA3 is involved at all.
Technician avatar Technician
That’s very normal. Many IoT devices, smart plugs, and older printers simply don’t support WPA3 at all and can be picky even around WPA2/WPA3 transition mode.

For those devices:
• Always use the 2.4 GHz WPA2-only SSID you created. Most smart home devices expect a plain WPA2-PSK network and will fail if they detect WPA3 or enterprise-style settings.
• Avoid special characters at the very start or end of the Wi-Fi password; some embedded firmware chokes on spaces or symbols there.
• If the router lets you set an IoT or guest network with WPA2-PSK and client isolation, that can be a nice way to keep low-security smart devices separated from your main WPA3 network while still giving them internet.
• Whenever you reset a smart plug or printer, make sure your phone is connected to the same 2.4 GHz WPA2 network during setup so the app doesn’t try to push it onto the wrong SSID.

Once the IoT gear is on that dedicated WPA2 network and your newer phones, laptops, and consoles use the WPA3 or WPA2/WPA3 network, you’ll have the best balance of security and compatibility.
Customer
I moved all the smart plugs and the printer to the 2.4 GHz WPA2 network and they finally connected. The newer devices are staying on the mixed WPA2/WPA3 network and show WPA3-Personal in their details. Everything is working now. Any final suggestions on best WPA3 settings so I don’t break things the next time I change something?
Technician avatar Technician
You’ve got a great setup now — let’s just future-proof it a bit.

Step D — Best practices when a device won’t connect to a WPA3 network
• Keep the main SSID on WPA3-Personal or WPA2/WPA3 mixed mode for laptops, phones, and tablets that support it.
• Use a separate WPA2-PSK 2.4 GHz SSID for legacy and IoT devices that cannot connect to WPA3 networks.
• Set PMF/Management Frame Protection to Optional/Capable instead of Required unless all of your clients explicitly support it.
• Update router firmware and Wi-Fi drivers regularly — vendors often fix WPA3 connection issues and “can’t connect to this network” bugs in updates.
• Before changing security modes, write down your current SSID names and passwords so you can quickly roll back if a device suddenly stops connecting.

With those in place, you get the extra security of WPA3 where it’s supported, without constantly fighting older devices that won’t connect to a WPA3 network. And if something goes sideways, you already know the playbook we just walked through.
Customer
That all makes sense. I’m happy I can use WPA3 on my newer devices without breaking the older ones. Thanks for explaining the WPA2/WPA3 mixed mode and walking me through all the router settings.
Technician avatar Technician
Any time! If a friend or coworker complains that their device won’t connect to a WPA3 Wi-Fi network or turning on WPA3 broke their older gadgets, you can share this checklist — and if you’d like someone to click through the router and Wi-Fi settings with you in real time, just start a chat with an expert and we’ll take it from there.

Quick answer: the accepted fix

Accepted fix when a device is not connecting to a WPA3 network: confirm whether the device actually supports WPA3-Personal, update its Wi-Fi drivers or OS, switch the router from WPA3-only to WPA2/WPA3 mixed mode or create a separate WPA2-PSK 2.4 GHz network for legacy devices, relax PMF from Required to Optional, and have problem devices forget and re-add the Wi-Fi so they can connect using WPA2 while newer devices use WPA3.

Why devices stop connecting when you enable WPA3 security

Most “device not connecting to WPA3 network” problems aren’t random — they come from a mismatch between what your router is broadcasting and what your devices actually support. Older laptops, phones, printers, and IoT gadgets often lack WPA3-Personal support, or they need newer drivers and firmware before they can join a WPA3 or WPA2/WPA3 transition mode network. When the router is set to WPA3-only with PMF required, those legacy clients simply fail to complete authentication and you see errors like “Can’t connect to this network.”

Separating your network into a modern WPA3 or mixed mode SSID for new devices and a WPA2-only SSID for older ones solves most of these issues. It lets new hardware benefit from the stronger encryption and protections of WPA3, while still giving your older gear a stable, compatible WPA2 Wi-Fi network to use.

How to check whether the problem is the device, router, or WPA3 settings

To quickly narrow down a WPA3 connection problem:

First, confirm your router actually supports WPA3 and is running the latest firmware. Then check whether the problem devices list WPA3-Personal or SAE in their Wi-Fi capabilities (for example with netsh wlan show drivers on Windows). If new phones and laptops connect to the WPA3 network but older ones do not, it’s almost always a compatibility or configuration issue rather than a total Wi-Fi failure. Try switching the router to WPA2/WPA3 mixed mode, set PMF to Optional, create a separate WPA2-PSK 2.4 GHz SSID for legacy devices, and have problem devices forget and re-add the network.

Device not connecting to WPA3 network — quick troubleshooting tips

Check WPA3 support, adjust router security mode, then reconnect devices with fresh profiles.

Fast path: verify that the router and device support WPA3-Personal → update router firmware and Wi-Fi drivers → change security from WPA3-only to WPA2/WPA3-Personal mixed mode → set PMF to Optional → have problem devices forget the network and reconnect → if they still can’t join, create a dedicated WPA2-PSK 2.4 GHz network for those legacy devices while keeping WPA3 enabled for newer hardware.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router model, Wi-Fi adapter, and devices that won’t connect to WPA3, 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 to WPA3 network, WPA2/WPA3 mixed mode problems, Wi-Fi 6 router issues, and more.

Expert will respond in minutes

We match you with a networking specialist who knows WPA3-Personal security, WPA2 fallback, Wi-Fi drivers, and router settings for all major brands (Netgear, TP-Link, ASUS, Linksys, and more).

Save time & money

Stop guessing why a device won’t connect to your WPA3 Wi-Fi or breaking older gadgets with new security settings. Get a clear step-by-step WPA3 fix in chat and get back online quickly.

FAQ

Why is my device not connecting to a WPA3 network?

Most of the time, the device either doesn’t support WPA3-Personal or needs updated Wi-Fi drivers or OS patches. Some routers also ship with WPA3-only or PMF “Required,” which older laptops, phones, and IoT devices cannot handle. Switching the router to WPA2/WPA3 mixed mode, relaxing PMF to Optional, and creating a separate WPA2-only SSID for legacy devices usually resolves this.

How do I check if my device supports WPA3?

On Windows, run netsh wlan show drivers and look in the “Authentication” section for WPA3-Personal or SAE. On phones, check the manufacturer’s specs or Wi-Fi settings — newer Wi-Fi 6 and Wi-Fi 6E devices typically support WPA3. If WPA3 is not listed anywhere, that device will not be able to connect to a WPA3-only Wi-Fi network and should use a WPA2-PSK network instead.

Should I use WPA3 only, or WPA2/WPA3 mixed mode?

If every device on your network is new and supports WPA3, using WPA3-Personal only gives the strongest security. In most homes, though, there are older devices that can’t connect to WPA3 networks. In that case, WPA2/WPA3 mixed mode plus a separate WPA2 SSID for stubborn devices is a good balance of security and compatibility.

Is it safe to keep a separate WPA2 network for older devices?

Yes, as long as you use a strong password and AES encryption. For best practice, put legacy and IoT devices on a WPA2-only 2.4 GHz network, keep important computers and phones on a WPA3 or mixed-mode network, and enable features like client isolation or guest mode for less-trusted devices when available on your router.

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.