This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 14.000000000000002%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
I have a question about connecting any device to Windows using WiFi Direct. In my case, the device is a Linux based device, but it shouldn't matter. I am using the built-in application in Windows, accessible from Settings -> Bluetooth & devices -> Add device -> Everything else.
What I managed to achieve is that from this application, I successfully find my device. When I click on it, it starts connecting. The WiFi Direct connection is successful, the P2P group is negotiated, and I also get an IP from Windows. The IP connection works, I confirmed it with a ping. Unfortunately, after a while (1 minute), Windows sends a "Disconnected" message and the network disconnects.
I also used a sample C# application for WiFi Direct communication: https://learn.microsoft.com/en-us/samples/microsoft/windows-universal-samples/wifidirect/. In this case, I also managed to connect, and this time everything worked as expected, no sudden disconnection.
Why did the method from "Settings -> Add device" not work fully, and why did Windows disconnect the network? Is there anything that needs to be provided to maintain the connection?
A dedicated application for connecting is a solution, but I would prefer not to need an additional application. Ideally, the built-in one in Windows should be sufficient.
