Probably due to e88b6f8 which replaced registry-mining for adapters with calls to GetAdaptersAddresses(), VMware's host-only and NAT virtual network adapters aren't showing up to Npcap. We're investigating why, but helpful information will be output of the following Powershell command: Get-NetAdapter -IncludeHidden -Name "VMware *" | select * | fl
The text was updated successfully, but these errors were encountered:
Big lead: Get-NetAdapterBinding -ComponentID INSECURE_NPCAP shows that Npcap 1.20 will bind to these adapters, but Npcap 1.30 does not. We made a small change to the INF file for npcap.sys that was intended to improve compatibility and follow microsoft guidance, but it appears this caused us to not bind to these adapters. We'll have to change that. Unfortunately, our window for being able to sign a driver for Windows 8.1 and earlier just closed yesterday, so the fix will have to wait until we can complete #237 and undergo WHQL certification for those operating systems. Windows 10 uses a different signature process for now, which will still work.