New client installers v.44 (Win and OSX)

Here you go, everyone! :(|)

sha256 checksum:
 windows: 50601d99d6dd14cb21810a7f51684c322252e9135bd0211511d34c097c6a5b81
 osx: c9d8e657f4b49b1dd3dd0a28aed3ee96fa0ee819e8ff2e33c0047a39c2b2a786

Change log:
Update Thu Oct 07 2014 - v.44
   - Add a link on the sign in page that enables user to reset password.
   - Add a 'Connect Auto' to the menu of regions
   - Show region and IP in the tooltip after connected

Comments

  • edited October 2014
    As per the usual, here is a Dropbox copy of the installer for Windows.
    CRC32: 761371E5
    MD5: 6C66B0F8B41E80E29D7987473799D38D
    SHA-1: D49B0C188C1FE4F07C2A3D9B0924DAF2886807E2
    SHA-256: 50601D99D6DD14CB21810A7F51684C322252E9135BD0211511D34C097C6A5B81
    SHA-512: 6FD97A8CE54481C35BB330AD6665E9BCDCF9CE6730DF607040376F0D7E8A6BDC57FA3FB7FC85D6B7EF11B4F3B5E381470FA940483C27D1D3B8A3EC3197B0A839
    SHA3-256: CA87DD2EAAAEA063615D25972B5FD8DA8ABA2BC6C5EC99044BE59FFDB348B6A5
    SHA3-512: A79C46647973F49158299D987841AEC193C11138A099C7EA84F1ADD9800280F9280D65B7431F69A9208F3416B6200C974EF17EE6496240F3621AE315C5BD8508

  • @grh will do!  And as for @OmniNegro, thank you as usual!
  • I second what @grh said. But they forgot to put the version number in the file name again, lol.

    No matter though, I got it first time from PIA.

    Thanks, as always, to @OmniNegro for the archive.

    Off to install.
  • No need to thank me. Dropbox is free, and it does occasionally help. I am glad to keep a full archive of the last eight versions at current. Sometimes people want to try the older versions and see if they work better. I never had any trouble with any version, but there they are.
    My VPN Folder on Dropbox.
  • edited October 2014
    KYJelly, it's working fine on OS X Yosemite 10.10 GM by the way. I'm not using the PIA beta anymore. 
  • Thank you PIA and KYJelly,

    - still the version is not numbered, please

    Anyone else:
    - is the Kill Switch working properly and without a fault?
  • @Asguardian

    Awesome!


    Even though it's not numbered it will be the most updated version.  We found the root of the problem from the installer before and made sure this update and moving forward would always be the correct version.  Sorry for the inconvenience.
  • Sounds like a non-essential upgrade from v.43. 

    https://www.privateinternetaccess.com/forum/discussion/comment/17610/#Comment_17610

    Presumably the port forward enabled gateways are not marked in the menu of nodes still.
  • I don't really see any difference on the OSX version, though I think the server list might have been reordered.  But I'm very thankful for updates and bug fixes.  Thank a ton! :)
  • No need to thank me. Dropbox is free, and it does occasionally help. I am glad to keep a full archive of the last eight versions at current. Sometimes people want to try the older versions and see if they work better. I never had any trouble with any version, but there they are.
    My VPN Folder
    i would like to thank you because i was looking for previous versions before v43 and i couldn't find them and i'm glad i did today
  • You are very welcome. Enjoy it.
  • KYJelly, what progress by PIA has been made on running the PIA program from one fixed location, due to the ruby instances running multiple times in the windows temporary directory?

    I heard PIA was working on this, and also saw that there was thread on this which required a hack of some sort to get around the problem.  An official way to bypass this ruby issue is much wanted by the customers!

  • KYJelly, what progress by PIA has been made on running the PIA program from one fixed location,

    This please. I have been waiting for some improvements there for years.
  • It seems every time I have to upgrade, I have to do the following to get the TAP driver working.
    1. Device manager tells me TAP driver needs me to restart for it to work so I restart.
    2. Device manager reports a failure to launch TAP driver code 10.
    3. I launch "Reinstall TAP driver" and after that, TAP driver is fixed.

    Is this normal?
  • It seems every time I have to upgrade, I have to do the following to get the TAP driver working.
    1. Device manager tells me TAP driver needs me to restart for it to work so I restart.
    2. Device manager reports a failure to launch TAP driver code 10.
    3. I launch "Reinstall TAP driver" and after that, TAP driver is fixed.

    Is this normal?
    Out of more than two dozen different versions of the client, I only ever had to restart twice. And I never had to do the reinstall. So no, I would say that is abnormal.
  • I'm on Windows 10 technical preview and while it installs fine and says it is connected, I have no internet access until I disconnect
  • I don't really see any difference on the OSX version, though I think the server list might have been reordered.  But I'm very thankful for updates and bug fixes.  Thank a ton! :)
    BIG DIFFERENCE on Mac OS X.. and THANK YOU VERY MUCH, Devs!

    1/ Menus have been cleaned up, connect & disconnect are up near the top where they should be, and the really big deal:

    2/ MouseOver tooltip that tells me EXACTLY what node I've connected to when I choose "Auto" or anything else.

    Before this I'd have to use iStat Menus + Terminal. This is really welcome 'at a glance' information. Thank you for the .44 update!


  • 1/ Menus have been cleaned up, connect & disconnect are up near the top where they should be
    I'm still using v43:

    image
  • Why does the new .44 PIA_Tray.exe run twice (in Task Manager)?  One instance uses>12% CPU

  • edited October 2014
    Still no response on the multiple instances of PIA_TRAY.EXE - one of which uses high CPU% and continually tries to close?  :(

    This is occurring ONLY with v.44

    ===============

    Also, what is the status of fixing the KILL SWITCH function????!!!!

    Just *kinda* serious issues, people .........................

  • edited October 2014
    Using the Win7 PIA v.44 client I'm noticing with consistency that the client does NOT automagically re-connect upon resuming from 'suspend'.  I.e., red icon in the tray with no attempts to reconnect, a right-click/connect required to continue...  (i5 desktop, 8 GB RAM machine, not a laptop).

    Anyone else seeing this issue?

    Edit:  My proofreading sucks!  Comment edited to read '...client does NOT automagically re-connect...'
    .
  • i find from hibernation with win7 the client will reconnect automatically, provided my firewall doesn't block it.

    I find a boot up to windows from post frequently will lead to the pia client refusing to connect (after I manually tell it to), until I go into local area connection and put all the ip settings to automatic.


    They really should fix this.  It isn't like they cant duplicate the error.

  • edited October 2014
    I'm having a lot of trouble with the latest installer. Everything seems to be OK, nice green icon, tells me I'm connected to North York... BUT... when I check my IP address using the IP Cloaking graphic from PIA, my connection is shown as coming from my actual location  - which clearly is not what I want.

    The worst thing is that PIA happily shows a green icon when it is in fact not working!!

    Now, I've had this problem before and usually it's some TAP driver problem. So I reinstall the driver and then things are OK. But not this time. Now I can't get the VPN running - have tried uninstalling, reinstalling, rebooting - no luck.

    I would love to be able to confirm which version of PIA I'm using, but of course PIA loves to keep this a big secret, so all I can say it's the one that shows region and IP..... except that of course those bits of information are WRONG.

    Edited to add: running Windows 8.1 64-bit
    2nd edit: Managed to get it running now. Turns out that despite uninstalling, the TAP driver was still there. I went to Device Manager and removed it, as well as the driver software. Then reinstalled PIA, and now it's running. But I still say PIA tray icon should NOT show green when VPN is not actually connected.
  • edited October 2014
    If it found and bound to a TAP driver, then it probably thought it was working as expected. Did you by any chance have OpenVPN installed at some point? I could swear they installed something similar but renamed from what PIA has as the TAP driver, and perhaps PIA was using that.

    Two things to mention, there is a .45 client out now, and you should probably update. Expect to have to manually reinstall the TAP driver because it has already given you problems for some unknown reason though. Second, you may want to disregard the web interface of the "IP Cloaking" thing from PIA and also the color of the tray icon for the program. Just use this. It will work much better and give you actual details as of the moment you use it.
    (And I am told that despite being given for Windows 7, that it will also work for Windows 8. One way to be certain.)
    PIA Information Tool.
Sign In or Register to comment.