File Share Encryption

 View Only
  • 1.  PGP WDE for Mac Problem

    Posted Nov 21, 2011 06:20 PM

    I recently went to update itunes on november 6th 2011.  Now my computer wont work at all and the technicians at mac say they have to wipe the whole drive.  I have had a similar issue a year ago when updating OSX as it interferes with PGP WDE for mac.  Is there a solution that can save me having to wipe the whole drive?



  • 2.  RE: PGP WDE for Mac Problem

    Posted Nov 21, 2011 07:34 PM

    Installing iTunes should not have been a problem with your PGP usage.  However, if your current problem is that you are not now able to boot, you can use the Knowledge Base Article to decrypt your disk. 



  • 3.  RE: PGP WDE for Mac Problem

    Posted Nov 30, 2011 04:59 PM

    This article may explains the issue.

    "Symantec strongly recommends that all customers install the Apple OSX 10.6.5 update as soon as possible by following the steps in the Detail section below. This will prevent the accidental installation of 10.6.5 when the Software Update mechanism is used to upgrade other Apple products, such as iTunes or Safari."

    http://www.symantec.com/business/support/index?page=answerlink&url=http%3A%2F%2Fwww.symantec.com%2Fbusiness%2Fsupport%2Findex%3Fpage%3Dcontent%26id%3DTECH149998%26actp%3Dsearch%26viewlocale%3Den_US&answerid=16777216&searchid=1322690107520



  • 4.  RE: PGP WDE for Mac Problem

    Posted Dec 02, 2011 11:21 AM

    Thanks for the help Julian. I think it's important to note that you were on the right track with this.

    THe problem is, that if you follow the steps in the above listed article. You will still run into problems with the 10.6.8 update (which also includes all patches from all the previous updates as well). Where you will have this problem booting again.

    That article really should be deprecated. I will request to have it expired.  Customers are now recommended to upgrade their PGP Desktop release to 10.1.2 Build 9 or newer. See this KB article here which should fix the problem permanently (the above listed KBA is a workaround)

    http://www.symantec.com/docs/TECH16322