Network troubleshooting technician providing live Wi-Fi security help

Joe B.

Reviewed for technical accuracy

Specialities: Home networking, Wi-Fi routers, WPA2/WPA3 security, Windows/macOS Wi-Fi issues, DNS & IP configuration, ISP setup

Fix device not connecting to WPA2/WPA3 mixed mode — Wi-Fi authentication problems, “can’t connect to this network”, WPA3 compatibility issues

Technician avatar Technician
Hi! We’ll get your device not connecting to WPA2/WPA3 mixed mode issue sorted so everything can join your Wi-Fi again.

To start, can you tell me:
• What router model you have and whether it’s a Wi-Fi 5, Wi-Fi 6, or Wi-Fi 6E router?
• Which devices are failing — for example, an older Windows 10 laptop, Android phone, smart TV, printer, or IoT device?
• What exact message you see when the device tries to connect: “Can’t connect to this network”, “Incorrect password”, “Authentication error”, or something else?

Also, in the router’s wireless/security settings, does it show the network mode as WPA2/WPA3 mixed, WPA3-Personal (SAE) only, or something like “WPA2-PSK + WPA3-SAE transition mode”? That detail helps us decide whether we should tweak the router, the device, or both.
Customer
I have a new Wi-Fi 6 router from my ISP. There’s one main SSID for everything, and they told me to enable WPA2/WPA3 mixed mode so it’s “more secure.”

Since then, my iPhone and newer laptop connect fine using WPA3, but my older Windows 10 laptop and a Wi-Fi printer refuse to join. On the laptop I get “Can’t connect to this network” right after typing the password. On the printer, it just says the password is incorrect even though I’m sure it’s right.
Technician avatar Technician
That’s a textbook WPA2/WPA3 mixed mode not working scenario.

In WPA2/WPA3 transition mode, your router advertises both WPA2-Personal (PSK) and WPA3-Personal (SAE) on the same SSID. Newer devices negotiate WPA3, while older devices should fall back to WPA2. In reality, some older Wi-Fi cards, outdated drivers, and legacy IoT devices see the mixed network but can’t complete the handshake, so you get vague errors like “Can’t connect to this network” or “Incorrect password”.

We’ll:
• Confirm which devices actually support WPA3 and which are WPA2-only.
• Adjust the router’s security mode and “transition mode” settings so WPA2-only devices can connect reliably.
• Update Wi-Fi drivers/OS on the laptop so it handles WPA3 or mixed mode properly where possible.

The goal is to keep the network as secure as we can without locking out your older devices.
Customer
That makes sense. The ISP app just had a toggle for “WPA3 + WPA2 (recommended)” and I turned it on. Before that, everything was set to WPA2-Personal only and all devices worked.

The Windows 10 laptop is a few years old, and I doubt the printer supports WPA3 at all. I’d prefer not to buy new hardware just to use WPA3 if there’s a way to fix the WPA2/WPA3 mixed mode connection problem.
Technician avatar Technician
Totally fair — we’ll test first, then decide how strict we want to be with security.

Step A — Confirm WPA2 works cleanly
1) In the router app or web UI, temporarily change the main SSID’s security from WPA2/WPA3 mixed mode back to WPA2-Personal (WPA2-PSK) only.
2) Keep the same Wi-Fi name and password. Save/apply, then wait ~30 seconds.
3) On the old Windows 10 laptop, “Forget” the network, then reconnect and enter the password again.
4) Do the same on the printer: re-run its Wi-Fi setup and point it to the SSID again.

If those devices connect immediately under WPA2-only, we’ve confirmed the problem is specifically with WPA3 or mixed mode compatibility, not the password or basic Wi-Fi signal. Then we can decide whether to:
• Keep the main network on WPA2 for full compatibility, or
• Use a second SSID — one WPA3-only for newer phones/laptops and one WPA2-only for legacy devices.
Customer
I switched the main SSID back to WPA2-Personal only. After forgetting and reconnecting, both the old laptop and the printer connect instantly again. No more “Can’t connect to this network” errors.

But I’d still like the extra security of WPA3 for the newer devices if possible. The router lets me choose WPA2, WPA3, or WPA2/WPA3 mixed mode per SSID.
Technician avatar Technician
Great — that proves the hardware is fine and the real issue is how the devices handle WPA2/WPA3 mixed mode.

A good compromise is:
• One SSID for WPA3-Personal only (for newer phones, tablets, and laptops).
• One SSID for WPA2-Personal only (for the older Windows 10 laptop, printer, smart devices).

Mixed mode sounds ideal, but in practice it can trigger odd behavior: some clients mis-detect the security type, some drivers get confused by WPA3-SAE and PMF/802.11w requirements, and some IoT devices simply cannot parse the beacon. That’s why you see authentication errors and “password incorrect” even when the passphrase is right.

If you’re okay having two Wi-Fi names, we’ll:
1) Rename the current network to something like “Home-WPA3” and set it to WPA3-Personal only.
2) Create a second SSID “Home-WPA2” set to WPA2-Personal only with the same or a different password.
3) Move newer devices to the WPA3 network and keep the legacy devices on WPA2.
Customer
I can do that. I created “Home-WPA3” as WPA3-Personal and “Home-Legacy” as WPA2-Personal. My iPhone and new laptop connect fine to the WPA3 SSID.

The older laptop still won’t connect to the WPA3 network though — it sees the SSID, but when I try, it again says “Can’t connect to this network.” I guess that one will have to stay on WPA2 only?
Technician avatar Technician
Right, that’s expected for many older machines.

Step B — Check WPA3 support on the laptop
1) On the Windows laptop, update Windows 10 to the latest build it supports.
2) Update the Wi-Fi adapter driver from the laptop or Wi-Fi card manufacturer (Intel, Realtek, etc.). WPA3 support often comes from driver/OS updates, not just the router.
3) In a Command Prompt, you can run netsh wlan show drivers and look for “WPA3-Personal” under supported authentication types.

If it doesn’t list WPA3 at all, that adapter simply doesn’t support WPA3 and will never join a WPA3-only network. In that case, you have three options:
• Leave it on the WPA2 SSID (most common).
• Add a cheap USB Wi-Fi adapter that explicitly supports WPA3.
• Or accept that this one device will remain on WPA2 while everything else uses WPA3.

The key point: your problem isn’t the password — it’s a capability mismatch between older hardware and WPA3 / WPA2/WPA3 mixed mode.
Customer
I checked, and the command doesn’t list WPA3 in the supported auth types. So I’ll just keep that laptop on the WPA2 network for now.

One more thing: my Android phone connects to the WPA3 network, but occasionally I get an “Authentication error” when it roams between rooms, then it reconnects after a couple of seconds. Is that also related to WPA2/WPA3 mixed mode or WPA3?
Technician avatar Technician
Good question — that’s more about how WPA3 handles management frame protection (PMF/802.11w) and roaming than mixed mode itself, but they’re related.

On some routers, enabling WPA3 or WPA2/WPA3 transition mode automatically forces PMF to “required.” A few Android devices, or older firmware builds, briefly struggle with this and show “Authentication error” during roaming.

Step C — Smooth out WPA3 connections on phones
• Make sure your phone is on the latest Android or iOS version available.
• In the router’s Wi-Fi security settings, if there’s an option for PMF/802.11w, set it to “Required” only on the WPA3 SSID and “Optional” or “Disabled” on the WPA2 SSID.
• Avoid re-enabling global WPA2/WPA3 mixed mode on a single SSID for now; keep the WPA3 SSID pure WPA3 and the legacy SSID pure WPA2.
• If your router has advanced roaming options like 802.11r Fast Transition, try toggling it; some devices behave better with it off when combined with WPA3.

After that, monitor whether the “authentication error” popups disappear or at least become rare.
Customer
I updated the phone and changed the PMF setting as you suggested. The authentication errors seem to have stopped, and roaming feels smoother.

So right now I’ve got “Home-WPA3” for newer stuff and “Home-Legacy” for WPA2-only gear. Everything connects. Anything else I should do so I don’t break things again if I touch the WPA2/WPA3 settings in the future?
Technician avatar Technician
You’ve done the hard part — now we just make the setup future-proof.

Step D — Make sure WPA2/WPA3 changes don’t break devices again
• Take screenshots of your current Wi-Fi security configuration for both SSIDs (mode, encryption, PMF setting). If you ever reset the router, you can rebuild exactly what works.
• Avoid flipping the main SSID back to a single WPA2/WPA3 mixed mode unless the router vendor specifically recommends it for your devices — a dual-SSID approach is often more stable.
• Periodically check for firmware updates on the router; vendors steadily improve WPA3 and transition mode behavior.
• If you retire the last legacy device, you can then switch everything to WPA3-Personal only and remove the WPA2 network completely.

That way you keep security high without running into the “device not connecting to WPA2/WPA3 mixed mode” trap again.
Customer
Got it. I’ve saved screenshots and won’t mess with mixed mode on the main SSID anymore. With the two networks, everything is stable and I still get WPA3 on newer devices.

Thanks for walking me through this — the ISP support just told me to “restart everything” and didn’t explain why certain devices can’t connect in WPA2/WPA3 mixed mode.
Technician avatar Technician
You’re very welcome — you did all the right tests.

Summary: When a device is not connecting to WPA2/WPA3 mixed mode, it’s usually because the client doesn’t fully support WPA3 or transition mode, not because the password is wrong. The clean fix is to:
• Verify devices can still connect to a WPA2-only SSID.
• Use separate SSIDs for WPA3-only and WPA2-only instead of one mixed network.
• Update router firmware and client drivers so WPA3 and PMF are properly supported.

If you ever change routers or upgrade devices and run into WPA3 or mixed-mode issues again — “Can’t connect to this network”, “incorrect password”, or random auth failures — you can open a chat with an expert and we’ll review the exact security settings with you live.
Customer
Perfect. Everything’s working now, and I understand what WPA2/WPA3 mixed mode actually does. I’ll reach out again if I replace the router or that old laptop. Thanks!
Technician avatar Technician
Glad to hear it! If a friend says their device won’t connect after enabling WPA3 or their WPA2/WPA3 mixed mode network only works for some devices, you can share this checklist — and if you’d like someone to go through the router’s Wi-Fi security page 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 WPA2/WPA3 mixed mode: confirm the device can join a WPA2-only network, then either keep that device on a separate WPA2 SSID or update its OS and Wi-Fi drivers so it supports WPA3 / transition mode. On the router, prefer using separate WPA3-only and WPA2-only SSIDs instead of a single mixed network if older devices show “Can’t connect to this network” or “incorrect password” errors.

Why devices fail to connect to WPA2/WPA3 mixed mode (drivers, hardware, transition mode)

Most WPA2/WPA3 mixed mode connection problems are caused by older Wi-Fi adapters, outdated drivers, or buggy implementations of WPA3 transition mode. The router announces both WPA2 and WPA3, but the client’s Wi-Fi stack doesn’t fully understand WPA3-SAE, management frame protection (PMF), or new security capabilities. As a result, you see “Can’t connect to this network”, “Wi-Fi authentication problem”, or a generic wrong-password error even when the passphrase is correct.

Another common cause is that the device supports WPA2 only, while the router is configured as WPA3-only or has strict WPA3 settings with PMF required. Some IoT devices, printers, and older laptops only handle WPA2-PSK (AES) and will never connect to WPA3 or strict WPA2/WPA3 mixed mode. Splitting the network into separate WPA3 and WPA2 SSIDs avoids these compatibility traps while keeping security as strong as possible for newer clients.

How to check if it’s the router, Wi-Fi security mode, or the device

To quickly narrow down a device not connecting to WPA2/WPA3 mixed mode issue, test in stages:

First, set the SSID to WPA2-Personal only. If the problem device connects immediately, the hardware and password are fine and the problem is specifically with WPA3 or mixed mode. Next, try a separate WPA3-only SSID and see which devices can join; if some devices don’t even support WPA3 in their driver capabilities, they must stay on WPA2.

If no devices can connect after enabling WPA3, check the router’s firmware version and security settings (PMF, SAE, transition mode). Updating firmware, disabling experimental features, or reverting to a simpler WPA2/WPA3 configuration often restores compatibility. When only one client fails and others work fine, focus on that device’s OS updates and Wi-Fi drivers rather than the router.

Device not connecting to WPA2/WPA3 mixed mode — quick troubleshooting tips

Check device capabilities first, then adjust WPA2/WPA3 security and SSIDs instead of guessing.

Fast path: test the device on a WPA2-only SSID → if it works, the issue is WPA3/transition mode, not the password → create separate WPA3 and WPA2 networks instead of one mixed SSID → update router firmware and client Wi-Fi drivers → confirm whether the adapter actually supports WPA3-Personal. This approach resolves most “can’t connect to this WPA2/WPA3 mixed mode network” problems without having to replace every older device immediately.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router model, Wi-Fi adapter, and device list, 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 WPA2/WPA3 mixed mode, WPA3 Wi-Fi authentication errors, incorrect password issues, and more.

Expert will respond in minutes

We match you with a networking specialist who knows WPA2/WPA3 transition mode, WPA3-Personal (SAE), PMF, and Wi-Fi driver quirks on Windows, macOS, Android, and iOS.

Save time & money

Skip hours of trial and error with WPA2/WPA3 mixed mode. Get a clear step-by-step Wi-Fi security fix in chat and keep both new and legacy devices online safely.

FAQ

Why won’t my device connect to a WPA2/WPA3 mixed mode Wi-Fi network?

Usually this means the device doesn’t fully support WPA3 or transition mode, or its Wi-Fi driver is outdated. The router advertises both WPA2 and WPA3, but the client fails the handshake and shows “Can’t connect to this network” or “incorrect password.” Testing the device on a WPA2-only SSID is the quickest way to confirm it’s a WPA3 compatibility problem rather than a bad password.

Is it better to use WPA2/WPA3 mixed mode or separate WPA2 and WPA3 networks?

WPA2/WPA3 mixed mode is convenient but can cause compatibility issues with older devices. For many home networks, using separate SSIDs — one WPA3-only for newer phones/laptops and one WPA2-only for legacy devices — is more reliable. You still benefit from WPA3 security where it’s supported while avoiding constant connection errors on older hardware.

How do I fix “Can’t connect to this network” after enabling WPA3?

First, switch the SSID back to WPA2-Personal and see if the device connects. If it does, update the device’s OS and Wi-Fi drivers, then try again with a separate WPA3-only SSID. If the adapter still doesn’t list WPA3 in its supported authentication types, keep that device on a WPA2-only network or add a newer Wi-Fi adapter that supports WPA3.

When should I switch my whole network to WPA3-only?

Once every device you care about supports WPA3-Personal and connects without issues, you can turn off the WPA2 SSID and run the network as WPA3-only for better protection. Before doing that, make a list of any printers, IoT gadgets, or older laptops that still rely on WPA2, and plan either to replace them or keep a small separate WPA2 network just for those legacy devices.

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.