Wi-Fi Inspector (17.3.2290+91) skipping connected clients

merckxist · 2017-04-01T18:55:56.000Z

On a WinXp and Win7 client, the Wi-Fi Inspector is only listing wired systems connected on my local network. It shows none of the mobile devices that are connected to the same Wi-Fi router (Netgear AC1750) as the two Windows hosts. There is a Win10 host on the same network that does show the mobile clients when I run Wi-Fi Inspector there. All hosts have the same version of Avast. All running the latest OS (respectively) versions/updates. Before this latest release of Avast, all Windows hosts were listing both wired and Wi-Fi clients in the Wi-Fi Inspector scans. Anyone else seeing this behavior with these (2290,91) free versions of Avast?

system · 2017-04-01T21:48:28.000Z

I had the same problem with 17.3.2290+91 on a Win10Home laptop and TP-Link Archer C9 router, with not a single Wi-fi attached device showing up in the scan. Due to the multiple bugs (far too many to put up with), I reverted back to 12.3.2280 (build 12.3.3154.23) and all Wi-fi devices now show up in the scan.

merckxist · 2017-04-02T19:10:19.000Z

Chris-G post:2:

I had the same problem with 17.3.2290+91 on a Win10Home laptop and TP-Link Archer C9 router, with not a single Wi-fi attached device showing up in the scan. Due to the multiple bugs (far too many to put up with), I reverted back to 12.3.2280 (build 12.3.3154.23) and all Wi-fi devices now show up in the scan.

Thanks for the observation. I tried reverting to both 12.3.2280 and 17.2.2288 on the WinXP host but still didn’t see Wi-Fi devices with either version. Maybe its an adapter setting. Earlier, with the 17.3.2290 version showing Wi-Fi clients on the WinXP host, I tried moving its adapter to the Win7 host, but that did not result in any change on Win 7. When I moved that adapter back to WinXP, that host no longer displayed the Wi-Fi clients. So at this point I think I’ll just go with 17.3.2290+91 everywhere and see if the adapter settings are consistent across hosts. My router is set to block anything but known MAC addresses, so I’m not too worried about intruding neighbors. Maybe Avast can investigate the feature for possible issues and some future update will magically find those stealthy Wi-Fi clients.

mchain · 2017-04-02T19:46:53.000Z

Not addressing issue for which only avast can resolve, but workaround maybe that you can use in the meantime: https://www.softperfect.com/products/wifiguard/
Other networking tools available on same web-board.

merckxist · 2017-04-03T03:16:30.000Z

mchain post:4:

Not addressing issue for which only avast can resolve, but workaround maybe that you can use in the meantime: https://www.softperfect.com/products/wifiguard/
Other networking tools available on same web-board.

Thank you for the suggestion. I tried wifiguard and found the same results as with Avast. And to be more precise, both are finding wired devices such as a router, other hosts (Win & Linux), a NAS appliance and wireless printers (HP & Brother). Likewise, on the Win 10 host, they both also find mobile devices, Iphone, Ipad, Android and an IoT refrigerator as well as everything discovered from the WinXP and Win7 boxes. So there’s some consistency among these tools, but not so with all OS versions from what I’ve seen so far.

FilipBraun · 2017-04-03T07:16:58.000Z

Hello,

Thank you for reporting this issue.
I’m looking into it and will post back here with some news.

Filip

FilipBraun · 2017-04-03T09:22:15.000Z

Hello merckxist,

Unfortunately I was not able to reproduce the issue on Win XP neither on Win 7.
Could you please send us log from your scan on Win 10 (where you see the devices) and then from Win 7 (where you don’t see the devices)?
We would like to try and look for the issue there.

To generate and send logs:
First enable debug logging: GUI → Settings → General → Maitenance → Enable debug logging
Then reproduce the issue (Run network scan).
Then create support package and submit it (https://www.avast.com/en-us/faq.php?article=AVKB33) and send me a message with the ID of created package so we can find it.

Thank you,
Filip

merckxist · 2017-04-03T18:13:45.000Z

Filip Braun post:7:

Hello merckxist,

Unfortunately I was not able to reproduce the issue on Win XP neither on Win 7.
Could you please send us log from your scan on Win 10 (where you see the devices) and then from Win 7 (where you don’t see the devices)?
We would like to try and look for the issue there.

To generate and send logs:
First enable debug logging: GUI → Settings → General → Maitenance → Enable debug logging
Then reproduce the issue (Run network scan).
Then create support package and submit it (https://www.avast.com/en-us/faq.php?article=AVKB33) and send me a message with the ID of created package so we can find it.

Thank you,
Filip

The support file packages have been uploaded. Log capture from Win 7 is 1ZAHL. Log capture from Win10 is JDISN.

Thanks for looking at this, let me know if you need anything else.

Announcements