Quick Share Not Working Between Android and Windows?

Verdict: When Quick Share fails between Android and Windows, first check the receiving device: the correct PC app must be installed, receiving must be enabled, and both devices need working wireless connections. Test one small file in each direction to distinguish a discovery problem from a missing approval request or a transfer that starts and then fails.

Start with a one-file test

Place the phone beside the PC and open Quick Share on both. Pick a recent screenshot or another small, non-sensitive file that opens normally on its original device. Send it from the phone to the computer, then send a different file back. Note the last successful stage: recipient listed, request displayed, request accepted, or file received.

This is a diagnostic method, not a performance benchmark. A successful send in one direction does not establish that the other device’s receiving settings are correct. Keep the failed direction in mind while following the checks below.

The table narrows the next check; none of these symptoms alone proves a hardware fault.

Check the app and receiving settings

1. Install the appropriate Windows app

Use Google’s Quick Share download page for a non-Samsung PC. Google directs Samsung PC owners to Samsung’s Microsoft Store app and says Google’s Windows app is no longer supported on Samsung PCs. A Samsung phone connected to another brand’s PC does not make that PC a Samsung computer.

Google lists Android 6 or later and 64-bit Windows 10 or later for its general requirements. Its current Help Center lists Windows 11 or later for ARM computers; the download page still contains a contradictory ARM footnote. If your installer reports an unsupported device, check the current requirements for that exact PC rather than assuming every Windows laptop qualifies.

Also check what you opened: Windows Nearby sharing is Microsoft’s feature for sharing between Windows PCs. Its settings are not the receiving settings for Google’s Quick Share app.

2. Make the recipient discoverable

On Android, search Settings for Quick Share, then open its receiving screen. Keep the screen on and enter your passcode if it is locked. Google’s Android instructions say receiving mode makes the device visible to people nearby while that screen remains open; leaving it ends that temporary visibility. Galaxy labels can differ.

In Google’s Windows app, check Settings > Device visibility. Restricting reception to your own devices requires the same Google Account. Choose a receiving option appropriate to this sender; restore your preferred restriction after testing. See Google’s Windows sharing guide.

On a Galaxy Book, Samsung documents a receiving menu offering nearby people or contacts. Its app also offers a link-sharing route. A link opened in a browser is a different test from discovering a nearby device: note which route you used when reporting a failure.

3. Check Android’s basic discovery conditions

Google recommends Bluetooth on, devices within about 30 centimeters during troubleshooting, and no competing transfer to the recipient. Android 12 and earlier also require checking that Location is enabled. If discovery remains stuck, restart the phone and repeat the same small-file test. These are Google’s documented troubleshooting checks, not a reason to change unrelated app permissions.

When the device appears but the file will not arrive

4. Inspect the request on Windows

Keep the receiving app visible for one attempt. In Windows 11, go to Settings > System > Notifications. Enable notifications for the app and check whether banners are allowed. Turn off Do not disturb for the test, or review notification center: Microsoft explains that muted notifications can go there without showing a banner. Check automatic rules if this only happens during games, full-screen apps or display duplication. See Microsoft’s notification guidance.

Keep the distinction precise: a missing banner does not necessarily mean the phone failed to find the PC. Google says transfers between your own devices using the same Google Account are accepted automatically. Otherwise, record whether the recipient appears on the sender and whether a request exists inside the receiving app.

5. Compare networks without changing the file

Enable Wi-Fi and use the same network. For office networks that block local sharing, Google’s network workaround is: disable the phone’s Wi-Fi, enable its hotspot, then connect the PC there. Follow workplace policies. Background internet activity can use your mobile allowance.

If the same file now transfers, report the network-dependent result to the network administrator. It narrows the investigation but does not identify a particular router setting. If the hotspot itself cannot provide internet, use the separate hotspot internet troubleshooting guide.

6. Check the documented PC limitations

Google says to avoid administrator mode, which can disrupt drag-and-drop. Missing Bluetooth Low Energy Extended Advertising can also prevent discovery on some networks. Ask the PC manufacturer about that capability; a working Bluetooth mouse is not a sufficient compatibility test.

Find the received file and decide what to do next

Android saves received Quick Share content in the default file manager under Downloads > Quick Share, according to Google’s Android guide. For Google’s Windows app, check the Quick Share folder inside Downloads. Open the received item before deleting the original.

If only one item fails, compare its behavior with another locally available file. If several small files fail, preserve the exact error, PC model, Windows version, phone model, app used, transfer direction and results on each network. That is more useful for Google, Samsung or your PC support team than a report that sharing “doesn’t work.”

A Quick Share failure alone does not establish that the phone needs repair. For an urgent transfer, use a data-capable USB cable; our phone-to-computer USB troubleshooting guide covers that separate connection path.

Research basis: official Google, Samsung and Microsoft documentation checked on October 8, 2026, with AI-assisted synthesis. No hands-on transfer-speed or device reliability testing is claimed.