When the VPN detection is not working correctly then it could be due to a few reasons. First try Reverse IP in Config, this changes the VPN detection algorithm. If that doesn't work make sure only one active network adapter is being used and TAP if using OpenVPN.
If you want to make sure DNS leak fix is working then go to Config of VPNCheck Pro and select DNS leak fix in the tab, enter 0.0.0.0 if you're using Windows Vista and above or 18.104.22.168 if you are using Windows XP as the Preferred DNS server. Enable DNS leak fix, Press OK to exit the Config. Then restart either Cycle IP:Task or Cycle IP:Network so it will change to the new DNS server address. Once your VPN is connected open cmd prompt and type ipconfig /all.
In Windows 7 look for your main network connection which should read DNS Servers: 0.0.0.0. That means DNS leak fix is working.
In case there is a network error once DNS leak fix is enabled, then turning off and on the router might help. Disabling all network adapters not needed in Device manager of Windows could help DNS leak fix to find the main active network adapter.
Open config window of VPNCheck Pro then click the menu Help and Reset DNS manually.
Usually this is due to not using the correct VPN adapter name in Config. If using Windows 7 you can find VPN adapter name by going to Control Panel/Network and Internet/Network and Sharing center/Change adapter settings. Now you'll see all network adapters.
It could also be an issue in the config files of .Net framework. To solve this in Windows Vista and greater go to C:\Users\"username"\AppData\Local\Guavi and C:\Users\"username"\AppData\Roaming\Guavi and remove all directories and files in the folder Guavi. The drive letter could be different on your computer. Remember to enable show hidden files to see Appdata.
If you're using security software such as a firewall or similar it could block VPNCheck Pro from accessing Windows properly.
VPNCheck Pro is designed to work with the standard OpenVPN client from openvpn.net. It can be found here OpenVPN community client.
If this occurs there might be a permission issue. Copying the programs which you try to run to the user directory seems to solve this.
VPNCheck Pro is designed to run in Windows XP and greater using at least .Net Framework 2.
If trying to start VPNCheck and nothing happens then there might be a conflict in Windows and config files. VPNCheck will fix this automatically but you can do it manually.
To solve this in Windows Vista and greater go to C:\Users\"username"\AppData\Local\Guavi and C:\Users\"username"\AppData\Roaming\Guavi and remove all directories and files in the folder Guavi. The drive letter can be different on your computer. Remember to enable show hidden files to see Appdata.
DNS leak fix doesn't work: It can be resolved by changing to fixed DNS address in Windows.
Unable to close WindowsApps: Add permission to WindowsApp directory C:\Program Files\WindowsApps. Start the application you want to be closed. Then add the WindowsApp in VPNCheck Pro for example C:\Program Files\WindowsApps\Microsoft.WindowsCalculator_10.1601.49020.0_x64__8wekyb3d8bbwe\Calculator.exe.
VPNCheck Pro hangs in notification tray: Enable compatibility for Windows 8.
VPNCheck Pro is available for Windows at the moment.
When network drivers to these are enabled while VPNCheck is running, it might be detected as IP change. If you´re using a different kind than these two then VPNCheck might fail to function. For any trouble do create a ticket or contact directly.
Failure to register VPNCheck Pro: Make sure VPNCheck Pro is allowed to access the registry in Windows.
If a started application by VPNCheck Pro cannot be accessed by a third-party program, then run VPNCheck Pro from a location with proper permissions. For example Documents or Desktop.