File Share Encryption

I'm currently using a perpetually licensed PGP Desktop 10.2.1 on my Windows 7 machine.  My purchase was back when I did so as a Symantec employee, but the registration numbers I have available are not being accepted by fileconnect.  Is there some way that I can upgrade to a Win 10 compatible version?

Tom,

The license is perpetual, but the support contract is what covers the updates/upgrades.  You may be able to contact Customer Care to see about updating the serial number, but I don't think they will be able to without a support contract in place.

Alternatively, you can get a trialware version for the latest product here:
https://buy.symantec.com/estore/clp/freetrials

Thanks for the response.  I was hoping that this would be considered as a minor update, that would be available for this situation.  I'm only crawling towards Win 10, but wanting to be prepared. 

On my computer using PGP WDE, Windows 10 check is showing PGP incompatibility.  But on this machine, using Bitlocker, the Windows 10 check does not show any incompatibility.  So, I may wait until upgrading to Win 10, and see how it all works for me.

My current license, shows all PGP Desktop components, except NetShare, as enabled.  Which version of Symantec Desktop is the similar product?  If there is a Trial version of it, I may want to give it a try.

The SKU is now common across both encryption products, Symantec Endpoint Encryption, and Symantec Encryption Desktop.  You basically get your choice of hich product to use.

I believe that the version you have is 'PGP Desktop - Professional' edition.  In the current iteration, the trialware license features a full-functioned client, even though it says you will be downloading a trial for Symantec Desktop Email Encryption (which is still the same client as Symantec Encryption Desktop, formerly PGP Desktop).

I decided to give the Trial a try.  This required me to log into my Sym account, and led to my being able to only download the Corporate software for various operating systems.  I downloaded it and installed it.  The install accepted my perpetual licensing of the prior installation.   My email now works fine on all incoming email, encrypted or not.  Outgoing email is fine if there is no key to encrypt to, but fails when I send the email to myself to test outgoing encryption:

:32:43.422: --- 15 Apr 2016, 11:32:43.422 ---
11:32:43.422: Connect to 'relay.pair.com', timeout 300 seconds.
11:32:44.424: >> 220 Tom-<deleted for privacy> PGP Universal service ready (proxied server greeted us with: 220 relay01.pair.com ESMTP Postfix)
11:32:44.424: << EHLO [192.168.0.10]
11:32:44.424: >> 250-Tom-XPS-<deleted for privacy>
11:32:44.424: >> 250-STARTTLS
11:32:44.424: >> 250-8BITMIME
11:32:44.424: >> 250-DSN
11:32:44.424: >> 250 OVID
11:32:44.426: << MAIL FROM:<tom-<deleted for privacy>>
11:32:44.474: >> 250 2.1.0 Ok
11:32:44.474: << RCPT TO:<-<deleted for privacy>>
11:32:44.521: >> 250 2.1.5 Ok
11:32:44.521: << DATA
11:32:44.521: >> 354 Start mail input; end with <CRLF>.<CRLF>
11:32:44.536: >> 451 Encryption Desktop: Error processing message

All my email and pgp settings appear to be the same as on my other computer that is still using the earlier version, and working fine.  However, I am still requesting verification of my needed email settings for my email server at  pair.com.

PGP log shows the following, but only when I test outgoing encryption, my sending email to myself, and only when doing so from this updated install:

10:27:06 Email     Warning    Server relaylb.pair.com advertised STARTTLS support, but STARTTLS command failed
10:27:06 Email     Warning    STARTTLS negotiation with server failed
10:28:06 Email     Warning    Server relaylb.pair.com advertised STARTTLS support, but STARTTLS command failed
10:28:06 Email     Warning    STARTTLS negotiation with server failed
10:37:52 Email     Warning    Server relaylb.pair.com advertised STARTTLS support, but STARTTLS command failed
10:37:52 Email     Warning    STARTTLS negotiation with server failed