# inSSIDer packet capture fails

**URL:** <https://community.oscium.com/t/inssider-packet-capture-fails/1064>\
**Category:** inSSIDer\
**Created:** [June 25, 2020, 11:25pm UTC](https://community.oscium.com/t/inssider-packet-capture-fails/1064 "2020-06-25T23:25:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dlritter](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@dlritter](https://community.oscium.com/u/dlritter)\
**Post date:** [June 25, 2020, 11:25pm UTC](https://community.oscium.com/t/inssider-packet-capture-fails/1064/1 "2020-06-25T23:25:50Z")

</div>

TP-Link T9UH installed, app opens reporting :  
200NGW [scan], TP-Link Archer T9UH v2 [packets] wiSpy DBx2…  
after a moment it tweaks the driver and the T9UH is removed.  
functions that require the packet device open with the admonition to purchase a compatible device…  
Win10 ver 2004 build 19041.329

---

<div class="post-metadata">

**Author:** ![dlritter](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@dlritter](https://community.oscium.com/u/dlritter)\
**Post date:** [June 25, 2020, 11:39pm UTC](https://community.oscium.com/t/inssider-packet-capture-fails/1064/2 "2020-06-25T23:39:25Z")

</div>

now when I run inSSIDer on win10enterprise ver 1803 I can see how the program is suposed to work, so MS tweaked the os a bit again…

---

<div class="post-metadata">

**Author:** ![brian](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.oscium.com/brian/32/76_2.png) [@brian](https://community.oscium.com/u/brian)\
**Post date:** [June 26, 2020, 2:47pm UTC](https://community.oscium.com/t/inssider-packet-capture-fails/1064/3 "2020-06-26T14:47:07Z")

</div>

Hi @dlritter! Welcome to the MetaGeek community. I’m sorry your first post was related to a problem with packet capture in inSSIDer. It sounds like it is working since the most recent Windows update, though, so that’s great news. I think we have a sample of that adapter at our office, I’ll grab it next time I am there (mostly working from home right now) and see if I can replicate the issue you ran into.

---

<div class="post-metadata">

**Author:** ![dlritter](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@dlritter](https://community.oscium.com/u/dlritter)\
**Post date:** [June 26, 2020, 11:10pm UTC](https://community.oscium.com/t/inssider-packet-capture-fails/1064/4 "2020-06-26T23:10:50Z")

</div>

lets try again with one picture…

---

<div class="post-metadata">

**Author:** ![dlritter](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@dlritter](https://community.oscium.com/u/dlritter)\
**Post date:** [June 26, 2020, 11:13pm UTC](https://community.oscium.com/t/inssider-packet-capture-fails/1064/5 "2020-06-26T23:13:44Z")

</div>

and the 2nd picture..

 ![Annotation 2020-06-25 161214.png](https://canada1.discourse-cdn.com/flex047/uploads/metageek1/original/1X/58fb99b8f82770ee0cebd4d894c7e8ba957b151b.png)
