Solution 1:

This actually sounds like a problem with the infrastructure – it usually happens when the Wi-Fi access point cannot reach the authentication server. Eduroam uses WPA-Enterprise, and the Wi-Fi APs do not process your password directly but instead relay it to the institution's central RADIUS server, then send the response back. It is very possible that one of the nearby APs has lost its wired connection to the institution network but continues to broadcast a (strong but useless) Wi-Fi signal and keeps getting chosen by your computers as the preferred AP.

Talk to whoever is managing the Eduroam Wi-Fi hardware at your location.

Additionally, if you're not at your home institution (that is, if the "@realm" in your username is different than where you're connecting), it could also be a problem with the connection between the two institutions. (Make sure you do add the @domain suffix to the username, as some sites deliberately reject Eduroam logins without one.)

If you had a Linux system, Wireshark would be able to show the 'EAPOL' packets being exchanged over the Wi-Fi adapter during authentication, but it probably wouldn't reveal a lot. As this doesn't need "monitor mode" it might also work with Wireshark on Windows and/or macOS as well.