Fix it now
800, 809 and 789 are Windows remote access errors. Avast publishes none of them, and SecureLine on Windows connects over OpenVPN, Mimic or WireGuard rather than through the Windows remote access stack, so check first which connection is actually failing.
- Read the error carefully. A SecureLine failure normally appears as a “We’ve got something” dialog carrying a six-digit code. A three-digit 800, 809 or 789 comes from a Windows VPN connection profile – look under Settings, Network & internet, VPN and see what is listed there.
- Confirm the VPN is paid for. In SecureLine open Menu, then My subscriptions, and check that Active appears next to Avast SecureLine VPN. Avast states plainly that SecureLine needs its own subscription and that an Avast Premium Security subscription will not activate it.
- Choose a different server location and connect again. One overloaded or blocked endpoint produces a clean failure like this.
- Change the protocol in the app’s settings. Avast recommends Mimic where the default protocol is blocked.
- Disconnect and exit every other VPN client, restart, and connect once without launching anything else first.
- Test on a phone hotspot. If it connects there, the fault is the network you were on and nothing on the PC needs changing.
Do not go editing IPsec registry values for this. Avast lists the Windows protocols as Automatic, WireGuard, Mimic and OpenVPN – none of them IPsec or L2TP – so IPsec NAT traversal settings cannot affect a SecureLine connection on Windows.
If the tunnel comes up and survives a reconnect you are finished. If not, the next section explains what each number is actually reporting.
Why it happens
These three numbers belong to the Windows remote access layer, and Microsoft publishes what each one means. 800 is that the VPN connection could not be established because the server may be unreachable or the security parameters may not be configured properly. 809 is that the remote server is not responding, which Microsoft attributes to a device between the two ends refusing VPN traffic, and its Always On VPN guidance names UDP 500 or 4500 being blocked as the usual case. 789 is narrower still: an L2TP connection whose security layer hit a processing error during the initial negotiation.
Avast does not publish these codes, and that is not an oversight. SecureLine’s Windows client uses Automatic – which connects over OpenVPN and falls back to Mimic – or WireGuard, Mimic or OpenVPN chosen by hand. None of those is L2TP or IPsec, and none of them is dialled through the Windows remote access stack, so the stack has nothing to report about them. When SecureLine itself fails it says so in its own words, with a six-digit code.
So the first useful question is not “why is Avast failing” but “which connection produced this number”. On a machine that also carries a manually created Windows VPN entry, a work VPN, or a SecureLine profile set up on a Mac or iPhone where IPsec is used, the three-digit code is coming from that connection. Fixing SecureLine will not change it, and fixing it will not fix SecureLine.
The VPN subscription is not live
You have this one if Nothing connects, on any network, including a phone hotspot, while the antivirus side of Avast is healthy and paid up.
- Open SecureLine, go to Menu then My subscriptions, and confirm Active appears next to Avast SecureLine VPN.
- If it does not, sign in to the Avast account the installation uses and check which products it holds.
- Renew the VPN subscription, or remove SecureLine if you no longer want it. It will not open a tunnel without its own entitlement.
An Avast Premium Security subscription is not a VPN subscription. Avast says so in its own SecureLine FAQ, and this is the single most common reason a fully paid-up customer cannot connect.
The number is coming from a Windows VPN profile, not from SecureLine
You have this one if 789 in particular, or a three-digit code raised from Settings, Network & internet, VPN rather than from the SecureLine window.
- Open Settings, Network & internet, VPN and list what is there. Remove entries left by products you no longer use.
- If the entry is one you need – a work tunnel, or a manually configured connection – treat it as a Windows VPN problem and take 789 to whoever runs that gateway.
- Connect SecureLine from its own window and confirm it behaves independently of that profile.
The network drops the tunnel
You have this one if It connects on a phone hotspot and fails on one particular network, typically a workplace, hotel, school or guest network.
- Change the protocol in SecureLine’s settings. Avast recommends Mimic where restrictions block the default.
- Where the failing connection is an IPsec one, Microsoft names UDP 500 and 4500 being blocked as the cause of the 809 class of timeout – ask the network owner to permit them.
- Avast notes directly that administrators of public and company wireless networks may block VPN connections. If that is the situation, the answer is a conversation, not a workaround.
A second VPN client or a firewall owns the path
You have this one if It connects with the other client stopped and fails with it running, or with a third-party firewall active.
- Disconnect and fully exit every other VPN client. Two clients cannot share a default route sensibly.
- Stop a third-party firewall briefly as a test only, and if that is the cause, add a rule for the SecureLine executable rather than leaving the firewall off.
- Check for DNS filtering or parental controls on the router, which commonly block VPN endpoints by category.
The local installation is damaged
You have this one if Everything above checks out, the subscription is Active, and the client still fails on every network.
- Restart the machine and connect once before launching anything else.
- Uninstall SecureLine, restart, and reinstall it so its adapter is registered cleanly.
- Reactivate by signing in to the Avast account that holds the subscription.
Avast lists uninstall and reinstall as the last of its own steps, after the server, protocol, other-VPN, firewall and subscription checks. It is rarely the answer and it is never the first thing to try.
Full reference
What Microsoft actually publishes for each number
| Code | Microsoft’s published meaning | Where it is raised |
|---|---|---|
800 |
Unable to establish the VPN connection. The VPN server may be unreachable, or security parameters may not be configured properly for this connection | Windows remote access |
809 |
The network connection could not be established because the remote server is not responding, possibly because a device between the two is not configured to allow VPN connections | Windows remote access |
789 |
The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer | Windows remote access, L2TP only |
Read the third row again if you are troubleshooting SecureLine on Windows. 789 is specific to L2TP, and SecureLine on Windows does not offer L2TP. A 789 on that machine is telling you about a different connection.
What SecureLine’s own failures look like
- A “We’ve got something” dialog with one or more six-digit codes. Avast publishes a troubleshooting article for this and asks for a screenshot of the code if the steps do not clear it.
- “Maximum connections reached”, which is a licensing condition rather than a network one.
- “Sorry, the SecureLine VPN server has refused your license file”.
- “Your Avast SecureLine VPN is over”, which is the subscription talking.
- “SecureLine has encountered a technical issue”.
None of those is a three-digit number. If what is on your screen is one of them, the codes on this page are not your problem and the subscription and protocol checks are where to start.
Protocols and where they are chosen
| Setting | What Avast documents |
|---|---|
| Automatic | Connects over OpenVPN where possible and switches to Mimic automatically if OpenVPN fails. This is the recommended setting |
| Mimic | Avast’s own protocol, recommended where restrictions block the default |
| WireGuard | Selectable by hand |
| OpenVPN | Selectable by hand |
| IPsec | Avast documents IPsec and UDP 500 and 4500 in the context of Mac firewall configuration, not the Windows client |
Checks worth running before you ask anyone to change a firewall
- Confirm the internet works with SecureLine disconnected. Avast lists this first for a reason.
- Try a second server location, then a third. One endpoint in maintenance produces a clean, repeatable failure.
- Tether to a phone and retry. A tunnel that comes straight up on mobile settles the diagnosis in under a minute and saves you a firewall conversation you did not need to have.
- Restart the PC and connect before opening anything else.
- Run
ipconfig /allonce connected and confirm the virtual adapter holds an address.
How many devices the subscription covers
Avast publishes that an Avast SecureLine VPN (Multi-Device) subscription can be activated on up to 10 devices at once, and that subscriptions bought before April 2021 covered 5. If SecureLine is refusing connections on the newest machine in the house, count what is already activated before assuming a network fault – and note that this is a licensing limit, so it produces a licensing message rather than one of the codes on this page.
When a licence is the actual fix
There is one situation here where a purchase is the fix and only one: SecureLine has no live subscription of its own. Avast is explicit that the VPN needs a separate subscription and that an Avast Premium Security subscription will not activate it, so a customer who is fully paid up for the antivirus can still have no VPN entitlement at all. Arco supplies Avast SecureLine VPN subscriptions and will confirm the device count on the plan you are looking at before you commit – Avast publishes up to 10 devices on a current Multi-Device subscription, and 5 on ones bought before April 2021, so an older plan you are renewing may not be the size you remember. If My subscriptions already shows Active, this is a network or protocol problem and you should not be buying anything to solve it.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
800 |
Unable to establish the VPN connection. The VPN server may be unreachable, or security parameters may not be configured properly for this connection | Microsoft Learn |
809 |
The remote server is not responding, which Microsoft attributes to a device in the path – firewall, NAT or router – not configured to allow VPN connections | Microsoft Learn |
789 |
An L2TP connection attempt failed because the security layer hit a processing error during initial negotiations. SecureLine on Windows does not offer L2TP | Microsoft Learn |
Confirm the fix worked
- SecureLine reports a connected state with a named server location.
- A site that reports your public IP address shows the VPN location rather than your own connection.
ipconfig /allshows the virtual adapter with an address assigned.- Menu, then My subscriptions, shows Active next to Avast SecureLine VPN.
- Disconnect and reconnect once more to confirm the fix holds beyond the first attempt.
Questions people ask about this
My Avast Antivirus subscription is paid. Why does the VPN want its own?
Because Avast sells them separately and says so: “Avast SecureLine VPN requires a separate subscription to use. You cannot use an Avast Premium Security subscription to activate Avast SecureLine VPN.” Check what your Avast account actually holds before treating this as a technical fault.
Is error 800 an Avast error?
No. It is a Windows remote access error, published by Microsoft, and Avast does not use it. SecureLine’s own connection failures appear as a “We’ve got something” message carrying a six-digit code.
Should I open UDP 500 and 4500 for SecureLine?
Not on Windows. Those ports belong to IPsec, and Avast documents them for Mac firewall configuration. The Windows client uses OpenVPN, Mimic or WireGuard. Changing the protocol in the app is the equivalent move on Windows.
Will a VPN work on hotel or airport wireless?
Often, not always. Avast notes that administrators of public and company networks may block VPN connections, and its own advice where the default protocol is blocked is to switch to Mimic. Some networks block VPNs deliberately and no client setting changes that.
Can I run SecureLine alongside another VPN?
Installed, yes. Connected at once, no – two tunnels fight over the default route, and disconnecting the other client is one of Avast’s own troubleshooting steps.
