Revision history [back]

Unsurprisingly having the npcap driver in state stopped will prevent the locating of capture interfaces. We'll need to check if the service is configured to start, if not make it so and then start it.

Check the service config:

sc qc npcap

On my system I get:

[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: npcap
        TYPE               : 1  KERNEL_DRIVER
        START_TYPE         : 1   SYSTEM_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : \SystemRoot\system32\DRIVERS\npcap.sys
        LOAD_ORDER_GROUP   : NDIS
        TAG                : 24
        DISPLAY_NAME       : Npcap Packet Driver (NPCAP)
        DEPENDENCIES       :
        SERVICE_START_NAME :

If the START_TYPE isn't SYSTEM_START, then make it so. This will need an Administrative (elevated) CMD prompt (note the odd spacing is required):

sc config npcap start= system

and now start the service, again an elevated CMD prompt is required:

sc start npcap

As to how you got into this state, there is an npcap installer option to NOT start npcap at system startup, which you may have chosen. Another possible way to fix this is to reinstall Wireshark and\or npcap and make sure it's permitted to start at system startup.