Avast VPN not turning off and hanging Windows 10 Sshutdown

[J2roc]

Thanks.
[/quote]
You can upload it here: ftp://ftp.avast.com/incoming/
Pick a unique name (and post it here), so the devs can find it. Thanks
[/quote]

Done. The file name is j2roc_7nx29d_vpn_log.rar

The filesize is 13,772,207 bytes.

thanks

[Asyn]

You're welcome. Now you need to wait for Pavel...

[Darren119]

hi, i am experiencing the EXACT same problem as the thread poster....Avast VPN slider button moving to "turning off" when i am done visiting certain sites but the switch on the screen then just spinning and not turning off, hanging like that and then no internet access. Just cant get out of it until i reboot. Sometimes it takes down my whole Win10 and i get blue screen "YOUR PC HAS CRASHED " after 5 or 10 minutes if i continue to struggle on with the PC.

this started happening about 3 or 4 days ago. Its frustrating as hell.

I have re-installed Avast VPN. No diff.

i am also running Avast Premium Security. I wonder if the two have a clash problem. The firewall in the APS is quite screwy, sometimes i need to toggle the firewall switch to get internet access when i start the PC for some reason. It seems to fight with the Windows Firewall and needs a toggle to get the two accepting who is in charge or something. Any rate this is probably an unrelated problem and has been going on for some weeks now.

This problem with VPN has been only the last 3 or 4 days.

Please help its driving me bonkers my whole system has ground to a halt

[Asyn]

Hi Darren, if you're willing to help, see Reply #8 from Pavel.

[Darren119]

ok ive made the log

heres a dropbox link for it

https://www.dropbox.com/s/fa2qs5932h5ltle/VPNscrewy-log.rar?dl=0

file is called VPNscrewy-log.rar

[Asyn]

Good job. Now you need to wait for Pavel...

[Darren119]

ok i also tried to close the VPN service to get things up and running again...i get access is DENIED...wierd....pls see attachment.

basically theres no way to save the situation but reboot which is just shaving days off my life

[J2roc]

ok i also tried to close the VPN service to get things up and running again...i get access is DENIED...wierd....pls see attachment.

basically theres no way to save the situation but reboot which is just shaving days off my life

Yes, it looks we have the EXACTLY same problem. It looks one can kill the VPN process in Windows 7 (according to an earlier post), but it does not work for me in Windows 10.

[Darren119]

Yes, it looks we have the EXACTLY same problem. It looks one can kill the VPN process in Windows 7 (according to an earlier post), but it does not work for me in Windows 10.

Jroc are you also running Avast Premium Security? i wonder if there is an issue between the two

[J2roc]

Jroc are you also running Avast Premium Security? i wonder if there is an issue between the two

Yes, but here is the funny thing. I moved to APS around October last year. The transition was seamless. So, things were okay for about 3 months. We now have three people reporting the problem. Wonder how many other have it.

My APS version is 19.8.2393 (build 19.8.4257.552).

[Darren119]

ive run APS for over a year and its been fine too. Clearly something has happened/updated/changed in the last 4 or so days. I ghosted my whole Win10 back to a week ago and i still have the problem

my APS is 19.8.2393 (build 19.8.4257.549)

[bob3160]

Jroc are you also running Avast Premium Security? i wonder if there is an issue between the two

Yes, but here is the funny thing. I moved to APS around October last year. The transition was seamless. So, things were okay for about 3 months. We now have three people reporting the problem. Wonder how many other have it.

My APS version is 19.8.2393 (build 19.8.4257.552).

Was your SecureLine installed as part of the Avast installation or, was it a separate install of just the VPN? (https://www.avast.com/secureline-vpn#pc)
If it was part of the Antivirus install, you might want to try removing it via Programs and Features select Avast and then select Change.
Then uncheck SecureLine once you've done that and restarted your computer, Install the free standing version from the link supplied.

[J2roc]

bob3160,

As I wrote way back in answer to this question, I am not 100% sure. I started to use Avast Firewall and Antivirus (Avast Internet Security?) 10 or more years back. I added VPN as separate module about 2-3 years ago. I then moved to APS in Oct 2019.

So, it would appear that my VPN was always a separate install.

Thanks for your suggestion. I will hold a couple of days to see what Pavel says. If I do not hear from him
I will try your fix.

In any case, it appears that something has changed in the past week as we have three people reporting the same thing.
Thanks again.

[J2roc]

A bit of googling got me this:

https://forum.avast.com/index.php?topic=221480.0

Looks like there was a similar problem in 2018.

Repy #3 in that thread says:

>>
OK, you need to install the standalone version of SecureLine.
http://secureline.tools.avast.com/tools/secureline/avast_secureline_setup.exe
<<

Note Reply #5 in that thread:

>>
From the changelog: SecureLine VPN component won't be part of AV. User will be offered to install standalone VPN client independent from AV (staged release not for all users now)
<<

Well, I never heard anything about it as I guess my VPN was always separate. But how can I be sure that it did not get bundled sometime after I got VPN about 3 years ago? When I check for Programs
I see Avast Premium Security and Avast SecureLine VPN listed separately. But, the installation date for both is 29 Nov 2019. That looks like the date that I may have moved from AIS to APS.

But, that still does not explain why the problem began just last week -- and for three of us.

[Norm2020]

I've also been having the same problem for the past week. I have Windows 10, and Avast VPN hangs when I disconnect the VPN. It also hangs if I try to change VPN location or if I shut down the computer while connected to Avast VPN.

Perhaps it's just a coincidence, but I installed the latest Windows 10 updates on Monday, January 13. (I postponed any later Windows updates to await feedback about their stability.)