You type the password, it connects for a moment, then asks again. Or it accepts it and drops an hour later with another prompt. Repeated password requests almost never mean the password is wrong. They mean the authentication handshake is failing, and there are only a handful of reasons for that.
The short answer
Forget the network on the device and rejoin from scratch, which clears a corrupted stored profile. If it recurs, check the router’s security mode: a device that only supports WPA2 will fail repeatedly against a WPA3-only network, and the error it shows is a password prompt rather than anything useful. Setting the router to WPA2/WPA3 mixed mode resolves it.
Why it looks like a password problem when it is not
Joining a Wi-Fi network involves a four-step exchange that proves both sides know the password without sending it. If any part of that exchange fails, for any reason, the device reports it the only way it knows how: by asking for the password again. So the prompt is a generic failure message, not a statement about your password.
The things that break the exchange:
- A security standard mismatch. WPA3-only networks reject older devices, which then ask for the password endlessly.
- A corrupted stored profile. The device has cached keys that no longer match.
- MAC filtering. The router refuses the device, and the device interprets the refusal as an authentication failure.
- A full address pool. The router accepts the password and then has no address to give, and some devices retry the whole join.
- A weak signal. The exchange is time-sensitive and fails if packets are lost.
- MAC randomisation. The device appears as a new unknown client to a router configured with device rules.
Forget the network and rejoin
On the device, remove the network completely rather than just disconnecting. Restart the device, then join again and type the password carefully. Watch for autocorrect capitalising the first letter, which catches people constantly on phones.
Check the router's security mode
Log into the router and look at the wireless security setting. If it is WPA3 only, change it to WPA2/WPA3 mixed. Older laptops, smart home devices, printers and games consoles frequently cannot do WPA3, and the symptom is exactly this.
Check for MAC filtering or a device block list
Look for an allow list, a block list, or parental controls that might have caught the device. A device blocked by a schedule set up months ago fails in exactly this way.
Restart the router to free the address pool
If the router has run out of addresses, devices authenticate and then fail. A restart releases every lease at once. If it recurs monthly, widen the address range in the settings.
Turn off MAC address randomisation for your home network
Modern phones present a random hardware address per network, and can generate a new one after an update, which makes them unknown to a router with device rules. In the network’s settings on the phone, switch to using the device address for your home network specifically.
Check signal strength where the device sits
A marginal signal causes the handshake to fail intermittently, and the device asks again. If the prompts only happen in one room, that is your answer and no configuration change will fix it.
Simplify the password temporarily
Some older devices handle certain characters badly, particularly ampersands, percent signs and quotes. As a test, set a long but purely alphanumeric password. Remember every device will need reconnecting.
Reset network settings on the device
This rebuilds the whole wireless configuration. You will need to re-enter passwords for every network, so it is a step with a cost, but it clears corruption that forgetting one network does not reach.
Test the device on a phone hotspot. If it joins that without complaint, the device is fine and the problem is a setting on your router. If it asks for the password on the hotspot too, the device’s wireless configuration is the problem.
The WPA3 trap
This deserves emphasis because it has become common. Newer routers increasingly default to WPA3, or to a transition mode that some devices still handle badly. A laptop from a few years ago, a printer, a smart plug or a games console may have no WPA3 support at all. They see a network they cannot authenticate against and prompt for the password forever.
Mixed WPA2/WPA3 mode is the practical answer for a home network with a mix of ages. You keep the stronger standard for devices that support it while remaining compatible with everything else. It is slightly less secure in theory than WPA3-only, and vastly more usable in practice.
If only one device is affected and everything else on the network is fine, do not start changing router settings. The fault is on that device, and changing the router risks breaking things that currently work.
When only the guest network does it
Guest networks often have their own quirks: client isolation, shorter lease times, session timeouts that disconnect devices after a set period, and sometimes a separate security setting. If the prompts only happen on guest Wi-Fi, check its timeout setting first, because many routers disconnect guest clients on a timer by design.
Why does my phone say the password is wrong when it is right?
Because the prompt is a generic failure message. Any breakdown in the authentication exchange produces it, including a security standard mismatch, a corrupted profile or a router that is refusing the device.
What is WPA3 and why would it break my devices?
The current Wi-Fi security standard. Devices more than a few years old often do not support it, and on a WPA3-only network they fail to authenticate and ask for the password repeatedly. Mixed mode solves it.
Does MAC randomisation cause this?
It can, if your router uses MAC filtering, fixed address reservations or per-device rules. The phone appears as a new unknown device and is refused.
Why does it happen only in one room?
A weak signal. The authentication exchange is time-sensitive, and lost packets make it fail. The device then asks again rather than reporting a signal problem.
Will changing my Wi-Fi password fix it?
Rarely, and it means reconnecting every device in the house. Try forgetting the network on the affected device first, and check the router’s security mode.
The bottom line
Forget the network and rejoin on the affected device, because a corrupted profile is the most common single cause. If it comes back, look at the router’s security mode, since a WPA3-only network quietly locks out older devices and reports it as a password problem. Treat one affected device as a device problem and the whole house as a router problem.
