Updated September 8, 2026 · Published by FarsiVid
When Quick Share is not working between Android and Windows, identify the stage that fails before changing settings. A PC that never appears in the device list has a different problem from a visible PC that rejects a transfer, or a successful transfer whose file you cannot find.
Start with one small, harmless file and keep both devices nearby. This guide separates compatibility, discovery, acceptance, transfer and receipt so you can make one useful change at a time.
Check compatibility and the correct Windows app
Google’s Quick Share for Windows page lists the Windows and Android requirements and provides the official download. The current requirements include 64-bit Windows 10 or later, with Windows 11 or later for ARM PCs, and Android 6 or later. Supported hardware and regional availability still matter.
The Windows setup help directs Samsung PC users to Samsung’s Quick Share version. It lists Iran, Cuba, North Korea and Syria as unavailable locations. Check compatibility before reinstalling.
Confirm the app publisher before installing. A similarly named app is not evidence that you have the supported Google or Samsung package.
Use a small receipt test
On the sending device, create a plain-text note or a small image with a recognizable filename, such as transfer-check-2026-09-08.txt. If using text, put a unique line inside it: FarsiVid transfer check: blue folder 27. The content is arbitrary and contains no private information.
Attempt to send only that file. Record what happens before retrying: the receiver is missing, a request appears but is not accepted, progress stalls, or the app says complete. A tiny file removes the uncertainty of a large transfer taking time while you investigate discovery.
| Failure stage | Observable symptom | Next check |
|---|---|---|
| Compatibility | App will not install or open | Check architecture, OS version, publisher and region. |
| Discovery | Receiver does not appear | Check receiver visibility, Bluetooth, proximity and network. |
| Acceptance | Receiver appears; transfer waits | Look at the receiving screen and confirm the intended device. |
| Transfer | Accepted request stalls | Try the tiny file and an allowed network without device isolation. |
| Receipt | App reports success; file seems missing | Open the actual destination folder and verify the file. |
If the Windows PC does not appear
Check the PC’s receiving visibility and the Google Account on each device. Run the Windows app normally, not as administrator. Check Bluetooth and the same-network connection, then move the devices close together. These requirements are documented in the official Windows help.
Do the checks in order and retry once after each change. For example, if the PC becomes visible after correcting the receiving account, you have learned something specific. Reinstalling the app, rebooting the router and changing visibility simultaneously would hide which action mattered.
If Android does not appear as the receiver
Open Quick Share’s receive flow on the phone and keep the device unlocked while testing. Google’s Android sending and receiving instructions describe temporary receiving visibility and how to select the destination. If you use an option visible to everyone nearby, return to your preferred restricted setting afterward.
On a desk with several phones, a familiar device name can still be ambiguous. Confirm the receiving screen and any matching verification code instead of sending personal files to the first similar name in the list. Use the harmless test file until the pairing of sender and receiver is clear.
If the transfer is accepted but stalls
Check whether the devices are on a guest Wi-Fi network, workplace network or another connection that isolates clients. Being able to browse the web on both devices does not prove they can communicate with each other locally. If permitted, repeat the small-file test on a trusted home network or an allowed hotspot.
If the PC uses Ethernet while the phone uses Wi-Fi, confirm that both paths belong to the same local network rather than separate guest and private segments. Our Ethernet and Wi-Fi guide explains why having two connections does not automatically combine or bridge them.
Do not disable the entire firewall as a routine fix. On a managed PC, give the administrator the exact app, network and failure stage. On a personal PC, inspect relevant app permissions and change only settings you understand, keeping a note of the original value. If the test still fails, a USB transfer may be the more useful next step for a file you need immediately.
If the app says complete but the file is missing
Google’s Windows help identifies the usual received-file location as Downloads → Quick Share. Open the destination through the app if available, check the filename and open the file itself. Search for the unique filename only if the expected folder does not contain it.
For the text example, confirm the unique line is intact. For a photo, open the transferred image at full size. For a video, play beyond the first frame. This checks receipt more meaningfully than seeing a progress bar reach its end.
Keep the original until you finish that check. If the transfer is part of freeing phone space, read our Google Photos storage guide before deleting anything: a cloud-synchronized deletion and removal of a local copy can have different consequences.
Keep a useful failure report
If you need more help, record the Windows architecture and version, Android version, app publisher and version, network type, file size, failure stage and exact error. Leave account addresses and personal filenames out of a public report. “Receiver missing on guest Wi-Fi; tiny file works on home Wi-Fi” gives a helper a far better starting point than “Quick Share is broken.”