Ask Your Question

Please turn off promiscuous mode for this device

asked 2023-01-01 04:44:58 +0000

wenxu gravatar image

The capture session could not be initiated on capture device "\Device\NPF_{A9DFFDF9-4F57-49B0-B360-B5E6C9B956DF}" (failed to set hardware filter to promiscuous mode: 连到系统上的设备没有发挥作用。 (31)).

I have no problem using this software in win10, but since I upgraded to win11, it cannot be used normally, like this.

How can I solve it?

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2023-01-01 08:21:56 +0000

Guy Harris gravatar image

Please turn off promiscuous mode for this device

Sure, tell us where your computer is, and let us select Capture > Options and click the "Promisc" checkbox for that interface; that wil turn off promiscuous mode.

Or you could do that yourself, so that Wireshark doesn't try to turn pomiscuous mode on.

(The problem is probably a combination of 1) that device's driver doesn't support promiscuous mde and 2) a recent change to the Npcap driver caused it so that it no longer attempted to hide the error code that the driver returns from that from some crap code inside Windows that turns the "not supported" error that Npcap will ignore into some generic uninformative error that Npcap has no idea that it should ignore. Thanks, Microsoft!)

edit flag offensive delete link more


No, it's probably due to 1) the Windows 11 driver using the Windows NetAdapterCx framework, 2) the NetAdapterCx framework not strictly following the Network Driver Interface Specification (NDIS) rules, and 3) the Npcap driver expecting all adapter drivers to strictly follow that specification and reporting an error if they don't.

This should be fixed in Npcap 1.74, which was released today (2023-04-20). (The Npcap driver no longer reports an error for that particular violation of the specification.)

Guy Harris gravatar imageGuy Harris ( 2023-04-21 06:02:45 +0000 )edit

@GuyHarris, This absolutely helped me with this issue. I have Win11Pro 21H2, was getting the error from fresh Wireshark install. I uninstalled and tried multiple things but it didn't work. It wasn't until I saw your comment and noticed I was on npcap version 1.7 which needed to be upgraded to the new 1.74. I no longer have this issue.

Wireshark_Guru gravatar imageWireshark_Guru ( 2023-04-25 14:50:06 +0000 )edit

@GuyHarris likewise. thank you.

jafristr gravatar imagejafristr ( 2023-05-22 18:58:58 +0000 )edit

Thanks for this. I just reinstalled wireshark and it still automatically installs Npcap 1.71 with the error. So those installing might want to install it separately.

Joan gravatar imageJoan ( 2023-08-23 15:35:58 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2023-01-01 04:44:58 +0000

Seen: 48,725 times

Last updated: Aug 23 '23