#10.6 8 UPGRADE MAC OSX#

But it was designed to be, as a last resort, a fix to get you around the issue that one time.

The workaround of copying over the pgpboot.efi and replacing the boot.efi is an easy fix.

#10.6 8 UPGRADE MAC OSX#

You guys do realize that if you don't fix the root problem by updating your PGP Desktop code you will run into the same problem the next time that Mac OSx pushes out their next update right? Because the second workaround may fix problem now but will break PGP again after the next update most assuredly. * AS A LAST RESORT you can also boot off the mac osx cd and copy the pgpboot.efi over the boot.efi fileīut I would really recommended upgrading PGP if you are 10.0 anyways. I recommend 10.1.2 SP3 since that incorporates the latest fixes boot the mac in target disk mode and decrypt the disk there find the recovery cd used for the version of PGP Desktop that you have deployed and use that to boot the os and then decrypt from there before upgrading to 10.1 SP1 or newer. I will repeatedly state that you should NOT update your mac to 10.6.8 unless you are using PGP Desktop 10.1 10.1 SP1 or newer.Īs far as workarounds go if you are on older than 10.1.1 SP1 and cannot boot I see you having two options: Or else through your PGP Universal Server Now all updates are handled manually through the symantec licensing portal at: We are techically on 10.1 SP3 which addresses some known issues with machines that are encrypted with 64-bit kernels on mac osx 10.6 The 'check for updates' feature no longer functions with PGP Desktop 10.1 and newer. I don't have access to the right resources to confirm or deny just yet whether QA has tested the macosX update with PGP Desktop 10.1 Support is using pgp desktop 10.1.2 build 22 Support has tested the mac osx 10.6.8 update on a macbook pro with success booting the drive

10.6 8 upgrade