Endpoint Encryption

 View Only
Back to discussions
Expand all | Collapse all

Could not load string file – Error -11995 (PGP Desktop Corp 10.2.0 build 1672; win7 pro; 64-bit)

  • 1.  Could not load string file – Error -11995 (PGP Desktop Corp 10.2.0 build 1672; win7 pro; 64-bit)

    Posted Aug 03, 2011 08:32 AM

    Upon updating to 10.2.0, after reboot I got a dialog box about being unable to access

    C:\Program Files (x86)\Common Files\PGP Corporation\Strings\PGPwdesdk.en-US.str

     

    The file did exist. (14,006 bytes).

    File properties, Security tab : unable to display current owner

    Changing ownership to myself, an administrator, resulted in no dialog box upon reboot. However, that should not be necessary.

     

    Note that there is no pull-down for the new pgp 10.2.0 at

    http://www.symantec.com/business/support/index?page=selectProduct&previous=&productName=&productVersion=&productPlatform=&platformVersion=&summary=You+have+the+following+errors%3A-%0D%0A&prdName=PGP+Desktop+Corporate&prdNameId=59256&prdVersionId=&prdPlatformId=57408&prdPlatformVersion=&probdesc=Example%3A+I+cannot+activate+my+software%2CError+code+29004



  • 2.  RE: Could not load string file – Error -11995 (PGP Desktop Corp 10.2.0 build 1672; win7 pro; 64-bit)

    Posted Aug 18, 2011 12:20 PM

    The link that you posted does not work for me. Is it possible for you to post some specifics about your setup as well as a screenshot of the error?

    - Ben



  • 3.  RE: Could not load string file – Error -11995 (PGP Desktop Corp 10.2.0 build 1672; win7 pro; 64-bit)

    Posted Aug 19, 2011 01:29 PM

    Seems that  installation could not set up right security permissons.

    Do you have any security software or local\domain policy blocking this?

    Can you do a verbose installation again , with msiexec options, and send the logs?

    You may also want to take a look at the whole C: or C:\Program Files (x86) permissions inheritance, as well as your administrator permissons.

    Anyway is the first time i have heard about this issue. You already solved the issue...unless it's happening to other computers.

     

    Regards