"No Interfaces Detected" launching Kai in Win10

Kai Beginner Joined: 07 Dec 2014 Posts: 12

Hi everyone!

I've run into an issue that I want to bring to everyone's attention. Microsoft has changed the way that Windows handles drivers in Build 10049. Because of this change, WinPCap no longer functions the way that it should. When you open Xlink, you'll get an error that there are no interfaces detected (this is a WinPCap error).

Unfortunately, the WinPCap team hasn't updated or developed the product in over a year. This compatibility problem with the latest build of Windows 10 is documented in other Apps that utilize WinPCap.

Now that Kai only uses WinPCap, it seems like it may not be possible to use Kai with Windows 10. Can anyone think of any workarounds for this issue? I'd love to get it working again.

Team XLink Developer Joined: 28 Nov 2007 Posts: 2338

Hi there!

I just downloaded the technical preview (build 9926 x64) and kai (7.4.28 ) seems to work perfectly. I ran it as administrator (this is extremely important) and the network adapters are shown correctly. I'm using winpcap 4.1.3.

Kai Beginner Joined: 07 Dec 2014 Posts: 12

Yep, that was true for me as well. It's only the latest 10049 Build that breaks things. The previous builds worked fine. If you allow the computer to install updates, then you should experience the same thing that I am.

I researched a bit and it appears that up until now, Microsoft had backwards compatibility for NDIS 5 built into Windows. This was true up until this most recent build. Now they've switched it strictly to NDIS 6, and WinPCap is not programmed for NDIS 6. That's the core issue.

I'd also guess that if they are introducing exclusivity for NDIS 6 in this build, then they are likely not going to reintroduce the backwards compatibility for NDIS 5. We can hope that they do, but I think that we have to assume that we need another way for Xlink to work with Windows 10.

Team XLink Developer Joined: 28 Nov 2007 Posts: 2338

Ah I see. I'll see if I can get mine to completely update. In the meantime can you try PSSDK mode? Its in the main config page.

Kai Beginner Joined: 07 Dec 2014 Posts: 12

I can't get into the Config GUI. When I try to launch the Config, it tells me immediately that there are no interfaces detected and it closes. I tried adding it manually to Xlink Config and that did nothing. I installed 7.1.3.7, and when I open it I get an error that it could not initialize PSSDK Manager. I did go in and set it to Adminstrator and I also tried different compatibility modes (XP SP3, Vista, etc). Each time that I set a Compatibility Mode and try to Launch, I get an error and it reboots my computer. I'm not looking at the blue screen right now, but it says something about opening a page where a page is not allowed.

If you have a different version that you'd like me to try, or a different method to use with the latest version, let me know.

Posted: Thu Apr 02, 2015 4:06 am

I'll have a look into this tomorrow and see what I can find.

Team XLink Developer Joined: 28 Nov 2007 Posts: 2338

Oooooh I forgot that we completely removed PSSDK a few versions ago, but forgot to update the UI, oops.

BTW my install is not updating to 10049 so I should be able to start looking for a fix.

I also found this: http://netscantools.blogspot.ca/2015/03/winpcap-and-wireshark-problems-on.html

Posted: Thu Apr 02, 2015 4:19 am

Try the following version of Winpcap, it apparently supports NDIS 6.

https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/installer/winpcap-nmap-4.1.3-NDIS6-1.2.0.exe

Kai Beginner Joined: 07 Dec 2014 Posts: 12

SgtLegend wrote:

Try the following version of Winpcap, it apparently supports NDIS 6.

https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/installer/winpcap-nmap-4.1.3-NDIS6-1.2.0.exe

That seems to have done the trick! I'm really glad to see that there is a version of WinPCap that works with NDIS 6. Thank you!

EDIT: This might be a good thing to add to the FAQ or something along those lines. As we get closer to the summer, many people will be upgrading to Windows 10 and will potentially have this issue. Thank you again! I'm very happy to be able to play again.

Posted: Thu Apr 02, 2015 7:31 am

Cool, we will still need to do further testing to ensure no P2P functionality is broken within the engine.

Let us know if you spot anything weird.

Kai Beginner Joined: 07 Dec 2014 Posts: 12

SgtLegend wrote:

Cool, we will still need to do further testing to ensure no P2P functionality is broken within the engine.

Let us know if you spot anything weird.

Will do