Wi-Fi Direct Pairing Fails: Devices See Each Other But Can't Connect

You're trying to share a file or cast your screen between two Android phones, or maybe between a Windows laptop and a printer. Both devices see each other in the Wi-Fi Direct list. You tap to connect, and then — nothing. It either spins forever and times out, or shows an error like "Connection failed" or "Pairing unsuccessful". I've seen this exact mess on Android 11 through 14, Windows 10 20H2+, and various Wi-Fi Direct printers (HP, Brother, Canon). The trigger is almost always a stale network profile or a core service that's not actually running.

Why This Happens

Here's the plain truth: Wi-Fi Direct creates a temporary peer-to-peer network between two devices. It doesn't use your home Wi-Fi. For it to work, both devices need to agree on a Group Owner — that's the device that acts like a mini router. When pairing fails, it's usually because:

• The Wi-Fi Direct service isn't running. On Windows, it's the Wi-Fi Direct Services Connection Manager Service. On Android, it's baked into the Wi-Fi stack, but a misconfigured IP address or DNS can break it.
• Driver is old or corrupted. Realtek and Intel Wi-Fi adapters are notorious for this. Windows can install a generic driver that doesn't support Wi-Fi Direct properly.
• Firewall blocks the handshake. Windows Defender Firewall or a third-party firewall (like Norton, McAfee, or even ESET) can block the UDP ports used for Wi-Fi Direct discovery (port 5353 for mDNS and port 1024-65535 for data).
• Both devices try to be Group Owner. This happens more than you'd think. Some devices are aggressive about taking control, and if both insist, they never negotiate a connection.

Skip the basic "restart both devices" advice — you've already tried that. Here's the real fix.

Step-by-Step Fix

1. Check and Restart the Wi-Fi Direct Service (Windows Only)

Open services.msc — hit Win+R, type services.msc, and press Enter. Find Wi-Fi Direct Services Connection Manager Service. Right-click it, select Properties. Make sure the Startup type is Manual (not Disabled). Click Stop if it's running, then Start again. This clears any stuck state. Do the same for Function Discovery Provider Host and Function Discovery Resource Publication — set them to Manual and restart them.

2. Update the Wi-Fi Adapter Driver (Do This On Every OS)

On Windows: Open Device Manager. Expand Network adapters. Find your Wi-Fi adapter (Intel, Realtek, or Broadcom). Right-click, select Update driver → Browse my computer for drivers → Let me pick from a list of available drivers on my computer. If there's a newer driver listed, select it. If not, download the latest driver from the manufacturer's site (Intel Driver & Support Assistant works well for Intel). Don't use Windows Update's driver — it's often stripped down and won't support Wi-Fi Direct correctly.

On Android: You can't update the Wi-Fi driver directly, but a full network settings reset clears stale Wi-Fi Direct profiles. Go to Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth. This will wipe saved Wi-Fi networks and Bluetooth pairings, so have your Wi-Fi password handy.

3. Temporarily Disable Windows Defender Firewall

This is the fastest way to rule out a firewall block. Open Windows Security → Firewall & network protection → click the active network profile (Domain/Private/Public) → toggle Microsoft Defender Firewall to Off. Try the Wi-Fi Direct connection again. If it works, you need to add a rule for Wi-Fi Direct. Re-enable the firewall, then create an inbound rule allowing UDP ports 5353 and 1024-65535 for Wi-Fi Direct Services Connection Manager Service (search for WFDConMgrSvc.exe). This is a pain, but it's the proper fix.

4. Force One Device to Be the Group Owner

On Android, you can't directly set this, but you can influence it by connecting the device you want as Group Owner to a known Wi-Fi network first. On Windows, you can try using a third-party tool like Wi-Fi Direct Manager from the Microsoft Store, but honestly, they rarely help. The better trick: connect both devices to the same regular Wi-Fi network (your home router). Sometimes this helps them negotiate the Group Owner role correctly.

What to Check if It Still Fails

If you're still stuck after the steps above, look at these:

• Check for IP address conflicts. On Windows, open Command Prompt and run ipconfig /all. Look for the Wi-Fi Direct adapter — it should have an IP in the 192.168.173.x range (typical for Wi-Fi Direct). If it's something else or shows 0.0.0.0, run ipconfig /release then ipconfig /renew on that adapter.
• Third-party antivirus can block Wi-Fi Direct. Temporarily disable Norton, McAfee, or Kaspersky completely. Not just the firewall — the whole suite. Test the connection. If it works, check the app's network protection settings for a Wi-Fi Direct exclusion.
• Hardware limitation. Some older Wi-Fi adapters (especially USB dongles) don't support Wi-Fi Direct at all. Check the specs of your adapter — if it says "SoftAP" or "Virtual Wi-Fi" but not "Wi-Fi Direct", it won't work. You'll need a different adapter.

Bottom line: 90% of Wi-Fi Direct failures are caused by a stopped service, a bad driver, or a firewall rule. Don't waste time on app-level fixes — go straight for the system settings.