Phone Link won't connect? Work through these in order
"Connection failed," "Bluetooth pairing failed," "link expired," or paired-but-not-connected — these can all have the same handful of causes. The order matters: start gentle, and only reach for the heavy stuff at the end. Don't throw every fix at it at once.
From my own testing + fixes shared by readers · Verified August 30, 2026
First: is it actually Microsoft's servers?
Do this before anything else
Phone Link's secure cross-device transfer runs on Microsoft's servers, and sometimes those servers have a wobble or a brief outage. If you happen to be linking right when that's happening, no amount of troubleshooting will help — the foundation itself is down. You'll see the same scary errors on both Android and iPhone: connection failed, Bluetooth pairing failed, link expired.
Don't pile fix on fix when it might be the server. Give it time to resolve on its own — generally under an hour. In my testing, waiting roughly an hour was enough to get connected again. Don't blame your phone or PC; sometimes it genuinely isn't you.
If it's still broken after an hour, then it's worth working down the list below.
Reset the network it runs over
On mobile data / hotspot: airplane-mode trick
If you're connecting over a phone hotspot, mobile data sometimes behaves inefficiently. Swipe down to your control panel and turn on Airplane mode for at least 60 seconds, then turn it off. Works on both iPhone and Android, and it cleanly re-establishes the data connection.
On Wi-Fi: restart the router
Turn your router/modem off and on — through its app or the physical switch. In my testing this made connections noticeably more reliable and smooth. (And remember: both devices on the same network matters a lot.)
Same Wi-Fi, still nothing? Check "AP isolation"
Here's a sneaky one that fooled me: your phone and PC can be on the exact same Wi-Fi and still be unable to see each other, because many routers have a setting — called AP isolation or Wireless isolation — that deliberately stops devices on the network from talking to one another. It's common on guest networks and some default router setups. In your router's admin page look under Wireless → Advanced and make sure AP/Wireless isolation is turned off, then reconnect.
Check the hidden Windows toggle
Phone Link can be switched off in Windows — but the setting isn't labeled "Phone Link" and has no obvious on/off. It reads "Allow this PC to access your mobile devices." If that's off, you must turn it on. The catch: while it's off, none of the aka.ms shortcuts work — except aka.ms/MobileDeviceSettings, which opens this exact page (Bluetooth & devices → Mobile devices) so you can flip it on.
Phone Link won't even open from the link?
Two quick things. First, your browser may be blocking the app-launch prompt — allow the pop-up / "Open Phone Link" prompt and try the link again. Second, you can launch the app directly without a browser: press Windows key + R, type ms-phone: and press Enter. If the app isn't installed, get it from the Microsoft Store.
Remove the device and re-pair
If your phone already shows as connected under Settings → Bluetooth & devices → Mobile devices but you're still having trouble, remove the device there and run the pairing again from scratch. A stale, half-broken pairing is a common culprit.
Also clear any half-built Bluetooth or Wi-Fi connections the devices made between themselves: find them by device type/name in your Bluetooth and Wi-Fi lists on both the phone and PC, then forget/disconnect them and start fresh. In my testing, restarting both apps fixed it first; if not, forgetting those stale connections did; only after that did I move to Repair/Reset.
Deliberately unlinking — or removed it and it's still syncing?
If you're removing the phone for good (not just re-pairing to fix a fault), the reliable way is from the phone — and there's a common trap where removing on the PC doesn't stop it syncing, with no error shown. Both are written out step by step, for Android and iPhone, in the dedicated guide: how to disconnect or remove Phone Link →
Connected, but notifications aren't coming through?
That's usually a permission, not a connection. On the phone, make sure notification access is enabled for Link to Windows, and turn off battery optimization for it (so the system doesn't kill it in the background). Then restart both apps. Full permission rundown: what each app needs →
These get confused constantly, and they're two different switches. Battery optimization is the per-app setting above. Battery saver is the system-wide mode that kicks in when you're low — and Microsoft explicitly says to keep it off on both the phone and the PC, because it throttles the background activity the connection depends on. This is a classic intermittent-fault cause: everything works, then your phone hits 20%, saver flips on automatically, and notifications quietly stop. If your connection "only breaks sometimes," check the battery level when it happens.
Everything works except calls — or calls have no audio
Calls are the odd one out: they ride your PC's Bluetooth hands-free audio channel, separate from the Wi-Fi link everything else uses — which is why messages and notifications can be fine while calls fail. Work through: confirm the phone is paired and connected in Windows Settings → Bluetooth & devices (paired-but-not-connected is enough for sync, not for calls); in Phone Link open Calls and complete the extra "set up" prompt if it's showing; check Windows' sound output/input isn't pointed at another device mid-call; and if audio still routes to the phone or drops, remove the Bluetooth pairing on both sides and re-pair. Bluetooth audio is also the first thing wonky USB Bluetooth dongles break — a PC with flaky Bluetooth will show exactly this "everything but calls" pattern.
"Phone Link has been blocked by your system administrator"
Two very different causes behind one message. If your PC or Microsoft account is organization-managed (work or school), this is usually an intentional admin policy, not a fault — details and what to expect: work & school accounts →. But it also hits personal PCs: check Settings → Accounts → Access work or school for a leftover organization account you can disconnect (then restart), make sure third-party security software isn't blocking the app, and if you're on a fresh Windows install, note that a stray policy can ship enabled — the deeper Group Policy / registry cleanup is possible but fiddly, so exhaust the simple checks first. If the PC genuinely belongs to an organization, the honest answer is that only its admin can unblock it.
Mirroring works, but one app is just a black rectangle
Not a bug — and no fix, by design. Apps with hardware DRM or banking-grade screen protection refuse to be recorded, and mirroring is screen recording. Banking apps and streaming services are the usual ones. Audio may keep playing while the picture stays black. Don't reinstall anything; use those apps on the phone directly. Why this happens →
Link to Windows vanished from your phone — or won't install
If the app has disappeared, or the store says it isn't compatible with a phone that worked before, this may not be fixable. Microsoft maintains a supported-device list, and devices get removed from it. Once yours drops off, Link to Windows can become incompatible and disappear, with no supported way back — it isn't a corrupted install and reinstalling won't help. Support is also gated by market, so the same model can qualify in one country and not another. Which phones get what →
Repair, then reset Phone Link
This is the fix for the maddening one — both devices say they're Bluetooth-paired, but Phone Link insists it's not connected. No third-party tools needed.
On your Windows 10/11 PC
- Go to Settings → Apps, scroll to the bottom and open System components.
- Search "Phone Link," click the three dots beside it, then Advanced options.
- Scroll down. First click Terminate to fully close the app.
- Under Reset, click Repair first. Test it.
- If it's still off, click Reset.
I did Repair, then Reset, and it came back working — it didn't even ask me to pair again, since I'd never actually disconnected; it had just glitched itself into a bad state.
If Repair returns "Repairing failed, please try again after some time," it's almost always because Phone Link is still running and can't be repaired while live. Restarting the PC won't help: Windows 10/11 keep two startup processes — Phone Link and Mobile Devices — that relaunch the glitched app on every boot. The fix: go to Settings → Apps → Startup, turn both off, restart the PC, and then Repair — it worked flawlessly for me after that. Turn them back on once you're connected, since they matter for normal use. (Clicking Terminate first gave no success or error prompt — just dead clicks — so don't rely on it alone.)
On your phone (Link to Windows)
Android: go to Settings → Apps → Link to Windows → Storage, tap Clear cache first; if needed, Clear data/storage (this signs you out, so you'll re-pair). Force-stopping the app first also helps.
iPhone: iOS has no per-app repair, so the equivalent is to delete the Link to Windows app and reinstall it from the App Store, then pair again.
Clear Phone Link's LocalState (advanced)
For a stubborn bad connection, clearing Phone Link's LocalState folder — the app's working data — is more thorough than a reset and can clear issues a reset won't. I tested this on a connection that was genuinely stuck, and it brought it back.
Then restart the PC. (Phone Link's package is still named "YourPhone" under the hood, so that path is correct.)
This deletes Phone Link's local data, so you'll re-pair afterward. Run PowerShell as Administrator, and if you're not comfortable with commands, stick to the Repair/Reset in Step 4 instead.
Full clean reinstall (last resort)
If nothing above worked, a complete removal and reinstall is the final step before contacting Microsoft.
With Revo Uninstaller (Portable)
- Run Revo Uninstaller Portable and remove Phone Link plus its leftover registry entries. Always accept the System Restore point when Revo prompts — that's your safety net.
- Then, in Windows Settings, reinstall Phone Link, and turn the "Allow this PC to access your mobile devices" toggle back on.
It's tempting to remove Phone Link with a winget command in PowerShell. Don't. In my testing the uninstall succeeded but Phone Link could not be reinstalled afterward — the only way to get it back was a full Windows reset. Use the Repair/Reset or the Revo method instead.
A more unusual approach I've used to force a stubborn connection: USB tethering. Connect the phone in USB tethering mode so it shows up as a new "router" device, disable your main internet and leave the phone's USB routing as the only connection, then open Phone Link — it connects. Once linked, switch your main internet back on and use it normally.
Still stuck? Talk to Microsoft
If you've genuinely worked through all of the above and it still won't connect, this is the point to contact a Microsoft live chat agent — it may be an account- or server-side issue only they can see. That's the honest last resort, not the first move.
Did this get you connected?
Thanks for the feedback — it helps me keep this accurate.
Questions & answers
Comments are moderated — real questions get answered, spam and links are removed. Found a fix that worked for you? Share it — if I can reproduce it, I may add it here.
FAQ
My PC gets slow and Cross Device Service is eating memory.
A long-running set of user reports — going back to 2023 and not formally confirmed by Microsoft — describes Cross Device Service consuming enormous amounts of RAM (reports range from 15 GB to about 30 GB) until the machine crawls. The catch that hides the cause: this is the background broker for clipboard sharing, notification sync, remote control and Resume, so closing the Phone Link window doesn't stop it, and the name in Task Manager doesn't say "Phone Link". Reversible ladder, in order: update Windows, Phone Link and the phone-side app; end Cross Device Service in Task Manager (containment only — it can restart); disable the Mobile devices entry under Task Manager → Startup apps; or unlink Phone Link entirely. Do not use removal scripts or delete Windows packages — Phone Link is deeply integrated and forced removal can break servicing. The cost of mitigating is losing clipboard sharing, notification sync, remote control and Resume.
Windows keeps showing a "Microsoft account problem" notification.
That prompt covers several different conditions, one of which is a Phone Link pairing mismatch. Before you unlink and re-pair anything, check that Windows and Link to Windows are signed in with the same Microsoft account, then open Settings → System → Shared experiences on the PC — if it offers Fix now under Accounts, run that repair first. It resolves the account-state version of this without touching your pairing.
Phone Link says "connection failed" — is it my fault?
Not necessarily. Microsoft's servers occasionally have outages, and the same errors appear on both Android and iPhone when that happens. Wait up to an hour before troubleshooting your devices.
Both devices say paired, but Phone Link says not connected.
Repair, then reset Phone Link in Settings → Apps → System components → Phone Link → Advanced options (Terminate first). If that fails, clear its LocalState folder, then as a last resort do a clean reinstall.
I can't find a "Phone Link" on/off setting in Windows.
It's labeled "Allow this PC to access your mobile devices," under Bluetooth & devices → Mobile devices. aka.ms/MobileDeviceSettings opens it directly.
The Android (or iPhone) button does nothing when I add a second device.
Not you, and not your phone. With one platform already linked, I found the other platform's button on the "Add a mobile device" screen simply doesn't open the next screen — adding a second phone of the same type works fine. Unlinking didn't clear it; a PC restart after removing the device did. The full tested detail →
Can I uninstall Phone Link with winget?
Avoid it. In testing the winget uninstall worked but Phone Link couldn't be reinstalled, requiring a full Windows reset. Use Repair/Reset or Revo Uninstaller instead.
"Your Android device went to sleep. Wake it up" — and the button does nothing.
The PC is asking for something the phone's power management has already killed. Unlock the phone and open Link to Windows so it's foreground, turn off battery optimization for it, and try again; if the button still does nothing, restart both apps and reconnect. Users report this appearing after major Android/One UI updates too — see the next answer.
A big phone update (like One UI) just landed and now it won't connect.
A recurring pattern users report after major Android updates: permissions and background exemptions get reset or re-interpreted, and the old pairing goes stale. Re-grant Link to Windows' permissions and battery exemption first; if that doesn't do it, remove the link on both sides and pair fresh — full steps in the disconnect guide.
Phone Link keeps crashing on the PC (PhoneExperienceHost errors).
PhoneExperienceHost.exe is Phone Link's process — if Windows' Event Viewer shows it faulting, that's an app-corruption problem, not a pairing problem. Go straight to Step 4's Repair, then Reset; the local-data deletion in Step 5 is the deeper version of the same fix.
People say Phone Link froze their phone — can that happen?
There have been credible user reports (notably on some Galaxy models) of phones becoming intermittently unresponsive with Phone Link connected, recovering once the PC app closes. I haven't reproduced it on my devices, so I won't claim it as tested — but if your phone freezes only while linked, the diagnostic is easy: turn Link to Windows off for a day. If the freezes stop, unlink and re-pair cleanly, and keep the phone-side app updated.
"File failed to send. We are unable to reach [my PC name]."
Sent from an iPhone via Link to Windows? Then this message is pointing at the wrong device. Your PC isn't blocked or unreachable — file sharing is refusing because the iPhone is signed in with a different Microsoft account from the PC. Everything else keeps working, which is why it's so easy to misread. Don't touch your firewall or network: check the account on both devices →
"Send to phone" asks me to sign in, or does nothing.
On iPhone this is almost always a Microsoft account mismatch. Everything else keeps working, so the link looks healthy — but file sharing needs the same account on both devices, and Windows only says so at the moment you try to send. "Maybe later" closes the window without sending. The full tested sequence and the fix →
My phone finished pairing, but the PC never connected.
Classic mismatched-account symptom. If you signed in on the phone with a different Microsoft account from the one on your PC, the phone-side flow completes convincingly while the PC never moves — and the final screen is blurred, with a panel saying "Almost there! Let's add your PC… sign in with [your email]." That's not a last step, it's a failure notice. The full tested detail and the fix →
Do both devices need the same Microsoft account?
Yes — the phone and PC must be signed in to the same Microsoft account, and a mismatch is a common silent cause. Check what's linked at account.microsoft.com/devices and confirm your phone is listed under the account you're using on the PC.
Pairing won't accept my code / I'm locked out.
Too many failed attempts to match the code between PC and phone will block linking for security. Close and reopen Phone Link on your PC and start setup again — you'll be asked to accept permissions instead of matching a code. See also the QR-code fixes.
Could another app be blocking the connection?
Yes. Other phone-to-PC linking tools can conflict — Samsung DeX, Intel Unison, or a manufacturer app like Virtoo by LG. Close, disable, or sign out of them, remove the pairing, and link again. Running DeX alongside Phone Link is a known troublemaker.
Did you rename your phone or PC recently?
Renaming either device can invalidate the stored pairing, so syncing quietly stops. Remove the pairing on both sides — forget the PC in your phone's Bluetooth settings, and remove the phone under the PC's Bluetooth & devices — then pair again so both sides register the new name.
On iPhone, could Low Power Mode or Background App Refresh be the cause?
Yes — both are easy to miss on iPhone. Low Power Mode throttles the background activity Phone Link depends on, so syncing and notifications can stall; switch it off while you're connected. And Background App Refresh has to be on for Link to Windows — check Settings → General → Background App Refresh and make sure it's enabled, then reconnect.
I can't find Phone Link in the Microsoft Store.
Known trap — the Store's search doesn't surface Phone Link, even though the app is there and its page opens fine by direct link. Don't search the Store: use www.aka.ms/PhoneLink in your PC's browser, search "Phone Link" in the Start menu, or run ms-phone: — all land on the app directly. The tested detail →
I set it up during Windows' first-run and now it's glitchy — is that why?
Very likely. In my testing, pairing during the out-of-box experience (OOBE) is far more prone to half-connecting and glitching than pairing from the desktop. Remove the link cleanly — from the phone (Link to Windows → profile → Settings → See your PC → ⋯ → Remove), or with the "Add a mobile device" reset on the PC (both in the disconnect guide) — finish Windows setup fully, then pair again from the desktop.
Keep reading: disconnect or remove Phone Link · requirements & specs · device modes that block setup · tested alternatives
A curious techy from Traverse City, Michigan. Every fix on this page is one I've reproduced and verified myself in the actual problem environment — where something first surfaced in a community like Reddit or the Microsoft Forums, I tested it before publishing. I run SyncYourDevice.com with no ads and keep this list current as the apps change.
Tested on: Phone Link (Windows) 1.26071.164.0 · Link to Windows (Android) 1.26071.104.0 · (iOS) 1.26081.28 — verified August 30, 2026.
Article updates
August 2026
- Added tiers for call/audio failures and the "blocked by your system administrator" message, plus FAQs for sleep/wake, post-update breakage, PhoneExperienceHost crashes, Cross Device Service memory reports and the Microsoft account repair path.
- Verified against Phone Link 1.26071.164.0, Link to Windows 1.26071.104.0 (Android) and 1.26081.28 (iOS).
- Tracking what changes across the apps themselves? That lives on the what's new in Phone Link timeline.
July 2026
- Added tiers for call/audio failures and the "blocked by your system administrator" message, plus FAQ entries for the sleep/wake error, post-update breakage, PhoneExperienceHost crashes and reported phone freezes.
- Reviewed and updated for the current Phone Link and Link to Windows versions.