Windows Wi‑Fi connects but cannot obtain an IPv4 address

A static IP can be useful as a temporary workaround, but it will not fix the underlying DHCP problem. It also has to match the network you are connected to, so an address that works at home will not necessarily work on your phone hotspot. I would use this mainly as a diagnostic test rather than the permanent solution.

Check whether the adapter’s MAC address is being randomized or whether any network access-control software is installed. A router block is possible on a home network, but it would not explain the same failure on a phone hotspot unless the laptop itself is applying some restriction. Testing with all VPN and security-network components disabled can help narrow that down.

Try booting a Linux live USB without installing anything. If Wi‑Fi works and you can browse normally there, the hardware is likely fine and the issue is isolated to Windows, its drivers, or installed networking software. That would make a Windows repair or reinstall a more sensible next step.

A 169.254.x.x address is Windows assigning itself an address because DHCP failed. Since it happens on both your router and a phone hotspot, the problem is probably on the laptop rather than with either network. Check for VPN clients, third-party antivirus, virtual network adapters, or other filtering software that could be interfering with DHCP. You could also try the laptop manufacturer’s Wi‑Fi driver, an older driver version, or a clean driver removal followed by installation.