Skip to content
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

Fix network disruption during Npcap install on 802.1q authenticated networks #1658

fyodor opened this issue Jul 9, 2019 · 1 comment


None yet
2 participants
Copy link

commented Jul 9, 2019

We have received reports from 2 users of 802.1q authenticated networks that their Wifi connection was disrupted during Npcap install until they re-authenticated to rejoin the network or just rebooted their system. We don't yet know if all 802.1q authenticated networks are similarly disrupted or if it was something specific to these particular networks/systems.

This issue is partially created as a call out for people to report if they are experiencing this issue or not. That will help us decide how to prioritize the issue and figure out what the cases might have in common besides 802.1q. Please let us know what version of Windows you are running too.

Obviously the best fix would be to prevent the network disruption in the first place, but that may be difficult if it is a bug/characteristic of how Windows handles the loading of WFP drivers. In the meantime, we are looking at creating a "/start_driver_now =no" install option that prevents the Npcap driver from loading until the next reboot. That means Npcap functionality won't be available until then either, but it may be better than risking even temporary network disruption on a running system.

@fyodor fyodor added bug Npcap labels Jul 9, 2019


This comment has been minimized.

Copy link

commented Jul 10, 2019

+1 to the addition of "/start_driver_now=no"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.