Ask Your Question

Unable to capture packets on Surface Mobile Broadband adaptor

asked 2021-04-13 16:24:46 +0000

Joel gravatar image

updated 2021-04-13 16:33:28 +0000

grahamb gravatar image

Some info:

Driver version:
Windows version: Windows 10 Pro 20H2 19024.906
Wireshark version: 3.4.4
Npcap version: 1.10
Device: Microsoft Surface Pro 5 with LTE

The Npcap Packet Driver appears correctly. Error message: "The capture session could not be initiated on interface '<redacted>' (failed to set hardware filter to non-promiscuous mode)." Please check to make sure you have sufficient permissions, and that you have the proper interface or pipe specified."

  • Issue does not affect packet capture over WiFi
  • Issue occurs for both Administrators and non-Administrators.
  • Issue occurs for both promiscuous and non-promiscuous adaptor setting.
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2021-04-14 18:54:27 +0000

Guy Harris gravatar image

Try updating to Npcap 1.30 using the 1.30 installer on the Npcap Web site. Even if that doesn't fix the problem, it might improve the error message to indicate more precisely what the problem is.

If it doesn't fix the problem, report it as an Npcap issue on the Npcap issues list. Give the full details of the error message - with 1.30, there may be a colon, and an error string containing a message and a number, after "failed to set hardware filter to non-promiscuous mode", so provide all that information. Also, provide all the information you provided above.

edit flag offensive delete link more


Thanks for the quick response. I've updated and the issue persists, so I raised the issue with npcap. There's an error code (3758096571), although it doesn't resolve to a description.

Joel gravatar imageJoel ( 2021-04-15 13:44:00 +0000 )edit

Well, that's a broken driver. I infer from the "with LTE" that the device is built in to the Surface Pro; you'd think Microsoft would do some Windows Hardware Qualification Laboratory testing of the hardware in their own tablet and get that fixed.

It might be possible to work around that botch in Npcap (either in libpcap or in packet.dll).

Guy Harris gravatar imageGuy Harris ( 2021-04-15 22:35:18 +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


Asked: 2021-04-13 16:24:46 +0000

Seen: 472 times

Last updated: Apr 14 '21