Ok picked a server I know well or Locale and it is same line speed as 65 version.
The connectivity is NOT OK try 60 seconds x2 or more to fully establish a working link to even hit a website can open browser(S) and type speedtest.net not connect close reopen = repeat x4 on my connection yikes!!!
Version 65 was connect and bam it worked and worked right 100% of the time, so whatever is swapped from 65 up needs re-implemented especially forced DNS protection because this thing leaks from the get go unless you have the box ticked never had my DNS show 65 down since using.
For now it is good but going to be monitoring for DNS leaks like waiting on prey not feeling safe having to force!
Although I think 65 was coded to pre-enforce DNS leaks upon startup then people whined because they didn't setup right or just have crap connections losing connectivity which brought about the new UI with optional tick box now to use DNS leak protection.
I prefer IPLeak website runs a good test on it and run it more than once to be safe, for me it runs IP through about 80 to 100 different test cycles on load.
While using P2P, settings of the app being irrelevant as I've tried them all toggled on and off, it refuses to stay connected for more than perhaps 10-20 seconds. Sorry to say, I've dumped this and gone to using vanilla OpenVPN. No connection problems whatsoever. It doesn't have as many options, obviously, but at least it works. The PIA app use to work just fine on v5x. Ever since v6x came around though, fairly consistent issues. Perhaps the dev team should consider re-evaluating their approach to coding this software.
I'll keep an eye on the updates and try any new ones that look promising, but otherwise, I'll have to stick with vanilla OpenVPN.
Are we going to see any big changes in the upcoming version of the software v69? Last year a Beta version was released of v59, Will that be happening again?
OK well having been nagged for ages by my (apparently) working PIA instal which goes back 2-3 versions I'll risk it, not seeing numerous problem reports with the latest...
As a continuation to my last post, OpenVPN is giving me terrible speeds, even. Where I would normally get around 16mb/s down, I'm getting about 100kb/s. PIA was good to me in the start, giving me several mb/s, which is quite acceptable. This, however, is not. And I've tried on several different local servers, with different encryption settings, with no difference. Sorry to say, I'm going to have to look for a new VPN service unless this changes before my subscription ends.
As a continuation to my last post, OpenVPN is giving me terrible speeds, even. Where I would normally get around 16mb/s down, I'm getting about 100kb/s. PIA was good to me in the start, giving me several mb/s, which is quite acceptable. This, however, is not. And I've tried on several different local servers, with different encryption settings, with no difference. Sorry to say, I'm going to have to look for a new VPN service unless this changes before my subscription ends.
Until 2 days ago, I got identical speeds with PIA on or off. It's dropped from 50-80%.
I have a PC with 2 users. Administrator and Standard. When I install PIA on my Standard account and install it as administrator privileges, it installs the program and it's shortcuts in the Administrator account and I manually have to make shortcuts in Standard Account's desktop.
Well i cannot install the TAP Drivers on windows 10. PIA worked before and now it does not, keeps asking to reinstall TAP drivers. When i install PIA it says that TAP driver installation failed. Ive tried installing the OPenVPN TAP Drivers and it fails as well. I only have Windows Defender running.
I tried support but only got one message to tell me to do what i had already done half a dozen times. Any help would be appreiciated as PIA is now useless to me.
@JohnMarchant Are you running it as administrator? The TAP installation will always fail without proper privileges. Windows 10 is very.. annoying about privileges.
As another, albeit unlikely, reason, it could be that your ethernet/wifi device driver is corrupted or damaged in some way. If you've already tried explicitly running as admin and it didn't work, try re-installing or updating your respective device driver(s).
Comments
The connectivity is NOT OK try 60 seconds x2 or more to fully establish a working link to even hit a website can open browser(S) and type speedtest.net not connect close reopen = repeat x4 on my connection yikes!!!
Version 65 was connect and bam it worked and worked right 100% of the time, so whatever is swapped from 65 up needs re-implemented especially forced DNS protection because this thing leaks from the get go unless you have the box ticked never had my DNS show 65 down since using.
For now it is good but going to be monitoring for DNS leaks like waiting on prey not feeling safe having to force!
Although I think 65 was coded to pre-enforce DNS leaks upon startup then people whined because they didn't setup right or just have crap connections losing connectivity which brought about the new UI with optional tick box now to use DNS leak protection.
I prefer IPLeak website runs a good test on it and run it more than once to be safe, for me it runs IP through about 80 to 100 different test cycles on load.
my speeds --- 87.13 mbps down / 89.03 mbps up
https://imgur.com/a/eIPb2
I'll keep an eye on the updates and try any new ones that look promising, but otherwise, I'll have to stick with vanilla OpenVPN.
Release Date: February 15, 2017
OK well having been nagged for ages by my (apparently) working PIA instal which goes back 2-3 versions I'll risk it, not seeing numerous problem reports with the latest...fwiw
https://www.virustotal.com/en-gb/file/250e2da386e3dad1fc83541cffdc56735f64b1713f066681cb1b7f2ebf59d089/analysis/
generic.ml
Adware.OutBrowse.Win32.74012
I tried support but only got one message to tell me to do what i had already done half a dozen times. Any help would be appreiciated as PIA is now useless to me.
As another, albeit unlikely, reason, it could be that your ethernet/wifi device driver is corrupted or damaged in some way. If you've already tried explicitly running as admin and it didn't work, try re-installing or updating your respective device driver(s).