tag:blogger.com,1999:blog-1740550564148120237.post1827653153539696872..comments2023-09-23T07:51:06.345-07:00Comments on NetScanTools® Inside Out: Updated: WinPcap and Wireshark problems on Windows 10 Tech Preview 10041Unknownnoreply@blogger.comBlogger10125tag:blogger.com,1999:blog-1740550564148120237.post-19839163103034663142015-09-04T09:58:11.073-07:002015-09-04T09:58:11.073-07:00See: https://wiki.wireshark.org/CaptureSetup/Loopb...See: https://wiki.wireshark.org/CaptureSetup/Loopback and https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-1.00.exeAnonymoushttps://www.blogger.com/profile/15079063596491159572noreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-55393533347085406212015-05-11T18:04:57.880-07:002015-05-11T18:04:57.880-07:00try winpcap deriver for ndis 6 by Nmap, I tried it...try winpcap deriver for ndis 6 by Nmap, I tried it on build 10041 and it's wirking<br /><br />https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/installer/winpcap-nmap-4.1.3-NDIS6-1.2.0.exeDAHMANIhttps://www.blogger.com/profile/16192982838455800789noreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-47608384678180244892015-04-24T04:29:41.515-07:002015-04-24T04:29:41.515-07:00I just tried build 10061 and in this build it seem...I just tried build 10061 and in this build it seems to work again.Tomnoreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-55501293203904657012015-04-21T21:06:43.717-07:002015-04-21T21:06:43.717-07:00Same problem build 10049.
By the way for the last ...Same problem build 10049.<br />By the way for the last guy who has commented, build 10051 is just for phones so I don't what are you taliking about.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-11763752609740010022015-04-13T00:53:09.628-07:002015-04-13T00:53:09.628-07:00The same situation is with build 10051The same situation is with build 10051Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-61889957853262043212015-04-03T14:31:44.172-07:002015-04-03T14:31:44.172-07:00I also tried 10049 and does not work. Hope there ...I also tried 10049 and does not work. Hope there is a fix soon.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-73569432467460822762015-03-31T14:05:37.328-07:002015-03-31T14:05:37.328-07:00Just tried this on 10049. Does not work. It does f...Just tried this on 10049. Does not work. It does find my internal bluetooth interface, can't remember if this was the case on previous not working builds. Anyway, still doesn't work.Anonymoushttps://www.blogger.com/profile/04148538846897944528noreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-7092377462055406472015-03-31T13:20:17.153-07:002015-03-31T13:20:17.153-07:00I'm not on the 'fastest' release track...I'm not on the 'fastest' release track, so I don't have 10049 yet. Hopefully today, but my past experience is that once an internal networking change is made during beta, it does not reverse without lots of complaints (raw sockets for example). Bring this up at Sharkfest if you are going!Kirk Thomashttps://www.blogger.com/profile/01196946760222412036noreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-20988548819514391382015-03-31T13:06:56.695-07:002015-03-31T13:06:56.695-07:00I notice that Microsoft released build 10049 yeste...I notice that Microsoft released build 10049 yesterday. Does it still have the problem?<br /><br />http://blogs.windows.com/bloggingwindows/2015/03/30/windows-10-technical-preview-build-10049-now-available/Stan Slonkoskyhttps://www.blogger.com/profile/13453758065449182939noreply@blogger.comtag:blogger.com,1999:blog-1740550564148120237.post-29543500498980764292015-03-26T20:31:34.148-07:002015-03-26T20:31:34.148-07:00i can confirm wireshark has stopped working since ...i can confirm wireshark has stopped working since new build 10041. previous build worked just fineAnonymoushttps://www.blogger.com/profile/15109680296906990992noreply@blogger.com