I'm having the same issue with my Mid-2012 MacBook Pro (Retina), PGP version 10.3.0. At lease I assume it is the same problem - the symptoms sound the same.
I was unable to edit the table for the TECH206300 page as requested.
As a side not to others like turn1200, there is a good chance don't need to totally re-image a broken system. Most likely you only need to rewrite the MBR on the drive back to Apple's default.
There are a couple of ways to do this - my choice is to use the command line. First I reset the NVRAM (just for good messure), then boot into the recovery partition, launch the terminal window and use fdisk's -u flag to update the MBR (you might also have to set the bootable flag with fdisk if the partition is not marked as bootable).
I would be very interested in Symantec's most current option about this - we are ramping up our deployment and may need to rethink our approach if this continues to be an issue.