Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: _lexi on September 21, 2018, 04:44:20 PM

Title: Avast Wifi Inspector: Very unusual behaviour
Post by: _lexi on September 21, 2018, 04:44:20 PM
So last night I successfully executed a Wifi Inspector scan using the "Home" setting. I then clicked on the notifications window and clicked on the "Details" button next to the "Scan complete" message for the Wifi Inspector scan. Then something odd happened.

Wifi Inspector displayed the list of routers and client devices found during the scan, but it also had "23%" above it, as though it was part way though a new scan. I tried clicking the "Stop scan" button, but that just displayed a spinning wheel in place of the button's text.

I clicked away from the Wifi Inspector, onto the "Status" page. When I clicked back to the Wifi Inspector page, it had returned to normal, and was displaying only the start scan button. I ran the Wifi Inspector scan again and it completed successfully.

1. Was this just a glitch in the UI or something more serious?
2. If it's something more serious, should I repair or reinstall Avast?
3. Will the weird 23% Wifi Inspector scan have compromised my network in any way? I reset the wireless bridge that my computer is attached to, but I haven't had an opportunity to reset my router or VDSL modem.
Title: Re: Avast Wifi Inspector: Very unusual behaviour
Post by: _lexi on September 21, 2018, 05:00:28 PM
Forgot to mention, I'm running:

Windows 10, fully updated
Avast Internet Security 18.6.2349, fully updated
Title: Re: Avast Wifi Inspector: Very unusual behaviour
Post by: bob3160 on September 22, 2018, 01:00:23 AM
Sounds like the first time you didn't completely allow it to finish.The second time would have been faster since it already had lot's of information and it completed the scan.
https://youtu.be/8IQNO8IaLeA


Title: Re: Avast Wifi Inspector: Very unusual behaviour
Post by: Asyn on September 22, 2018, 06:15:36 AM
Hi, it's a known GUI bug, nothing to worry about.