Hi,
Please refer to Emily's answer in this thread.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
Hoping someone's hit this exact sequence before. Timeline of what happened and what I've tried:
Setup: Windows 11 25H2, Phone Link on PC, Bold K50 (Android) with Link to Windows app.
Initial symptom: Phone Link showed the K50 as "Offline" with grayed-out Bluetooth/Wi-Fi/battery icons. Clicking the status revealed: "Your Microsoft Account needs attention. You may need to update your password to reconnect."
Steps taken so far, in order:
Current theory: This is the 24-hour token propagation window MS warned about, not a local Bluetooth/Wi-Fi/permissions issue, since I've ruled those out individually.
Question: Has anyone actually hit this specific combo (MS password reset → sign-out-everywhere → Phone Link re-pair failure) and can confirm whether it's really just a wait-it-out situation, or if there's a cache/token somewhere on the Windows side that needs manual clearing to unstick it sooner? Open to Phone Link diagnostic logs / advanced reset options if that'd help someone help me.
Thanks so much for any help and guidance.
Richard
Hi,
Please refer to Emily's answer in this thread.
Things seems to be functioning well enough but every morning when I boot up the computer and Phone Link starts up it asks me to scan a code for the WiFi, that's annoying. Was never an issue before. Please fix this. Thanks~!
AI answer
The supported next steps are to fully unlink and re-pair, then reset the app if the loop continues.
Because the error shown is "Something went wrong", the documented causes are usually that the PC and Android device lost connection. Check these specifically:
Also verify these connection prerequisites:
If the pairing loop still continues, the documented escalation is to reset the app or unlink the Android device and set it up again. A similar accepted resolution for Phone Link repeatedly failing to open was:
The provided material does not confirm a required 24-hour Microsoft account token propagation wait for Phone Link, and it does not document any manual Windows-side token/cache clearing beyond unlinking, repairing, resetting, and pairing again.