We've released another update. It's technical and doesn't contain any changes for most of the users yet it fixes a major mistake.
If you use AdGuard VPN for Windows, you might notice that when pressing the Update button AdGuard ad blocker would be installed instead of the AdGuard VPN update. Obviously, it was an oversight on our part, for which we apologize to all the users who were affected by it. But one apology can't make up for it and we feel obligated to explain what happened.
The day before yesterday we released a new version of AdGuard for Windows but by mistake placed it on the AdGuard VPN for Windows update channel. This update was available for a couple of minutes but it was enough to cause problems. To better understand what happened, let's first figure out how AdGuard VPN is updated.
What could have happened after pressing the "Update" button? There are two possible scenarios:
We do apologize to you for this mistake and feel bad that our own negligence resulted in the incorrect update in the AdGuard VPN channel. This situation revealed the mistakes we made when designing the AdGuard VPN update process. It should not, at all, allow a situation in which the service pack that arrives is not the service pack of AdGuard VPN itself.
It's our fault that this problem has hit some users. We are particularly sorry for those who didn't have AdGuard ad blocker installed before. As an apology, we've given a six-month AdGuard ad blocker license and a three-month AdGuard VPN premium to all the affected users. If you are one of these people, please check your AdGuard account.