Avast WEBforum

Avast Products => Avast Omni => Topic started by: HeffeD on July 27, 2019, 07:34:36 PM

Title: Some beta feedback. (Issues?)
Post by: HeffeD on July 27, 2019, 07:34:36 PM
I hope this is the proper forum for beta feedback/issues!

Omni takes too long to come back online after a network Disconnect.
I installed my Omni yesterday, and last night I updated my router's (Netgear R6400) firmware. I was surprised to find that after my router had rebooted, I had no internet connection on any of my devices. Having only had the Omni online for a few hours, my first thought was that the firmware update was bad. In the process of troubleshooting, I realized the Omni was offline. I waited a few minutes, which I definitely thought was long enough for a device to reconnect, the Omni was still offline.

Figuring it must have gotten very confused during the firmware update, I unplugged the Omni from power for 30 seconds, then plugged it back in. I waited again for what I thought was plenty of time for a device to reconnect, but Omni is still offline. I then reset it, and waited... I don't know how long it took, but it was easily more than 5 minutes. Just about the time that I was considering a reinstall, it finally came back online.

This was happening during a full AV scan on my PC. I did get the message that I had connected to a new network, (No, I hadn't...) and it wanted me to tell Omni which type of network I was connected to. I left the window open, and planned to address this when the scan had completed. Unfortunately, the message dialog times out. Shouldn't this wait for input from the user?

Is this expected behavior, or an issue with my unit? If this is expected behavior, I think it's important to try and lessen this time frame, because router reboots or firmware updates are fairly common occurrences. Less technical people aren't going to understand that they're still protected at this time, because technically none of their devices are actually connected to the internet until the Omni is back online.

Update: Yes, my unit breaks when I reboot the router.

I had been thinking about the issue, and when I initially installed the Omni, it was easiest to plug it into an open port on the switch in my entertainment center. I did notice that the Omni comes with a very short ethernet cable, so I was wondering if maybe having a 50 foot cat6 cable and a switch between it and the router was the issue. So I shuffled some things around this afternoon so the Omni would be plugged directly into the router.

Then I decided to time how long it took the Omni to come back online after a router reboot. I rebooted, and started timing after the router had fully come online. After twelve minutes, I got tired of waiting, because that is an absolutely ludicrous amount of time to wait for something to come online after a disconnect, and power cycled the Omni. I then waited another six minutes (!) for it to come back online. Six minutes seems pretty long for a disconnect as well, so I reset the Omni. It was back online in just a couple of minutes!

So something is definitely wrong here. The unit definitely shouldn't require a reset after a router reboot.

The software is also broken if you try to open it while the unit is offline like this. It requires you to force quit it. Even after a reset and the Omni is back online, the software won't recognize it as such, and you need to restart your computer to make it work again.

Network scan seems broken after initial install?
When configuring Omni for the first time, the network scan found all of my devices and said the device was protected. I did go through and name the devices it was unaware of. Now any subsequent scans only show my PC and my router. (Which is unnamed for some reason) It says there are no problems with the network, but the only scan that completes is my PC. The router just sits and scans indefinitely. Is this normal?

I wonder if I caused this problem by my power disconnection and resetting the Omni during troubleshooting of my network going dark. I did go through the reconfigure hub steps from the settings menu, but this kept all of the previous settings. Is there a method that can completely wipe the Omni and start fresh?

Edit: Reading the support documents, I found that you can factory reset the Omni by pressing the reset button for 10 seconds. I did that, but the network scan still behaves as mentioned above.

Omni doesn't respect connected device names?
Omni should report your network device names to your router. All of my devices were named on my router. During Omni configuration, if these names weren't added automatically, I renamed them so I can see these same names in my connected device list in Omni. Apparently one of my Amazon devices hadn't been online during my Omni configuration, so it wasn't recognized/named. It apparently woke up to phone home around 3:00am. When I woke up, Omni wanted me to list the owner of the device. Looking at the device details, the name was the internal name of the device, which was Amazon(list of characters). Since I have several Amazon devices, this name didn't meant anything to me. So I opened my router GUI to cross reference the IP address with the network name. It isn't at all helpful when you look at your LAN address table and see 17 devices all called Avast Omni... One of these days I'll go around and unplug all of my Amazon devices to figure out what this device actually is, but that's not happening right now.

Refresh the device list?
It would be nice if there was a button that will refresh the current status of your devices. I don't know how often Omni polls the device status, but it's a little confusing to look at the device list and see my VoIP phone listed as offline, when I can see that it is in fact online and I can make/receive calls.

More robust networking features...
Since this unit basically takes over your routers job of talking to your devices, in order for it to be taken seriously by users with larger or complicated networks, you'll need to add better networking controls. Such as DHCP address reservations, or QoS settings.

On my network, I definitely want devices such as VoIP phones to have bandwidth priority over basically everything, and I have several smart devices that require either a static IP address, or an address reservation in order to be properly controlled by my home automation software. So when I look at the list of devices attached to my router, I want to see my named devices (as I've already mentioned, above) as well as the actual IP addresses and QOS settings I've assigned them.

My home automation still works, so the Omni is interfacing adequately, but it really does my head in to look at my attached devices and just see a bunch of Avast Omni's with random IP addresses.  :o
Title: Re: Some beta feedback. (Issues?)
Post by: J.Spiers on July 28, 2019, 12:57:58 AM
I agree with and have seen pretty much all of these kinds of issues since getting everything up and running properly. Additionally, I'm also having an interesting issue with the Omni software where I remove a device that is no longer connected to the network being "re-discovered" almost immediately. In fact, I replaced my router the other day and the Omni software still "re-discovers" these devices even though they have never been connected to this router, WiFi or ethernet.

I haven't had an issue with the omni hub taking a long time to come back online after the router disconnects it though. For me, it generally reconnects right away once the router comes back online.

Jess
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on July 30, 2019, 06:47:16 PM
I haven't had an issue with the omni hub taking a long time to come back online after the router disconnects it though. For me, it generally reconnects right away once the router comes back online.

Interesting. After a router reboot, or simply a network disconnect? They appear to be different.
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on July 30, 2019, 06:56:34 PM
It appears that there are differences between a network disconnect versus a router reboot. I'm assuming that with a router reboot, it's likely that your network 'fingerprint' changes, which confuses the Omni. Meaning, that rebooting your router will likely issue new IP addresses to any devices that don't have a static or reserved IP address. (Including the Omni) I'm not a networking expert, so this is just a guess.

As for just a network disconnect, there are some obvious security issues. The unit will go offline and is unable to report its status to mobile devices. The software on your PC does appear to poll the Omni every so often, so eventually it will figure out the Omni is offline, but the app on your mobile device, (at least with the Android version) will continue to report that you're fully protected, even though the Omni is in fact offline.
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 01, 2019, 06:10:16 PM
Omni causes my phone (Android 7.0) to disconnect from my network anywhere from 1 to 5 minutes.

My phone's network connection is used in part as a presence detection tool for my home automation system. The attached image shows my connection history from midnight until 10:00am. The 'network' line graph shows my connection to my router. All of the blue lines show disconnects.

The other line graph is monitoring my phone's GPS coordinates. I do use both of these to determine whether I'm home or not, for accuracy purposes. If all I was monitoring was my network connection, each disconnect from my router would be continually firing off the automations triggered by being away from home. (False positives)

This is quite abnormal behavior. When not using Omni, my phone only disconnects If I'm away from home.

Edit: After looking closer at my network traffic, other devices are being interrupted as well. None as often as my phone, but often enough for concern. Why is this happening?

Update: The disconnects are only from devices connected through WiFi. I did relocate the Omni, wondering if it was generating RF interference since it is right next to my router. The Omni is now 30 feet from my router, but this has made no difference to the disconnects. And no, I do not have any WiFi disconnects when not using the Omni.

I know that the concept of the Omni is network wide protection, including IOT devices, but if part of this protection is causing disconnects to WiFi reliant IOT devices, It's actually a hindrance for home automation setups.



Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 05, 2019, 10:24:46 PM
This is a partial log from my home automation system complaining about the connections being dropped.
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 15, 2019, 11:08:04 PM
What is the actual purpose of this beta? Is it actually a stress test and you're really just wanting bodies to give you more networks to monitor, and you aren't actually looking for problems to be reported?

I'm just curious because I've never participated in a beta where there is so little feedback from the devs. This has been a very odd experience so far. I've reported some serious issues and haven't heard anything! Not even a, "we're looking into it"...

Currently, this product is unusable for me due to the way it's interrupting my network traffic and causing triggers to misfire with my home automation system. Is anybody else participating in the beta having this issue? Or am I the only one that has active device monitoring and is able to see it happening?

I'm willing to continue running the Omni in the interests of beta testing, but the lack of input from the devs has me wondering if it's worth the hassle to do so. I'm all for helping to improve the product, but if I'm putting up with a headache for something that is apparently beyond the scope of this testing phase, then I'd like to know and I'll remove it from my network.

Thanks!
Title: Re: Some beta feedback. (Issues?)
Post by: Filip Havlicek on August 17, 2019, 01:30:55 PM
Hi HeffeD,

first of all, sorry for nobody from the Avast team replying to your messages. I have a feeling that your issues being so specific might have played a part in it. The purpose of the beta is definitely to gather feedback and fix potential issues.

Sending logs from your Omni hub
Since at least some of the issues here might require you to send us logs from your hub after you reproduce the issue, here is how to do it. Both Android and iOS admin/parent apps should contain an option to send logs from your hub in "More - Help & Feedback - Send Bug Report". The implementation is unfortunately not optimal at the moment so once you get the "OK" message, it only started sending the logs, not finished it - the logs are usually 100-200MB in size, so adjust the time accordingly based on your upload speed. Whenever you reproduce anything and upload the logs, note an approximate time of the upload and let me know what was the issue so that I can assign the investigation to proper people in the team. Now to tackle at least some of the issues.

Omni takes too long to come back online after a network disconnect
It definitely shouldn't take the hub to come back online after either router flash/reboot or the hub reboot itself. Not sure how long your router itself takes to reboot, but for example at my home if I reboot the router everything is back online in under 60 seconds and out of those it takes at least 30 seconds for the router itself to reboot. Both R6400 and R6400v2 should be supported, so I'm thinking it shouldn't be a case of router-hub incompatibility, but rather something with the hub itself or the network setup you are running might be somehow interfering with the hub. The hub is meant to be plugged into the main router, switch should matter that much, but if it's a managed one, it can definitely have an influence. To narrow this down a bit, can you try reproducing this and sending us the logs? Please note the times you rebooted the hub/router and the hub coming online so we can relate the logs with what you are experiencing. I can't really comment about the state of the Windows client you also mentioned, things should have changed for the better since you first posted, if you are still having troubles with the Windows client, let me know.

Network scan seems broken after initial install
I'm not sure what "network scan" you mean. When you open the Omni Windows client, is it the "Your home - X Online devices" section or the "This computer - Protection - Wi-Fi Inspector" section?

Omni doesn't respect connected device names
You are mentioning two issues here. First one is Omni not picking up names of your devices as you set them up on the router. As far as I know (and you can totally prove me wrong here) renaming devices on your router is a router-proprietary feature and it doesn't reflect in actual network hostnames of the devices nor the route provides any API to read those. There isn't much we can do about that unless Netgear can be convinced to provide an API for this. Second issue is your router listing 17 devices called Avast Omni. That is an unfortunate sideeffect of how we acquire traffic (we basically need to convince the router the hub represents all the devices and vice versa) and there isn't much we can do about that. Maybe this is going to change in one of the future software/firmware releases, but I can't make any promises at the moment.

Refresh the device list
The "refresh" should happen in terms of minutes, might depend on the actual (type of) device, especially in the online->offline direction. Did it get better over time or does this still happen? If it still happens, can you reproduce and send us the logs? Apart from the time I'd also need the IP and MAC of the device in question.

More robust networking features
We don't touch DHCP in the current setup, so DHCP leases are still issues by your router and therefore any setup you have in place, such as DHCP reservation, should be preserved. Can you confirm your devices get different IP addresses than they should? About QoS, I don't believe we interfere with it in any way, so again whatever you have set up should be working - I would need to verify this is the case as I haven't personally seen a network with Omni hub and any kind of QoS yet.

Omni hub offline reporting
The status should be generally done via the communication of the Omni hub with our cloud. The thing with Android especially (and I suspect iOS as well) is that once the screen is off, the device is not really connected to the Internet all the time, but it connects from time to time (if you want to read about it more, search for Android Doze for example, specific vendors also tend to implement their own things). So it can really be that the hub is reported as offline in our cloud, but the information just didn't get into the Android device.

Omni causes my phone (Android 7.0) to disconnect from my network anywhere from 1 to 5 minutes
This is something I have never seen before, it shouldn't really disconnect anything for such a long time (I have seen ~15 second disconnects on my network in the past whenever there was supposed to be a DHCP re-lease, but that got fixed since then). Is it really for 1-5 minutes? Can you watch out for it and whenever it happens again (especially for the longer time periods above 1 minute), send us the logs with the approximate time the device was offline and its IP and MAC address?

Thanks for the feedback and for the wait as well, let's hope we can get this moving from now on :)

Filip
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 17, 2019, 05:58:57 PM
Thanks for the feedback and for the wait as well, let's hope we can get this moving from now on :)

Thank you Filip, for your detailed response. I really appreciate it!  :)

I'll reinstall and get some logs.

I haven't experimented with the router reboots since I initially reported them. As for the network setup, I'll have the Omni plugged directly into my router. I initially did have it running through a switch, but did reconnect a few things so it was plugged into the router. I do run a DNS server on my network. Is Omni also trying to act as a DNS server? Perhaps the two are fighting? I'll have to do some more tests.

Yes, with the Network Scan Issue, it's the Wi-Fi Inspector. When the scan 'completes', It has only secured the PC. The router just scans forever. I'm comparing it to the initial network scan when it locates all of the connected devices and secures them.

Thanks for letting me know about DHCP. I'll look the devices up by their MAC addresses and see if they're actually getting different IP addresses than they should. I'll also look into the QoS. The naming issue makes sense now that you mention it...

Thanks again, I'll get back to testing.
-HeffeD
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 17, 2019, 07:10:14 PM
Here is a screenshot showing the Wi-Fi Inspector behavior. As you can see, the scan says it's complete and that there are no issues, but the router entry is still scanning. It never completes the scan.
Title: Re: Some beta feedback. (Issues?)
Post by: bob3160 on August 17, 2019, 11:01:46 PM
Granted, it takes a long time for the scan to complete but, on my systems,
it did finish the scan.
(https://screencast-o-matic.com/screenshots/u/Lh/1566075580722-78124.png)
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 18, 2019, 12:37:39 AM
What happens when you run the scan again? It will give me results like that the first time, but never again. I've waited several hours to see what happened, and the router stayed as shown in my screenshot.
Title: Re: Some beta feedback. (Issues?)
Post by: bob3160 on August 18, 2019, 12:44:47 AM
What happens when you run the scan again? It will give me results like that the first time, but never again. I've waited several hours to see what happened, and the router stayed as shown in my screenshot.
I just opened the UI and this is what I got on the next run of the scan. (It only took a second.)
(https://screencast-o-matic.com/screenshots/u/Lh/1566081790618-62799.png)
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 18, 2019, 01:33:11 AM
Odd... You don't show anything on your second scan. I wonder which is correct?
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 18, 2019, 01:43:54 AM
Filip, I just uploaded a log file at around 5:30pm MST. (I believe around 1:30am forum time)

The logs show two router reboots. I don't know how long it took to come back online the first time, because I wasn't expecting it to come back online, so I ran an errand.

I did another reboot, and it took 19 minutes for the hub to come back online. And interestingly, when this happens, it logs me out of my Avast account, and I need to relog using the desktop software.

As I've stated, my router is a Netgear R6400 (V1) and I have the hub plugged directly into the router using the short Ethernet cable supplied with the hub.

Edit: My router reboots in about 60 seconds.

Thanks!
-HeffeD
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 18, 2019, 06:05:29 PM
Filip, I've just uploaded another log showing my phone disconnects. I've sent the MAC and IP addresses through PM.

Edit: And let me reiterate, that when not using the Omni, I don't see these disconnects.

Thanks!
-HeffeD
Title: Re: Some beta feedback. (Issues?)
Post by: Filip Havlicek on August 21, 2019, 08:57:32 AM
Hi HeffeD,

OK, I did some investigation into the issue of the hub not being online for quite a long time after router reboot. What I know for sure is that the hub seems offline due to DNS resolving not working for it. It seems to me from the logs that you might be running your own DNS server on the Raspberry Pi? Are you sure that it works correctly for the hub? Do you have it properly configured on the router as well?

Maybe a quick test would be nice here - could you reconfigure your router to use some public DNS (8.8.8.8 for example) instead of your own and reboot your router to see if it helps with the issue? We are also making some changes on our side that might make the DNS resolving more resilient especially in non-standard cases, but it's not ready yet for you to test.

Regarding the device disconnects, I saw a potential cause in the first logs you sent as well, I forwared it to the team to investigate further.

Filip
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 21, 2019, 08:33:22 PM
Hi Filip, yes, I do run a DNS server on my network. I had mentioned this in my first reply to you.

-snip-
I do run a DNS server on my network. Is Omni also trying to act as a DNS server? Perhaps the two are fighting? I'll have to do some more tests.
-snip

I use the server for network-wide ad blocking. As for whether or not it works correctly for the hub, I couldn't say. I had been curious when I first received the unit if the hub would need to act as the DNS, which would make my ad-blocking system break. I was happy to see that it did not affect this. I had been assuming that the hub routes DNS lookups through my router., as all of my network devices do. Is this not the case?

Yes, my router is configured to use my Raspberry Pi for DNS lookups, the ad-blocking software on the Pi (Currently Adguard Home, but I've also used Pi-Hole...) is using Cloudflare for resolving DNS. The Pi has a static IP address.

I did just switch the DNS to my ISP's servers and did a reboot. The hub came back online within 10 seconds after the internet connection was restored. So the hub is definitely unhappy with resolving when my DNS settings are looking at my Pi. I'm curious as to why though, because none of the other networked devices have this issue after a reboot.

Thanks so much for looking into this. I really appreciate it!
-HeffeD
Title: Re: Some beta feedback. (Issues?)
Post by: Filip Havlicek on August 22, 2019, 02:48:34 PM
Hi HeffeD,

sorry, missed (forgot) the DNS information from the original post. The hub is currently not happy with DNS servers that seem to work but are somewhat non-standard in their behavior, for example not returning by-the-book answers. We have a fix for that in the pipeline, I don't know when exactly that will be released to the external beta, I would be hoping it would be pushed out during next week, but no promises.

Regarding the devices being offline, I still didn't get the answer from the devs. It's a little bit weird that it only happens for WiFi devices. Are all of them running some kind of non-standard (meaning something you wouldn't generally expect like home automation) software or are some of the just plain usual devices everyone could have? (What I'm trying to figure out is if there might be some software on the devices that would generate non-standard traffic in terms of content or amount that might result in the device being blocked by the hub from time to time.)

Filip
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 22, 2019, 07:07:17 PM
Hi Filip,

I don't know what to say about the non-standard DNS behavior. The Adguard Home software handles that, so it must be doing something odd.

The devices that have the most disconnect issues are my phone, and two Logitech Harmony hubs. They are standard items that anyone can buy. My home automation software does poll these devices regularly to check whether or not they're online, but the devices themselves are running the stock software.

My phone does use an app called Owntracks to report its location to my home automation software. It only reports if I've moved 500 meters, so it doesn't report if I'm stationary.

Interestingly, I do have two Amazon Echo Dots that don't drop their connection. One of them is positioned less than 3 feet from one of the Harmony hubs, so I don't feel it's any sort of Wi-Fi interference, because you'd think the Harmony hub and Echo Dot would be dropping at the same time, but that isn't happening.

The Harmony hubs are odd though, because they tend to both drop at the same time. So it could be that they are trying to communicate with Logitech's servers, which is getting blocked or something? The drops are also inconsistent. I haven't seen them drop in the last 48 hours... Very strange!

Thanks!
-HeffeD

Edit: Typo.
Title: Re: Some beta feedback. (Issues?)
Post by: Filip Havlicek on August 22, 2019, 10:36:36 PM
Hi HeffeD,

I have a hunch that some of your devices seeming disconnected occasionally might also be related to the AdGuard Home software you are running on the Pi. It seems to create a lot of DNS requests (and/or other connections) at certain times - hundreds in the matter of seconds - which results in Omni at least partially blocking the Pi until it "calms down" because that is definitely not a standard behavior. When in the "calm down" period DNS requests that are not cached on the Pi might not go through and time out/return an error potentially resulting in the devices seeming offline.

This is obviously just a theory, there might be a way how to verify it on your side, although I'm not sure how much configuration options the AdGuard Home has. I took a look at AdGuard DNS on GitHub and it seems to have a caching option in the plugin.cfg file here https://github.com/AdguardTeam/AdGuardDNS/blob/48a2aee015fd346fd683bd655860b60beff95b40/plugin.cfg#L32 If I understood correctly, commenting out the cache:cache line using # should disable caching. Not having the cache would result in DNS resolving being slower in general, but might also remove the issues you are having with the devices.

Again, most of what I wrote is just a theory, but if you would like to dig deeper into it, I'd say it's worth a shot.

Filip

EDIT: The other option, of course, would be to switch to your ISP's DNS on the router and keep it like that for a few days to see whether the disconnects will disappear or not. Not sure if that is something you'd want to go through, I guess you are using the AdGuard software for a reason :)
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 23, 2019, 05:41:17 PM
Hi Filip,

It's funny that you mention that, because I'd been thinking about what you said about the DNS not functioning normally, so I was going to switch back to Pi-Hole this morning and see what sort of effect that has on the disconnect issues.

I'll keep you posted!

Thanks!
-HeffeD

Edit: Well, Pi-Hole seems to behave better as far as DNS resolving and router reboots are concerned. After rebooting the router, the Omni hub comes back online within a few seconds after the internet connection is restored. I'll keep watching to see if there are changes to the disconnects.
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 26, 2019, 05:44:14 PM
Watching my connections all weekend, the only thing disconnecting is my phone.
Title: Re: Some beta feedback. (Issues?)
Post by: Filip Havlicek on August 27, 2019, 11:29:10 AM
Hi,

and that phone is supposed to disconnect or not? :)

Do you see any change in the disconnect "pattern"?

Filip
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on August 27, 2019, 06:36:49 PM
Hi,

and that phone is supposed to disconnect or not? :)

Do you see any change in the disconnect "pattern"?

Filip

Hi Filip,

No, the phone isn't supposed to disconnect. When Omni isn't running, it only disconnects when I go out of Wi-Fi range. These disconnects negatively affect phone and home automation performance. Automations meant to trigger when my phone disconnects or reconnects to the network are completely broken. I've had to modify these to use my presence awareness triggers, but this isn't ideal in many situations.

I do have a threshold I can set to account for the 'normal' temporary disconnects that happen as a battery saving feature when the device is sleeping. It's normally set at 2 minutes, so my home automation software only recognizes a disconnect longer than two minutes. So technically, I could increase this threshold, but raising the threshold to deal with an 8 minute disconnect isn't very practical.

Anyway, the threshold is only a 'fix' as far as home automation is concerned. The fact that I'm getting disconnects negatively impacts data usage on my phone. As I have a metered mobile data plan, most of my data usage only occurs when I'm connected to Wi-Fi. (Weather updates, software updates, streaming, etc...) This is of course, negatively affected by the network disconnects.

No, I haven't been able to discern any patterns in the disconnects. It appears random to me.

Thanks!
-HeffeD
Title: Re: Some beta feedback. (Issues?)
Post by: HeffeD on September 04, 2019, 12:38:02 AM
Hi Filip,

I guess the question I have would be, does Avast feel this is normal behavior?

Thanks!
-HeffeD
Title: Re: Some beta feedback. (Issues?)
Post by: Filip Havlicek on September 18, 2019, 01:07:55 PM
Hi HeffeD,

sorry for not answering for so long, my work schedule has been irregular as of late due to some troubles in my personal life. I'll try to get someone else to look into this issue.

I don't think this should be happening, so definitely something worth looking into.

Filip