Phone paired w PC can't connect.

Anonymous
2025-06-24T00:40:25+00:00

Android 13 Bluetooth (BT) pairs with Win 11 PC but can't connect. Recommendation for a similar prob was to remove BT driver, but PC Device Manager has 7 for BT, including 3 for phone. The 3 for the phone seem unrelated because they follow a very recent renaming. Is there no better solution? Problem occurred after resetting Phone Link system component (which Copilot recommended for a minor texting issue (all my replies to one thread showed by themselves in another)) that now seems completely unrelated to Phone Link.

Windows for home | Windows 11 | Connect Phone and PC

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2025-06-25T17:00:43+00:00

    Hi Stev,

    Hopefully everything works out this time.

    Regards,

    Tin

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-06-25T16:40:48+00:00

    Hello Tin, thank you for the update.  It may be a few days before I can try something new.  Your patience appreciated.  R, Stev C

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-06-24T21:37:16+00:00

    Hi,

    Thank you for the concise documentation and annotations; you've really worked hard on this. From your response, we can now refine the troubleshooting process and suggest likely culprits and the next best steps. Here is an outline of where we are and how we go forward.

    ***Summary of Key Observations from Your Notes:

    Bluetooth pairing succeeds, but the device is not "Connected", which is crucial for Phone Link to work.

    Phone Link was reset and reinstalled, but linking showed Microsoft Server Error 2605.

    Before, the phone tried to get access to your router IP (192.168.x.1) during linking- which, clearly, it was not supposed to.

    You have already used PowerShell to remove Phone Link and redownloaded it after.

    App on Android Link to Windows is fully reset and permissions reviewed.

    Root Causes Likely at Play:

    1. Residual Microsoft account device entanglement (cloud-side mismatch)

    Even with a local reset, your phone might still be linked somewhere in your Microsoft account backend, creating a broken association that results in error 2605 (which is usually a cloud sync or authentication issue).

    1. Bluetooth Profile Conflict or Mis-binding

    Even showing completed pairing, it still does not trigger full "Connected" state-a bug on certain combinations of Windows 11 and Android 13+ devices.

    1. Corrupt Appx provisioning / missing Phone Link UWP package

    Your PowerShell uninstall may not have fully cleared any provisioning traces of Phone Link, and this will cause the installation to be incomplete.

    Step-by-Step Fix (Refined + Targeted)

    A. Fully Unlink from Microsoft Account Cloud

    On your PC browser:

    Go to: https://account.microsoft.com/devices

    Find any instances of your phone and click "Unlink" or "Remove phone from account".

    Shop for your PC too if there's any Link to Windows association.

    On your Phone:

    Open Link to Windows app.

    Tap the account profile (top-right or menu) → Sign out if still signed in.

    Go to Settings > Accounts >Microsoft account, and remove the account if it was added for Link to Windows only.

    On your PC:

    Open Phone Link app.

    Click settings (gear icon) → Sign out if still signed in.

    If it's still found in Settings > Bluetooth > Mobile Devices, remove the device(s).

    Then reboot both phone and PC.

    B. Clean Reinstall of Phone Link (Correctly)

    This way, your Phone Link will now be correctly installed.

    Open PowerShell as Administrator, run

    Get-AppxPackage *yourphone* -AllUsers | Remove-AppxPackage

    Get-AppxProvisionedPackage -Online | Where-Object {$_.DisplayName -like "*yourphone*"} | Remove-AppxProvisionedPackage -Online

    Now install fresh from Microsoft Store:

    Phone Link - Microsoft Store

    After install, confirm it appears in Settings > Apps > Installed apps, and from there, do Advanced Options > Reset just in case.

    C. Correct Pairing Flow (No Microsoft Account Yet)

    This time, don't sign in to Microsoft account right away. Just:

    Pair via Bluetooth: PC initiates pairing.

    On phone, approve the pairing.

    Confirm that PC Device Manager > Bluetooth shows the phone as Connected, not just "Paired".

    If it still won't connect, try:

    Device Manager > Bluetooth > right-click the phone > Enable Service (if shown)

    Settings > Devices > remove, reboot both, try again.

    Optional: Enable Developer Option Logging on Android

    To gather more insight:

    Enable Developer Mode on your phone: Settings > About phone > tap Build Number 7x

    Go to Settings > Developer Options → enable:

    Bluetooth HCI snoop log

    Verbose logging

    Retry pairing. If it fails, export the logs for deeper analysis.

    Regards,

    Tin

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-06-24T20:03:30+00:00

    Hi Tin; Thanks for your response.  Since my attempt to diagnose & repair this has been repetitive & difficult (consuming the better part of the last four days) I will annotate each step in reply.  My inline notes marked with “>>sc>>

            Reference Info (only if my configuration matters—the solution may still work for others):

    Phones: (OS & Apps up-to-date) Samsung Galaxy xCover Pro (original) w Android 13 (2 copies, one in-use for 1.5 years & an identical in-the-box (new old stock) backup hardware w/o SIM.

    PCs: Desktop & Notebook, Win 11 (up-to-date), near-top-end Lenovo, AMD 16 & 12 core. The Desktop, shipped w Win 10, was updated to Win 11 a few months back without any effect on Phone Link operation. 

    From: Microsoft Community

    Sent: 23 June, 2025 22:22

    To: StvC

    Subject: Question has a reply: Phone paired w PC can't connect.

    Hi! Thanks for writing. I am Tin, and I am an independent advisor. I am so happy to offer you any needed assistance today. This is a typical mismatched Bluetooth profile or perhaps more corrupted pairing metadata and really not a core Bluetooth driver issue.

     >>sc>> “Not a core BT issue” sounds reasonable as a symptom not previously mentioned was that during the registration process (between Phone Link (P-L) & Link to Windows (LtW) ) my phone would use the default browser to try & open my Router-modem address (192.168.x.1) (which always failed as it did not include a Username or Password).

    >>sc>> for all Tin’s following PC steps my Notebook and backup phone are OFF and changes are only applied to my Desktop PC and primary phone.  Any on-the-phone steps are applied for both PCs.

    Instead of nuking all your BT drivers, here is a more targeted solution:

    1: Clean Out Broken Pairing Info

    Pair your PC and phone with both your phone and PC.

    >>sc>> just a “writing directions” editorial note: the next two lines should start w “On PC” or “On Phone” for maximum clarity & to minimize confusion.

    Go to Bluetooth & devices on your PC, select your phone and Remove device. >>sc>> Done.

    Settings → Connected devices on your Android phone: tap the PC → Forget.

    >>sc>> On my ‘droid 13, there “Forget” does not exist but I can do Settings > Connected Devices > LtW > Linked Account > (where I see both PCs Disconnected) > Account Settings > Sign Out

    Then (assuming your intent) Settings > Connections > Bluetooth > Desktop > Unpair (‘droid goes back a screen to Bluetooth) Available Devices (now appears) > Desktop > (where only option is Pair, so I do nothing).

    Clear your PC's cache for pairing records for the phone:

    Open Registry Editor (regedit) and go to:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices

    Each subkey here is a device. You can match your phone's Bluetooth MAC address (you'll find this in your phone's BT settings).  

    >>sc>> Searching all my phone’s settings, there is no MAC for BT, only Wi-Fi, Phone Wi-Fi, & Ethernet.  In Device Manager > Bluetooth I see 3 of the PC’s BT drivers include the name of the recently changed BT Device Name for the phone.  Looking at Properties > Details lists about 75 values, but nothing like MAC, Media Access Control, or Hardware Address.  Could the Phone’s BT use the same MAC that my Wi-Fi router sees?

    Delete the key corresponding to your phone.

    >>sc>> In REGEDIT, two devices listed, cannot tell if either is phone (might be other PC or Kindle) so deleting both… now nothing under Devices.

    Restart PC and phone.

    2: Reset Phone Link Data (if that caused it) >>sc>> if the P-L Reset did not cause this problem then it was something in the typical process of reconnecting the PC & Phone as I have not been able to make P-L work since then.

    If resetting Phone Link definitely triggered the issue, it is possibly conflicting with residues of corrupted data affecting the Bluetooth service.

    Completely reset Phone Link settings on PC:

    Go to Settings > Apps > Installed Apps → search for Phone Link → click Advanced Options → choose Reset.

    >>sc>> a segue here:  P-L not found here.  For others it might be because it is a Win 11 Component after that upgrade or in my case it is likely because the last step of the last fix I was trying was to use the PowerShell command “Get-AppxPackage Microsoft.YourPhone -AllUsers | Remove-AppxPackage” to completely remove Phone Link.  Sooo, searching from Settings > Home, gets me to switching P-L ON, and I get a popup prompt to Download and Install Phone Link (P-L).  After P-L downloads and is ON, still no P-L under Installed Apps so I search for it but none of the items found include a Reset button.  One item found (searching for Phone Link) is Settings > Bluetooth > Mobile Devices and Mobile Devices is OFF.  I turn it on and a Mobile Devices popup shows my phone and that it Cannot Reach this Device, so I click Remove (from account).

    OK, BACK from SEGUE:

    Go to the phone and clear Bluetooth permissions and data:

    Long-press Link to Windows app → App info → Storage & cache → Clear Storage and Cache.

    Revoke Bluetooth and notification access and enable them afresh.

    >>sc>> Long pressing the LtW app icon in my phone’s app drawer only offers “Select.”  On my phone I have to goto Settings > Apps > LtW > Storage to see Clear Data & Clear Cache buttons.

    3: Reconnect Cleanly

    Initiate pairing from your PC, not from the phone. That way, you will avoid Android's tendency to preselect limited BT profile.

    >>sc>> Since my PC was already at Settings > Bluetooth… > Mobile Devices, I clicked Open Phone Link button to initiate the paring process.  I click Android, scan the QR code w phone’s camera, get code to enter on PC, click Continue on phone, enter code, & Continue on phone gives is a spinning donut… (PC still shows the code) phone goes to Microsoft Server Error 2605.  This was seen MANY times during previous attempts.  This time the phone did not try to open a browser to my router.  While it never worked previously, I’m clicking Try Again on phone… donut spins long time, code on PC good for 3 min, so on PC click Cancel and Phone Link goes back to 1^st^ screen.

    After pairing:

    Inspect Device Manager > Bluetooth for new entries. If the phone shows as "paired", but not connected, right-click and choose Connect, or enable service manually.

    >>sc>> After failed paring, no new BT in PC’s Device Manager.  On PC, Settings > BT > devices, nothing new. On PC, Add BT Device sees phone & Phone sees PC.  PC initiates paring, phone replies, approval buttons clicked, BT devices pared but not Connected.

    Could you please try out these steps and let me know if it works out? And, in case that any other error arises, I would love to have more information it.

    Best regards,

    Tin

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-06-24T02:17:11+00:00

    Hi! Thanks for writing. I am Tin, and I am an independent advisor. I am so happy to offer you any needed assistance today. This is a typical mismatched Bluetooth profile or perhaps more corrupted pairing metadata and really not a core Bluetooth driver issue.

    Instead of nuking all your BT drivers, here is a more targeted solution:

    1: Clean Out Broken Pairing Info

    Pair your PC and phone with both your phone and PC.

    Go to Bluetooth & devices on your PC, select your phone and Remove device.

    Settings → Connected devices on your Android phone: tap the PC → Forget.

    Clear your PC's cache for pairing records for the phone:

    Open Registry Editor (regedit) and go to:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices

    Each subkey here is a device. You can match your phone's Bluetooth MAC address (you'll find this in your phone's BT settings).

    Delete the key corresponding to your phone.

    Restart PC and phone.

    2: Reset Phone Link Data (if that caused it)

    If resetting Phone Link definitely triggered the issue, it is possibly conflicting with residues of corrupted data affecting the Bluetooth service.

    Completely reset Phone Link settings on PC:

    Go to Settings > Apps > Installed Apps → search for Phone Link → click Advanced Options → choose Reset.

    Go to the phone and clear Bluetooth permissions and data:

    Long-press Link to Windows app → App info → Storage & cache → Clear Storage and Cache.

    Revoke Bluetooth and notification access and enable them afresh.

    3: Reconnect Cleanly

    Initiate pairing from your PC, not from the phone. That way, you will avoid Android's tendency to preselect limited BT profile.

    After pairing:

    Inspect Device Manager > Bluetooth for new entries. If the phone shows as "paired", but not connected, right-click and choose Connect, or enable service manually.

    Could you please try out these steps and let me know if it works out? And, in case that any other error arises, I would love to have more information it.

    Best regards,

    Tin

    Was this answer helpful?

    0 comments No comments