Now they've switched it strictly to NDIS 6, and WinPCap is not programmed for NDIS 6. This was true up until this most recent build. I researched a bit and it appears that up until now, Microsoft had backwards compatibility for NDIS 5 built into Windows. If you allow the computer to install updates, then you should experience the same thing that I am. It's only the latest 10049 Build that breaks things. I ran it as administrator (this is extremely important) and the network adapters are shown correctly. I just downloaded the technical preview (build 9926 圆4) and kai (7.4.28 ) seems to work perfectly. Last edited by Flickstiq on Thu 8:06 pm edited 2 times in total

Can anyone think of any workarounds for this issue? I'd love to get it working again. Now that Kai only uses WinPCap, it seems like it may not be possible to use Kai with Windows 10. This compatibility problem with the latest build of Windows 10 is documented in other Apps that utilize WinPCap. Unfortunately, the WinPCap team hasn't updated or developed the product in over a year. When you open Xlink, you'll get an error that there are no interfaces detected (this is a WinPCap error). Because of this change, WinPCap no longer functions the way that it should. Microsoft has changed the way that Windows handles drivers in Build 10049. I've run into an issue that I want to bring to everyone's attention. 'No Interfaces Detected' launching Kai in Win10 uk :: View topic - 'No Interfaces Detected' launching Kai in Win10 FAQ

Wireshark no interfaces found windows 0