SecureLine and Windows 10

[anarkii]

In the current build (10049) SecureLine doesnt want to connect to any VPN.
Avast error message is ‘Sorry, it is not possible to establish a connection’

Avast SecureLine TAP Adapter 3 is greyed out and disabled.

When I enable it, then try and reconnect to SecureLine, it fails the connection with the error message above, then greys out the TAP connection.

Will there be a fix for this via the program or shall I just wait and see with a new build of Windows 10?

[agress]

Hi anarkii,

We are looking into this right away. Will post back when we have some specific and useful info to share.

Best regards,

Davidek

[agress]

The issue was identified and we are working on a fix right now. Will post back with release/fix timing

[hlavacekj]

Hi anarkii,

please try this:

• open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class
• then press ctrl+f and serach for aswtap (should be located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E972-E325-11CE-BFC1-08002BE10318}\000X - where X stands for the instance of SecureLine adapter)
• crete new string value here (value name = ComponentId, value data = aswtap)
• enable SecureLine adapter and disable it again (when you are not connected to SecureLine, adapter should be disabled as default)
• try to connect to SecureLine

Hope it will help.

[anarkii]

Hi HK.

Apologies it took so long to reply, but your fix worked great, thank you

[anarkii]

Just wanted to bump this thread as you will need to do the registry editing still with todays release of Windows 10 - Build 10074 Insider Preview until a program fix is offered.

[system]

Hi,
I have W10 Build 10074 and the issue described above.
I checked the Registry and the ComponentId, value data = aswTap is already present.
When I try to start a connection the adapter is Enabled, Identifying… then back to Disabled, then the error message Sorry, it was not possible to establish a connection.
Tried a Repair of Avast but still not connecting.

Any ideas?

Thanks!

Martin

[bob3160]

Secure line seems to detect my current connection as insecure and keeps wanting to connect whenever I start up.
That same connection is recognized as a secure connection when I boot into the Windows 8.1 partition ???

[system]

Hey I had the same issue…the registry fix worked. buttt…Like one member said earlier …that key was already there. I replaced the aswTap with aswtap…lowercase t and did the enable and disable then it worked. Thanks and hope this helps

[system]

@mg71 post:7

Hi,
I have W10 Build 10074 and the issue described above.
I checked the Registry and the ComponentId, value data = aswTap is already present.
When I try to start a connection the adapter is Enabled, Identifying… then back to Disabled, then the error message Sorry, it was not possible to establish a connection.
Tried a Repair of Avast but still not connecting.

Any ideas?

Thanks!

Martin

try to replace the T with lowercase t…worked for me

[system]

Yes that’s worked.

Many thanks,

Martin

[anarkii]

Unfortunitly you need to do this fix (use lowercase aswtap) for todays build of 10122. Still no update from Avast that does it for you just yet.

[anarkii]

annnd again with 10125 and todays build of 10130.

[anarkii]

@anarkii post:13

annnd again with 10125 and todays build of 10130.

And again with todays build of 10158.

For the mods/admin etc - will there be a program fix or update to Avast that will fix this in the RTM of Windows 10 and beyond? Being a simple Registry fix seems like it should be a very easy update to push out.

[bob3160]

Apparently I no longer have the problem:

http://www.screencast-o-matic.com/screenshots/u/Lh/1435697351497-26174.png

http://www.screencast-o-matic.com/screenshots/u/Lh/1435697419866-87323.png

http://www.screencast-o-matic.com/screenshots/u/Lh/1435697480621-86194.png

[system]

Every build update I have to reinstall windows 10 and go through this process to get it working again. But it does function

[system]

I got the same problem. I use build 10159.
I couldn’t follow this solution as I have many \000X keys? and don’t know which one is the right one!

@HK post:4

Hi anarkii,

please try this:

• open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class
• then press ctrl+f and serach for aswtap (should be located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E972-E325-11CE-BFC1-08002BE10318}\000X - where X stands for the instance of SecureLine adapter)
• crete new string value here (value name = ComponentId, value data = aswtap)
• enable SecureLine adapter and disable it again (when you are not connected to SecureLine, adapter should be disabled as default)
• try to connect to SecureLine

Hope it will help.

[bob3160]

@Don49 post:16

Every build update I have to reinstall windows 10 and go through this process to get it working again. But it does function

Have you tried to simply do a repair of Avast (Programs and Features > Select Avast > Select Repair > When the process finishes, reboot your system.
That should take care of things. No need to reinstall Windows 10.

[system]

Build 10240 - used regedit as described above; all I had to do was change aswTab to aswtab and I was able to succcessfully connect.

[wphschmidt]

@bob3160 post:18

@Don49 post:16

Every build update I have to reinstall windows 10 and go through this process to get it working again. But it does function

Have you tried to simply do a repair of Avast (Programs and Features > Select Avast > Select Repair > When the process finishes, reboot your system.
That should take care of things. No need to reinstall Windows 10.

Just to clarify as well, trying to resolve issues with Secureline by doing a repair of Avast Security software may well be the ticket, however there is the “Stand alone” version of Secureline that may be installed without the use or installation of Avast software and thus a “repair” doesn’t apply .

edit:
To add, the HP ENVY I purchased couple of months back came with Secureline (standalone) PreInstalled with a trial period of 30 days