Just installed the new standalone beta vpn on a second system for testing purposes.
- Second system grabbed an existing single-use Securline VPN License in use on another primary system.
- Turned out that to use and insert the monthly activation code provided for the beta, it was necessary to deactivate the new freshly installed installation and then insert the monthly license code provided. The process to do so was not readily apparent.
- Deactivation seemed at first to involve uninstalling the new application. What should have been clear was this procedure would deactivate the primary vpn license and thus did not involve removing the application.
- Both systems have AIS installed as a part of a 3-system license.
The second system did snatch the single-use vpn license once before when an earlier version of avast standalone vpn was made available. The end result was the primary system lost access to the vpn network which I had paid for, or until the secondary system was removed from the vpn network. In both cases, in the first install and the newest one, another avast vpn was installed on the second system.
An average user might not know what to do if they encountered this edge case anomaly.
I propose a modification of the vpn install process to allow the manual insertion of a license or activation code similar to what is already in place in paid versions of avast. This, I feel, would help to prevent an edge case of multiple use of a single license, and allow the insertion of two or more single-use vpn licenses if required.
Other than this one issue, the standalone vpn works well and transparently.
