New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 April 2018 Update removes Npcap Loopback Adapter #80
Comments
Just remembered: I did not restart the I will be checking the upgrade logs for messages related to the Npcap Loopback Adapter to see why it was removed. |
Update: this affects all Microsoft KM-TEST Loopback Adapter devices installed on the system, and happens even if Npcap is not installed. It is not exclusive to Npcap. |
Related issues: nmap/nmap#998, nmap/nmap#1216, nmap/nmap#1095
This still happens, but now it only affects "Legacy loopback support" installations, since loopback capture and injection is now handled without the Npcap Loopback Adapter. |
Legacy loopback support with the Npcap Loopback Adapter is now strongly deprecated. We do not intend to address the problem of Windows feature updates removing the adapter. Recommended fix is to reinstall without this feature. |
No clues yet on why or how, but it's gone. Npcap 0.99-r5
Running
NPFInstall.exe -ul
thenNPFInstall.exe -il
restores the adapter, but Nmap isn't able to use it, giving thednet: Failed to open device lo0
error message.Reinstalling Npcap creates a new, working Npcap Loopback Adapter.
The text was updated successfully, but these errors were encountered: