locked
10041 and WinPcap 4.1.3 (anyone using this?) RRS feed

  • Question

  • I've found that while the driver appears to be loading properly, it doesn't actually do anything anymore (it was working as of 9926). Wireshark, for example, is missing LAN interfaces.

    I've tried reinstalling WinPcap to no effect.

    Is it working for anyone?

    Friday, March 20, 2015 3:17 AM

All replies

  • Hi,

    I tested the tool wireshark, seems issue as you described in preview build 10041, even I tried to install the program in compatibility mode, it still doesn't work, not show Interface lists.

    I'm not quite familiar with WinPcap, but you can also test it in compatibility mode, please see this similiar guide, right click the installer, choose a right compatibility mode.

    http://blogs.msdn.com/b/kaushal/archive/2012/08/08/installing-wireshark-winpcap-on-windows-8-rtm.aspx 

    I looked for the WinPcap in its offical website, and there's no version released for Windows 8\later. I recommend you contact the vender for the product for they are thirty party tools and the vender is more familiar with the products.

     


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, March 23, 2015 3:03 AM
    Moderator
  • Yes, I'll probably contact them next, though it looks like a tiny operation so I'm not counting on an update any time soon (odd that it was working just fine up until now). Thanks for confirming (btw, if you didn't have the WinPcap driver installed at the time of running WinPcap, it's normal for Wireshark not to show interfaces).
    Monday, March 23, 2015 5:09 AM
  • http://blogs.msdn.com/b/kaushal/archive/2012/08/08/installing-wireshark-winpcap-on-windows-8-rtm.aspx 

    I looked for the WinPcap in its offical website, and there's no version released for Windows 8\later. I recommend you contact the vender for the product for they are thirty party tools and the vender is more familiar with the products.

    WinPcap was working fine in Windows 8.x and in previous Builds of Windows 10, so is not a compatibility issue caused by WinPcap.

    it is clearly a bug caused by Microsoft, due somebody changed something in the network engine that broken the compatibility in Build 10041.

    Monday, March 23, 2015 2:15 PM
  • Melerix

    Instead of waiting for wireshark to become compatible you may want to check out MS message analyzer.  It does as much as (actually more) than wireshark and works in 10041

    http://www.microsoft.com/en-us/download/details.aspx?id=44226


    Wanikiya and Dyami--Team Zigzag

    Monday, March 23, 2015 2:50 PM
    Moderator
  • WinPcap was working fine in Windows 8.x and in previous Builds of Windows 10, so is not a compatibility issue caused by WinPcap.

    it is clearly a bug caused by Microsoft, due somebody changed something in the network engine that broken the compatibility in Build 10041.

    Yes, it was, but it's impossible to know whether it's a bug in Win10 or merely a change of design in it that WinPcap must compensate for to remain compatible. After all, much is in transition.
    Monday, March 23, 2015 3:02 PM
  • Hi,

    Currently, as Zigzag mentioned, we can use other tools as alternative solution, for wireshark and WinPcap, I recommend reporting this issue to the vender of the product, meanwhile please submit a feedback via the built-in Windows Feedback App to our develop team.

    Thanks for your support.

    Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, March 24, 2015 7:02 AM
    Moderator
  • Yes, though note that WinPcap is used by other programs too--it's not just tied to Wireshark. No doubt there are alternatives to those too, but it's worth mentioning.
    Tuesday, March 24, 2015 7:10 AM
  • This is magically back working again in 10074.
    Thursday, April 30, 2015 9:34 PM