How to Fix Nearby Share Not Working on Windows?

When Nearby Share stops working between Android and Windows, the first thing to check is the name you are actually using. Google’s Android sharing feature is now Quick Share, while Microsoft’s Nearby sharing is a separate Windows feature for sharing between Windows PCs.

That name overlap causes a lot of false troubleshooting. Your Android phone can be fine, Bluetooth can be on, and Windows can still show a sharing panel that will never discover the phone because it is not the Google Quick Share app.

Once the correct app is open, the symptom becomes easier to read. If the PC never appears, focus on the Windows package, visibility, Bluetooth, and distance. If the PC appears but no accept prompt shows up, check Windows notifications. If the transfer starts and then crawls or fails, look at Wi-Fi, Ethernet, or the network profile.

1. Use Quick Share, Not Windows Nearby Sharing

This is the mistake that wastes the most time. Windows Nearby sharing may look like the right setting because the old Android name was Nearby Share, but Microsoft’s feature is for supported Windows devices. Android-to-Windows transfers need Google’s Quick Share path on the PC.

1. On Windows, do not start from Settings > System > Nearby sharing when you are trying to receive from Android. Open the Quick Share app instead.

   

2. Confirm the PC is supported: Google lists 64-bit Windows 10 or newer for regular PCs, and Windows 11 or newer for ARM-based PCs.
3. Confirm the phone is running Android 6 or newer and has Quick Share available from the Share sheet, Quick Settings, or Settings search.
4. Make sure both Bluetooth and Wi-Fi are turned on before testing.
5. If this is a Samsung PC, install Samsung Quick Share from the Microsoft Store instead of using Google’s Windows package.

   

6. On a non-Samsung PC, install Quick Share from Google’s official Android/Quick Share download page.
7. If you previously forced Quick Share to run as administrator, turn that compatibility setting off for this clean test. Google’s Windows help says Quick Share should be run from a normal Windows account.

If the Android phone starts seeing the PC after the correct package is installed, the issue was never the phone. If the right Quick Share app is already open and the PC is still invisible, fix visibility next.

2. Make the PC Visible and Restart Quick Share from the Tray

Quick Share can be installed and open while still advertising the PC to nobody. The Your devices and Contacts modes depend on account matching, saved contacts, and signed-in state, so Everyone is the cleanest temporary test.

1. Open Quick Share on Windows and sign in with the same Google Account used on the Android phone if you want to test Your devices.
2. Open Settings > Device visibility and make sure receiving is not set to No one.

   

3. Temporarily choose Everyone, then try sending a small photo from Android again.
4. On the Android phone, keep the screen unlocked and open the Quick Share receive or sharing screen during the test.
5. If nothing changes, right-click the Quick Share icon in the Windows tray, choose Quit, and reopen the app.

   

If the PC appears under Everyone, change visibility back to the privacy level you want after the transfer test. If no visibility option makes the devices find each other, the problem is probably in Bluetooth discovery or the local network.

3. Rebuild the Bluetooth and Local Network Path

Quick Share does not use one single connection the whole time. Bluetooth helps nearby devices discover each other, while Wi-Fi, Wi-Fi Direct, Ethernet, or a local network route may carry the actual file transfer. That is why a device can appear once and then stall, or transfer in one direction but not the other.

1. Turn Bluetooth and Wi-Fi on for both the Android phone and the Windows PC.

   

2. Bring the phone and PC close together. Google’s Windows page says the devices should be within about 5 meters, and its Android troubleshooting page recommends going even closer during a failed test.
3. If the Android phone is on Android 12 or earlier, turn on Location for the discovery test.
4. Connect both devices to the same home Wi-Fi network when possible. If Windows asks whether the network is public or private, use a Private network for a trusted home network.
5. If you are on office, hotel, campus, guest, or public Wi-Fi, turn on the phone’s hotspot and connect the PC to it for one comparison.

   

6. Turn Airplane mode on and off on the phone, then reopen Quick Share.
7. Restart both devices once if discovery is still stuck after the radio and network checks.

If the hotspot or private network works, the original network was isolating devices or slowing local transfer traffic. If the devices still cannot find each other anywhere, check Windows notifications and the Bluetooth driver before reinstalling Quick Share.

4. Allow the Windows Accept Prompt and Repair Bluetooth if Discovery Is Unstable

Sometimes the Android phone finds the PC, but the receiving side never shows the banner you need to accept the transfer. Windows notification settings can hide that prompt, and a weak Bluetooth driver can make discovery disappear again after one attempt.

1. Open Settings > System > Notifications in Windows and make sure notifications are enabled.
2. Find Quick Share in the app list and allow it to show notifications.

   

3. Turn off Do not disturb or Focus assist for the test, then send one small file again.
4. If Quick Share still vanishes during discovery, open Device Manager > Bluetooth, right-click the real Bluetooth adapter, and choose Update driver.
5. Install pending Windows updates and restart the PC.

   

6. If other Bluetooth devices are also unreliable on this PC, install the Bluetooth and Wi-Fi drivers from the PC manufacturer’s support page rather than relying only on a generic driver scan.

If the accept banner appears now, the transfer was being blocked at the Windows notification or Bluetooth layer. If Quick Share itself opens blank, crashes, loses the right-click entry, or keeps ignoring saved settings, reset the app install next.

5. Reinstall the Correct Quick Share Package

A reinstall is worth saving for last because it will not fix the wrong Windows feature, a hidden receive setting, or a blocked guest network. It does help when the Windows app is damaged, stuck in the background, missing its context-menu entry, or still behaving like the old Nearby Share build after updates.

1. Uninstall the current Quick Share app from Windows.
2. Restart the PC before installing it again.

   

3. Install Google Quick Share on a supported non-Samsung PC, or Samsung Quick Share on a Samsung PC.
4. Open Quick Share from a normal Windows account, sign in if needed, and set visibility to Everyone for the first test.
5. Send one small photo from Android before testing a folder, large video, or many files at once.

If the clean install works, the Windows Quick Share state was damaged. If it still fails on a supported PC, the remaining causes are usually PC-specific Bluetooth/Wi-Fi compatibility, a managed network policy, or an account/visibility mismatch that the local app cannot override.