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
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…
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.
lets try again with one picture…
