📶 Troubleshoot Nearby Share and Quick Share for Windows

Medium25-35 minutesMulti-Device Ecosystem Synchronization

Last updated: January 22, 2026

Fix discovery failures, transfer speed problems, and configuration issues with Windows Nearby Sharing and Quick Share between devices.

Not sure this is your exact issue? Every WindowsHelper guide is scoped to one specific problem — not a generic troubleshooting checklist — so if the title above matches what you're seeing, this is the right guide.

What Nearby Share and Quick Share actually do

Nearby Share (and its close cousin, Quick Share) is Windows' built-in way to send files directly to another nearby device, a phone or another PC, without emailing them, uploading them somewhere first, or plugging in a cable. It's meant for short-range, device-to-device transfers of photos, documents, and other files.

This is different from features that hand off a snippet of text or a clipboard between devices, and it's not the same as Phone Link, which is about seeing your phone's calls and texts on your PC. This one is specifically about moving actual files from one device to another close by. When it doesn't work, it's usually one of two shapes: the two devices never find each other, or they find each other but the transfer crawls along far slower than it should for files sitting a few feet apart.

How to tell this is a discovery or speed problem

How serious is it?

Usually minor

This is a discovery and speed problem, not a sign anything is broken. Your files and both devices are unaffected either way.

Worth taking seriously

If you're relying on it for something time-sensitive, retrying the same attempt over and over without knowing why the devices aren't finding each other can eat up more time than it saves.

Why turning it off and on again doesn't explain the failure

Nearby Share depends on more than one thing lining up at the same time: both devices need to be discoverable, close enough, and often on compatible networks or radios, so a failure can come from either side, not just the PC in front of you. Toggling the feature off and on can occasionally jolt it back to life, but it doesn't tell you why it failed in the first place, so there's a good chance it happens again.

Working out whether the trouble is discovery, the devices never see each other, or the transfer itself, they connect, but slowly, is what WindowsHelper is being built to help you tell apart, rather than leaving you to retry the same toggle each time.

What this helps with

What to expect: Medium difficulty • usually about 25-35 minutes.

Topics covered
configurationdevicesdiscoveryecosystemfailuresissues

This is one of 25 Multi-Device Ecosystem Synchronization fixes in the WindowsHelper library. The full step-by-step fix for this is in the WindowsHelper app.

Coming soon in the app

The full step-by-step fix for this is in the WindowsHelper phone app — coming soon, no price announced yet. The free PC Companion (available now) is the piece that connects your phone to your PC.

🔔 Get notified at launch
Share: Share on X Share on Facebook Share by email

Common questions

Why doesn't the other device show up in the list?
That points to a discovery problem: the two devices haven't found each other yet, which is a different situation from finding each other and then transferring slowly.
Is this the same as copying and pasting between devices?
No. This feature sends whole files between nearby devices. Copying text or a clipboard between devices is a separate feature with its own way of working.
Is this connected to seeing my phone's texts on my PC?
No, that's a different feature entirely. This one is specifically about sending files from one device to another nearby one.
Why is the transfer so slow for a small file?
A slow transfer between nearby devices is often a clue that the connection being used is a weaker fallback rather than the fastest option available, which is worth understanding rather than just waiting it out.

Related fixes in Multi-Device Ecosystem Synchronization

You might also run into

Browse all 1,000+ fixes →