Quick Share Not Working Between Android & Windows? 7 Verified Wi-Fi Direct, mDNS Port & Bluetooth Handshake Fixes (2026)

Verdict: When Quick Share fails to transfer files between an Android smartphone and a Windows PC—stalling on “Searching for nearby devices”, dropping connections halfway through transfer, or throwing “Transfer declined”—the issue is almost never faulty Wi-Fi hardware. Quick Share relies on a dual-protocol handshake: Bluetooth Low Energy (BLE) for initial device discovery and local Wi-Fi Direct (or local WLAN TCP sockets) for the actual high-speed file payload. The breakdown is typically caused by Windows Defender Firewall blocking mDNS (UDP port 5353), disabled Wi-Fi Direct Virtual Adapters, network profile mismatches (Public vs. Private), or out-of-sync Google Account identity tokens. Enabling Windows Wi-Fi Direct, whitelisting Quick Share in firewall rules, and setting device visibility to “Everyone” permanently resolves the failure.

Google and Samsung officially unified their peer-to-peer file transfer protocols into a single consolidated client: Quick Share. For Windows users, the official Quick Share for Windows application (which superseded the legacy Nearby Share for Windows desktop client) offers a native peer-to-peer sharing experience similar to Apple’s wireless workflow (compare our guide on AirDrop device discovery troubleshooting). When wireless transfers fail, users often fall back to cables, but troubleshooting USB MTP file transfers to PC presents its own driver hurdles.

However, because the handshake spans two completely different operating systems and relies on dynamic hardware negotiation between Intel/Qualcomm Wi-Fi cards and mobile modems, users frequently encounter silent transfer failures. Here is the verified technical troubleshooting sequence to get Quick Share functioning reliably between Android and Windows.

Quick Share Diagnostic & Failure Mode Matrix

Identify your exact Quick Share failure symptom below to pinpoint the targeted protocol fix:

Fix 1: Switch Visibility to “Everyone” and Sync Bluetooth Discovery

By default, Quick Share sets visibility to “Contacts only” or “Your devices”. This relies on your Google Account’s cloud contact list to verify identity. If your Windows PC is logged into a secondary Google Account, or if contact sync is paused, the two devices cannot cryptographically verify each other over Bluetooth.

On Windows PC:

1. Launch the Quick Share desktop app.
2. Click the Who can share with you drop-down menu in the left panel.
3. Change it from Contacts only to Everyone.
4. Ensure Keep everyone mode on all the time is checked while troubleshooting.

On Android Smartphone:

1. Swipe down the notification shade and tap the Quick Share quick tile (or go to Settings > Connected devices > Quick Share).
2. Set Who can share with you to Everyone (or Everyone for 10 minutes).
3. Keep your smartphone screen awake and illuminated while initiating the transfer.

Fix 2: Set Windows Network to Private and Configure Firewall Rules

When connecting to your home Wi-Fi network, Windows often defaults to a “Public Network” profile for security. In Public mode, Windows blocks all unsolicited local network discovery requests, silently dropping Quick Share’s mDNS (Multicast DNS) broadcast packets on UDP port 5353 and peer-to-peer data sockets on TCP ports 8080 through 8085.

Step A: Change Network Profile to Private

1. Open Windows Settings (Win + I) > Network & internet > Wi-Fi.
2. Click on your active connected Wi-Fi network name.
3. Under Network profile type, select Private network (this tells Windows to allow local network file discovery).

Step B: Whitelist Quick Share in Windows Defender Firewall

1. Press Win + R, type control firewall.cpl, and press Enter.
2. In the left sidebar, click Allow an app or feature through Windows Defender Firewall.
3. Click the Change settings button at the top (requires administrator rights).
4. Scroll down the list and locate Quick Share (and nearby_share.exe).
5. Ensure both the Private and Public checkboxes next to Quick Share are checked.
6. Click OK and restart the Quick Share desktop application.

Fix 3: Enable the Microsoft Wi-Fi Direct Virtual Adapter

Unlike standard file sharing over a local router, Quick Share establishes a direct, high-speed point-to-point Wi-Fi Direct connection between your phone and your computer. This bypasses your router entirely, transferring files at rates up to 50–80 MB/s.

To do this, Windows uses a hidden virtual hardware driver called the Microsoft Wi-Fi Direct Virtual Adapter. If this adapter was disabled by a power-saving profile or an aggressive VPN utility, Quick Share will fail to establish a direct link, either failing immediately or dropping back to ultra-slow Bluetooth transfer speeds (which crawl at 50 KB/s).

How to verify and re-enable Wi-Fi Direct:

1. Right-click the Windows Start menu button and select Device Manager.
2. Click View in the top menu and select Show hidden devices.
3. Expand the Network adapters category.
4. Look for entries named Microsoft Wi-Fi Direct Virtual Adapter (often numbered #1 and #2).
5. If you see a downward arrow on either icon, right-click and select Enable device.
6. If it is already enabled, right-click your primary wireless card (e.g., Intel Wi-Fi 6E AX211 or Qualcomm FastConnect), select Update driver, and choose “Search automatically for drivers”.

Fix 4: Re-Authenticate Google Account Tokens in Quick Share for Windows

If you recently changed your Google Account password, enabled 2-Step Verification, or updated Google Play Services on your smartphone, the cryptographic session tokens stored in the Windows Quick Share app will fail silently. The app displays your avatar as logged in, but outgoing mutual authentication requests fail validation.

1. Open Quick Share on your Windows PC.
2. Click your Profile Avatar in the top right corner.
3. Click Sign out.
4. Restart the Quick Share application.
5. Click Sign in with Google and authenticate through your default browser window.
6. Verify that both your smartphone and your PC display the exact same Google Account address.

Fix 5: Update Quick Share to Version 1.0.2000+ (ARM64 & Multi-Band Fix)

Early iterations of the unified Quick Share for Windows client contained documented bugs where transfers failed if the PC was connected to a 5 GHz Wi-Fi channel while the smartphone was on a 2.4 GHz channel. Furthermore, users running modern Qualcomm Snapdragon X Elite and Snapdragon X Plus ARM-based Copilot+ PCs experienced driver crashes with early x86-emulated installers.

Google and Samsung updated the client with unified binaries providing native ARM64 support and automated cross-band channel negotiation.

• Open Quick Share on Windows > click the Gear icon (Settings) in the top right.
• Scroll down to the About Quick Share section.
• Check your version number. If it is below 1.0.2000.0, download the latest installer directly from the official Android Quick Share portal or the Microsoft Store.
• Restart your PC after the update to register updated network filter drivers.

Fix 6: Check for Interfering VPNs, Proxies, and Virtual Adapters

Third-party VPN applications (such as NordVPN, ExpressVPN, Cloudflare WARP, or Tailscale) inject virtual network adapters (TUN/TAP adapters) that route all incoming and outgoing IP packets through an encrypted tunnel. Because Quick Share attempts to communicate over local subnet broadcast addresses (255.255.255.255 and 224.0.0.251), a VPN with “Local network sharing” disabled will block the initial handshake.

• Temporarily disconnect all active VPNs on both the PC and your smartphone.
• In your PC’s VPN app settings, enable Allow local network sharing / Invisibility on LAN if you must keep the VPN active.
• Disable third-party virtual network switches (such as VirtualBox Host-Only Ethernet Adapter or VMware Network Adapter) in Windows Network Connections (ncpa.cpl), as Quick Share can mistakenly bind its socket to an unroutable virtual adapter.

Fix 7: Clear Quick Share Cache and Reset Play Services (Android)

If the failure originates on your phone (the phone freezes upon tapping the PC’s icon), the cached Quick Share runtime state in Google Play Services may be corrupted.

1. On Android, go to Settings > Apps > See all apps.
2. Tap the three dots > Show system apps.
3. Scroll down and select Quick Share (on Samsung, inspect both Quick Share and Quick Share Connectivity).
4. Tap Storage & cache > Clear cache, then tap Clear storage.
5. Return to the app list, locate Google Play services, tap Storage & cache > Clear cache.
6. Reboot your phone. Quick Share will reinitialize its BLE beacon state cleanly.