Disclaimer: AdGuard VPN for Windows is not an open-source project. We use Github as an open bug tracker for users to see what developers are working on.
For this release, we had a developer urge to make our VPN app compatible with x64 and ARM processors. This makes sense since most computers today run on 64-bit or ARM64 versions, which offer more processing power and memory. While we were at it, we also fixed a number of bugs and updated the VPN client.
Other improvements are in the UX department.
Locating the problem
The most common problems usually have typical causes. For example, if you’re having trouble connecting to a specific location or logging into your account, it might be due to a weak Internet connection or a temporary server issue.
To help you figure out what’s wrong and what you can do about it, we’ve added simple explanations in popups or snacks for such cases.
Exclusions made easier
To make it clearer how exclusions work, we’ve revised the wording and snacks. This should help users who were often confused and didn’t know whether AdGuard VPN was off or on for selected websites and apps.
Changelog
Improvements
- Compiled AdGuard VPN for x64 and ARM processors #643
Fixes
- Issues with application exclusions #703
- AdGuard VPN (x64) remains in
Program Files (x86)#700 - Previous version of app is duplicated in “Programs and Features” and can’t be uninstalled #691
- YouTube acts incorrect in exclusions when Wintun is on #682
- Default list of app exclusions doesn’t support some x64 apps #681
- Previously chosen DNS server changed its name back to “Default” after re-login #669
- Windows can’t get updates with AdGuard VPN enabled #663
- Import of unsupported file removes all website exclusions #610
- The Open main window at system start-up option doesn’t work #5074
VPN client (Implementation of AdGuard VPN protocol)
- Updated VPN client to v0.13.79 #708
- Minor fixes
AdGuard VPN for Windows direct download link: