Version 1.3.1 Update screwed me beyond repair

PIA_Man

Latest update for Jul 10 totally screwed me beyond repair. I've tried everything short of resetting Windows.

"Can't connect on UDP port 8080. Trying alternate settings."
https://i.postimg.cc/s2RpPd5X/PIA-error.jpg

Not even previous versions will work now. Same error. I have two PC's and it did the exact same thing to both. Running 1.2.1 on my laptop as I don't use it much. Certainly won't be updating it.

I've uninstalled PIA, wiped old files/cleaned registry, reset network settings, reinstalled network drivers, reset firewall settings, reset network hardware, reset router settings, disabled HOSTS, flushed DNS, tried static and dynamic IP, tried multiple DNS servers, disabled Avast AV and firewalls, uninstalled any potentially conflicting apps, and rebooted before and after every step. I've simplified every known related setting on my system and in PIA. What a doozy.

Whatever this update did, it permanently disabled PIA on a deep level. I commend whatever trick this is, as it's the first time in all my life I've been officially stumped by a network or PC issue in general. Given that I've spent several hours on this now, it might be time to switch providers as I don't feel like resetting Windows just to do a PIA update.


EDIT: Still no luck. Switching to ExpressVPN or NordVPN going forward.
PIA never even made contact with me. Poor product and service.

p6354661

1.3.1 was fine for me... now 1.3.2 destroys my VPN... I couldn't connect.
rolling back to 1.3.1 works.

[Deleted User]

Try turning off the 'Try Alternate Settings" option in the Settings/Option. It got stuck when it found the default port blocked.

PIA_Man

Still haven't got it working. Doesn't matter what version I try now.

Tried virtually every combination of settings in PIA (including unchecking Try Alternate Settings) and everywhere else on my PC. I'm scared to do a Windows reset because it's a lot of work to get everything back to normal, and who knows what else might get messed up in the process. Nothing is broken except for PIA so it's not worth the risk to me.

Updated my router to open-source 3rd party firmware for advanced features. Great firmware upgrade but didn't fix PIA.

bzzzt

Same here. Reinstalled adapter, uninstalled/reinstalled, etc.

 debug logs:
[2019-07-12 13:43:55.119][05b0][openvpn.mgmt][connection.cpp:814][debug] >FATAL:WARNING: Failed running command (--up/--down): returned error code 1
[2019-07-12 13:43:55.119][05b0][openvpn.stdout][connection.cpp:791][debug] Fri Jul 12 08:43:54 2019 us=937000 MANAGEMENT: Client disconnected
[2019-07-12 13:43:55.119][05b0][openvpn.stdout][connection.cpp:791][debug] Fri Jul 12 08:43:54 2019 us=937000 WARNING: Failed running command (--up/--down): returned error code 1

p8466672

update 1.3.2 not working, I rolled back to 1.1.1 that I had lying around, things are now working again.

Windows 10 version 1903

rcalinjageman

Same.  Rolled back to 1.3.0 and could finally connect.  With 1.3.1 I was getting system crashes; with 1.3.2 the crashes stopped but would not connect with or without 'alternate settings' checked.  Now back to 1.3.0 and everything is ok...

Omnibus_IV

You guys need to start adding what OS you are using. Just to say ver x.x does not wok is too ambitious. Version would help PIA try and figure out what is happening.

Just for the record, I have Win8.1 and running PIA 1.3.2 and am having no issues. I use the Comodo firewall and the driver version on the ethernet adapter is 9.23.3.601. The TAP version is 0901.

nelau602

Running into the same issue since I upgraded to 1.3.2  (build 02865) and Im using Windows 7 Ultimate.
Going to try and rollback to 1.3.0 and hopefully that will work.

Hoping they will fix this issue soon.

majormalfunction

This is interesting as I've had the same issue in the last couple of days with not being able to connect to any servers. Found a v1.02 installer and rolled back to it after reading what some of you have tried. All is working once again with no other changes. Windows 10 64bit Enterprise here. I had pretty much exhausted other options like the rest of you. My iPhone 8+ on 12.1.1 PIA client is working fine on the same lan. Just tested it. Going to dig out both my laptops next.

bgoreconsultinginc

W7 Professional 64. Update 1.3.2 broke my internet. I can ping 8.8.8.8 via command prompt window, 30ms delay via PIA autoconnect to FL. But Firefox 68.0, Chrome (whatever), and Thunderbird cannot access the interenet. Tried various settings in PIA, paused Avast (can ping with or without), nope, nada. It also takes much longer to connect, about 15-20 seconds on autoconnect. ? I'm OK on networking, but advanced beginner. Not expert. What do I do???  How do I rollback? Use restore point maybe? If I have a reent one. Maybe uninstall, but where do I find 1.3.1?

bgoreconsultinginc

OK, found previous versions, uninstalled 1.3.2, restarted, installed 1.3.1, still broke. Seems to be only browsers. IE, too (ugh--had to try). You broke something in windows, I think. Will see if other progs can phone home. But probably going to rollback windows, reinstall 1.3.1, keep trying. When I get it working, I will likely cancel my account. I can't afford this stupidity on your part. User for at least 6(?) years.

Floggin

Had this issue today, found this thread. I reinstalled Network Adapter and it fixed this problem. It's found under the Help section in settings. Hope this works for you. 

bgoreconsultinginc

I uninstalled v 1.3.1, and used a restore point in windows from a week ago. Checking the "software affected" (or whatever it's called) at that restore point first, it showed v 1.2.1 then. So after restore, I downloaded and installed v 1.2.1. Now it works. I work for myself, run an ecommerce website out of my home office, and do daily banking online, multiple accounts, multiple credit card sites, paypal, etc. And generate multiple shipping lables today. And use lastpass. Today, I was DOA for hours, and had no choice but to login to lastpass naked(!) to get anything done. Which means, sending my MASTER PASSWORD over the internet without VPN. So prudence dictates I now have to change EVERY. SINGLE. PASSWORD. I. USED. TODAY. Starting with my master password. Aboput to do all that right now. PIA just cost me about 6 hours of labor. And at my normal rate that would have paid for oh, 15 years of PIA. I am now looking for a new VPN service, and will cancel PIA. You just lost a customer of over 6 years. Suggestion: offer an immediate "undo" option, and include an automatic restore point prompt prior to installing. The rest of you, have fun! It was nice while it lasted.

Omnibus_IV

You do realize that once you leave the PIA server you data is naked, right? The only difference is your IP address is masked by the VPN Server's generated public IP address. However, anyone who wants to steal data can do so. The only time this might not be true is if you have a VPN account with the end server, such as a corporate server.

I do hope you can resolve this issue. Good luck.

PIA_Man

"You guys need to start adding what OS you are using."
We're in the Windows forum. Safe to assume we're on Windows. I'm talking about resetting so safe to assume I'm on 10.
In any case, it's their job to test new releases properly. No one even replied to me when trying to contact them. I would've gladly provided all kinds of details had they engaged. Poor product and poor service. PIA did break Windows in my case somehow. Hard to believe they would make major changes without testing properly or providing precautionary measures.

I can totally feel the pain of bgoreconsultinginc as it also cost me many hours of headaches. I ended up resetting Windows which is no easy task when you have dozens of heavily customized apps installed and tons of personalized settings. I'm still not completely back to normal. My time is worth a lot so I feel I've earned a free year of PIA. But as bgoreconsultinginc pointed out, I'll be switching VPN services when my subscription expires. Unless I hear back from PIA and am offered compensation. Then I might consider staying. But certainly not without acknowledgement.

Interestingly, I never reset my 2nd PC which had the exact same issue. I just left it unprotected since Jul 11. Once I noticed 1.3.3 was released, I uninstalled PIA on that PC, installed 1.3.3 from scratch and it worked instantly. So they've obviously fixed the bug in 1.3.3... finally. It only took them a week and several new versions.

Also interesting (and momentarily enraging) is that the other day I logged onto PIA (primary PC) and my screens went black and the PC spontaneously rebooted. Very strange. When I booted back up, I was unable to connect to PIA... getting the same errors that plagued me last week -- AFTER I reset Windows. I nearly pulled my hair out and smashed my keyboard. I wasn't very hopeful but I uninstalled PIA and reinstalled, and to my surprise it was working again, thank God.

Omnibus_IV

Not safe to assume since a few have already stated they are on Windows 7 and like I said, I am on Windows 8.1. So for the benefit of the PIA service guys, stating what version of Windows one is  using is beneficial.

Now that I have mentioned it, I just did the upgrade to V.1.3.3 and are showing no issues.

p8466672

Just downloaded installed V.1.3.3 -- everything seems fine.

Windows 10 64 bit 1903