I would like to report a concerning issue with Avast SecureLine VPN on Windows 11.
I have never knowingly installed, authorised, or used Avast SecureLine VPN. My preferred VPN service is Mullvad VPN.
Nevertheless, I discovered that Avast SecureLine VPN was installed on my computer and running as a Windows system service.
Here is what I have verified:
-
Avast SecureLine VPN does not appear in Windows Settings → Installed Apps or in the traditional Programs and Features list.
-
There is no registered uninstall entry for the product in the standard Windows registry locations.
-
The Windows service
SecureLinewas running automatically under the LocalSystem account. -
Its executable is located at:
C:\Program Files\Avast Software\SecureLine VPN\VpnSvc.exe -
The executable has a valid digital signature from Gen Digital Inc.
-
The installation configuration file:
C:\ProgramData\Avast Software\Icarus\avast-vpn\icarus.inicontains the following entries:
installed=1 product-full-name=Avast SecureLine VPN vpn_ui=0 vpn_win_uninstall_val=0 vpn_svc=1 vpn_driver_install=1 vpn_driver_uninstall=1
These settings are particularly concerning because they indicate an installation with no enabled graphical user interface and no enabled Windows uninstall-registration component.
I have stopped and disabled the SecureLine service as a precaution. I have not manually deleted program files, services, registry entries, or VPN drivers.
My questions to Avast are:
-
How can Avast SecureLine VPN be installed without the computer owner’s knowledge or explicit approval?
-
Can SecureLine VPN be bundled with other software, including products distributed by Gen Digital?
-
Why was this installation configured without a graphical interface or a normal Windows uninstall entry?
-
What is the official, safe procedure for completely removing this installation, including its services and drivers, without affecting Mullvad VPN, Oracle VirtualBox, or Windows networking?
-
Is AvastClear officially supported for this specific SecureLine VPN installation?
I have found another discussion from July 2025 describing a remarkably similar situation on Windows 11.
I believe this issue deserves a clear technical explanation and an official removal procedure.
I would appreciate a response from an Avast representative rather than an unverified recommendation to delete files or use third-party removal utilities.