Using Avast with Viscosity - possible DNS problem?

[REDACTED]

Hi,
I'm running Win 10 pro v1511 buil 10586.420
My rig;
i7 4790, ASUS Z87 Plus mobo, 32GB RAM, R9 390,

I'm always connected via Ethernet LAN (no wifi); connection is high speed Turbo via co-ax cable

I'm using Avast Free v 11.2.2.2262

I'm using TorGuard VPN service with the Viscosity app provided by TorGuard, v1.0.0.1098

I've had a an ongoing problem with my internet kicking out while running through the VPN.  What happens is that the regualr Windows (non VPN) adapter stops working properly. I get the yellow disconnected warning triangle in the taskbar network icon. Browser pages, email ... don't work. Error messages on web pages are generally just disconnect or DNS relate:

This site can't be reached
Try:
Reloading the page
Checking the connection
Checking the proxy and the firewall
OR:
server DNS address could not be found. Search Google for speedtest net. ERR_NAME_NOT_RESOLVED

Occasionally the problem can be resolved by turning off the VPN and rebooting, but usually I have to uninstall the Network adapter in Device Manager, and then reboot and let Windows ID then re-install the drivers. I can also do this manually, but either method is a temp fix; it still doesn't resolve the internet kick outs and having to start over, by re-installing the network adapter again.

I've ruled out viruses ... multiple scans, multiple times - on two platforms (Win 7 and Win 10), two different mobo's (the other one a Gigabyte board), updated drivers, etc.

One of the troubleshooting things I've tried is to manually set the IPv4 DNS addresses. This works temporarily, but the adapter keeps resetting back to "Obtain IP Automatically". It's not like virus behavior - that usually happens in the other direction - it would be going from Obtain Automatically routed to another DNS for the virus to intercept traffic ... plus the multiple scans show nothing, different OS installs, etc.

I've tried troubleshooting with the TorGuard techs by toggling various DNS settings in Viscosity or the TorGuard app on or off, or disabling IPv6 in the Windows (non VPN ) network adapter. The one temp fix that seems to work is manually changing the IPv4 DNS address, but as mentioned earlier, the settings never hold.

I even had the cable company come out, test my lines for connectivity and then swap out my router for a new one. So at this point I'm going through the non-variables ... what's been consistent about the installs?
And each system has had Avast installled.

So now I'm wondering about Avast.

Is it possible that Avast detects the manual DNS change on the IPv4 settings as virus behavior, and auto-resets the adapter back to Obtain automatically? How would I know this?

Thanks

[bob3160]

I;ve reported this directly to Avast. Let's see if they have an answer for you.

[REDACTED]

I;ve reported this directly to Avast. Let's see if they have an answer for you.

Thanks

[REDACTED]

Was there ever any feedback to  this thread please?

I have what may be a related problem. I am running Windows 10 Home and installed Viscosity (as recommended by my prefered VPN) but the offer of the Avast VPN appears to prevent Viscosity from connecting automatically. I have to shut it down, leaving the Viscosity background service running, and restart the Viscosity client. The whole procedure takes quite a few minutes (maybe 10) to get the VPN connected before I can start working and feel safe. I find it really annoying.

I do have an easy work around with an SSH tunnel to the VPN but it slows down my connection quite a lot.

Is there any way to stop the Avast offer of their VPN from starting up? It is not so  easy to find.

Thanks for any assistance.

[Asyn]

Is there any way to stop the Avast offer of their VPN from starting up? It is not so  easy to find.
Thanks for any assistance.

-> https://www.avast.com/faq.php?article=AVKB96#artTitle (Add/Remove components)

[REDACTED]

Thanks a lot for the extremely fast response!
That was marvellous
Mo

[Asyn]

You're welcome.