WiFi Direct in Windows 10 says “UnsupportedHardware”, although it should be supported

Question

I will try to do it shortly. I worked on Windows 10 (10130) on Microsoft Direct Direct Services available on GitHub , C # one in Visual Studio 2015 RC. Now, at their construction conference, they said you can run a command in the CMD to find out if your WiFi adapter is compatible with WiFi Direct

netsh wlan show wirelesscap 

Which gives me a great YES, your wireless adapter is compatible.

 Wi-Fi Direct Device : Supported Wi-Fi Direct GO : Supported Wi-Fi Direct Client : Supported 

But when I run the specified sample, everything goes OK until WiFiDirectServiceWrapper.OnAdvertisementStatusChanged (...) is launched, almost immediately after creating the advertiser. When I run the sample with the profiler, I get the following:

 private void OnAdvertisementStatusChanged(WiFiDrectServiceAdvertiser sender, object args) 

-

 sender | {Windows.Devices.WiFiDirect.Services.WiFiDirectServiceAdvertiser} AdvertisementStatus: Aborted AutoAcceptSession: true CustomServiceStatusCode: 0 DeferredSessionInfo: null PreferGroupOwnerMode: true PreferredConfigurationMethods : _native, can't see_ ServiceError: UnsupportedHardware ServiceInfo: null ServiceName: "myservice" ServiceNamePrefixes: {System.__comObject} ServiceStatus: Available 

I really don't know how I should loosen this, since I cannot find where this event is raised (the only links to this method are

 this.advertiser.AdversitementStatusChanged += OnAdvertisementStatusChanged this.advertiser.AdversitementStatusChanged -= OnAdvertisementStatusChanged 

^ the), and I do not see the implementation of WifiDirectServiceAdvertiser.

My WiFi card is Qualcomm Atheros AR9485 and I use the latest drivers available through Windows Update. In device manager, I get two virtual virtual Wi-Fi adapters:

 Microsoft Wi-Fi Direct Virtual Adapter Microsoft Wi-Fi Direct Virtual Adapter #2 

The second is disabled sometimes (the UnsupportedHardware event is the same, enabled or disabled). For all of them, I turned off the option "Allow the computer to turn off this device to save energy."

I tried to compile the code for x86 and x64, but I get the same result at the same point. I tried two more universal wireless portable devices (these USB USB adapters) that Windows say yes, they are also compatible with luck.

I know that Windows 10 is not final, but any help is appreciated.

Answer 1

It seems that WiFiDirect is not the only thing you should take a look at if the thing you want to do is advertise a service (which is actually “new in Windows 10” relative to Direct).

The command you have to execute is exactly the same as before:

netsh wlan show wirelesscap

but if you want to advertise the service, then the following options:

 P2P Device Discovery : Supported P2P Service Name Discovery : Supported P2P Service Info Discovery : Supported P2P Background Discovery : Supported 

What WiFiDirect does on Windows with 8 and 8.1 advertises the entire computer, but with 10, WiFiDirectServices advertises one or more services running simultaneously on your computer.

Let's say you are a com.boardgames developer. If you want to hold a board games contest somewhere without a hard AP, it can be a prefix of the name of all your services, so each client connects only to the one they need: for example, com.boardgames.solitaire or com.boardgames.chess instead of connecting to your car.

Unfortunately, none of the computers and Wi-Fi antennas I tried are compatible with P2P discoveries.