Your phone finds every other phone in the room and refuses to see the laptop sitting eighteen inches away, and you have turned Bluetooth off and on four times.
There is a line in Google's own requirements that explains this, and almost nobody reads it. It is about a Bluetooth capability your PC either has or does not.
I read that capability on this laptop before writing, expecting a yes, and got a no.
What Google actually requires
Short list, and three of the four are obvious.
⭐ Google says the machine must be "A computer with a 64-bit version of Windows 10 and up", adding that "ARM-based devices require Windows 11 and up".
⚡ Both devices need Bluetooth on and either "Wi-Fi" or "Ethernet" enabled, and Google's instruction is to "Connect to the same network".
⚠️ And they must be close: "within 16 feet or 5 meters of each other".
⛔ Meeting all of that and still being invisible is where people give up. The reason is one line further down.
The requirement that explains most failures
Read this one twice. It is a hardware answer to a software-shaped problem.
⭐ Google states it outright on its Quick Share help page: "If your Windows device doesn't support Bluetooth Low Energy (BLE) Extended Advertising, other people can't find and share with you on certain networks."
⚡ Extended advertising is a Bluetooth 5 feature. It lets a device announce itself with far more information than the old format allowed.
⚠️ Without it, your PC's announcement is capped at 31 bytes. That is not always enough for the phone to recognize what it found.
⛔ No setting turns this on. The radio either does it or it does not, and Windows only reports which.
What this laptop reports
Measured here, and it was not the answer I expected.
⭐ Low energy Bluetooth: supported. Central role: supported. Peripheral role: supported. All the usual boxes ticked.
⚡ Extended advertising: not supported. Maximum advertisement data length: 31 bytes, which is the old legacy limit exactly. Yours may say the same.
⚠️ This is a current laptop on Windows 11 build 26200 with a Wi-Fi 6 adapter. It still says no.
⛔ So this is not an old hardware problem. ⚠️ Plenty of machines being sold now will answer the same way.
How to read your own
One paste, and it is longer than it looks because it wakes a Windows component.
⚡ Open Terminal and paste all five lines at once. Nothing is changed and nothing is installed.
Add-Type -AssemblyName System.Runtime.WindowsRuntime
$m = [System.WindowsRuntimeSystemExtensions].GetMethods() | Where-Object { $_.Name -eq 'AsTask' -and $_.GetParameters().Count -eq 1 -and $_.GetParameters()[0].ParameterType.Name -eq 'IAsyncOperation`1' }
$t = $m[0].MakeGenericMethod([Windows.Devices.Bluetooth.BluetoothAdapter]).Invoke($null, @([Windows.Devices.Bluetooth.BluetoothAdapter]::GetDefaultAsync()))
$t.Wait(8000) | Out-Null
$t.Result | Select-Object IsLowEnergySupported, IsExtendedAdvertisingSupported, MaxAdvertisementDataLength⭐ False on the middle one is the answer to why your phone cannot see the PC in a crowded place.
⚠️ A length of 31 confirms it without needing to trust the flag on its own.
⛔ A length in the hundreds means your radio is fine and the problem is somewhere in the next two sections.
Visibility, which catches everybody at least once
Second commonest cause, and it resets itself more than people expect.
⭐ Google lists four choices: "Everyone", "Contacts", "Your devices" and "No one".
⚡ Everyone is the one that changes under you. On phones it drops back on its own, which is sensible and infuriating in equal measure.
⚠️ Your devices only works when both are signed in to the same Google account. A work phone and a personal laptop are not the same account.
⛔ Set it deliberately before you start looking for faults. Half the invisible-PC reports end here.
What to do when the flag says no
The workaround is in Google's own wording, and it is the phrase "on certain networks".
⭐ Put both devices on the same Wi-Fi network. That is the condition Google attaches to the whole requirement.
⚡ Guest networks and work networks are the usual saboteurs, because they isolate clients from each other on purpose.
⚠️ A phone on mobile data and a laptop on Wi-Fi are not on the same network. Obvious once said, and easy to miss.
⛔ If your router has separate names for its two bands, put both devices on the same one. Split band names cause this repeatedly.
When to stop fighting it
There are three faster routes and no prize for stubbornness, and the call is ours.
⚡ A cable moves everything with no discovery at all. Slower to start, faster to finish, and it never fails to see anything.
⭐ Phone Link handles photos and messages without any of the requirements on this page.
⚠️ Cloud storage is the boring answer that always works. Check what is already syncing before you set up anything new.
⛔ And if the whole reason for this was moving to a new handset, that is a different job. Do it in the right order.
Status: Bluetooth adapter capabilities read on this laptop on 28 August 2026, Windows 11 Home build 26200, alongside Google's own Quick Share requirements. ⛔ Nothing was paired, changed or transferred, no device, account or network name is published, and no file of anybody's was sent.
Why can my phone not find my PC on Quick Share?
Often because the PC's Bluetooth radio does not support Low Energy Extended Advertising. Google documents that a Windows device without it cannot be found on certain networks. Put both devices on the same Wi-Fi network, and check your visibility setting, before assuming anything is broken.
What does Quick Share need on Windows?
A 64-bit version of Windows 10 or newer, with ARM machines needing Windows 11 or newer. Bluetooth switched on, Wi-Fi or Ethernet enabled, both devices on the same network, and within about 16 feet or 5 meters of each other.
How do I check if my PC supports BLE Extended Advertising?
Paste the five line command in this article into Terminal. It reports three values from the Bluetooth adapter. If extended advertising says False and the maximum advertisement data length is 31, your radio is using the old legacy format and no setting will change that.
The Short Version
- Google requires 64-bit Windows 10 or newer, Bluetooth, and the same network.
- Devices must be within 16 feet or 5 meters.
- The hidden requirement is Bluetooth Low Energy Extended Advertising.
- Without it, Google says other people cannot find and share with you.
- This laptop reports it as not supported, at the legacy 31 byte limit.
- No setting turns it on. The radio either does it or it does not.
- Same Wi-Fi network is the workaround Google's own wording points at.
- Visibility resets. Check it before looking for a fault.
Where to Next
Check the visibility setting first, because it costs ten seconds and explains half of these.
Then get both devices onto the same Wi-Fi network, and the same band if your router splits them.
If it still cannot see the PC, read the Bluetooth flag. A False there ends the guessing.
When the flag says no, stop fighting it and use a cable or the cloud for anything large.
And if you have found a laptop that reports extended advertising as supported, say what year it is from in the comments. Nobody publishes which machines do.
Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.