File Share Encryption

I am very new to Mac (just recently bought my first MacBook) and have been using PGP(-WDE) for Win already for few years (no problems).

following scenario:

1) configuration of Boot Camp, installation of Win7-64bit on Boot Camp (booting into both Mac and Win works fine)
2) Deinstallation of PGP on Mac (by dragging Application folder into trash box)
3) installation of PGP on Win (PGP Win64bit version - installation worked fine - no encryption on Win done)
4) installation of PGP on Mac
5) encryption of whole HDD with PGP-WDE from Mac OS
6) bootguard/logging in for Mac works fine!
7) after restart/switching to boot into bootcamp/windows:  first the know black screen appears with "loading bootguard etc" appears,
then for a very short moment the nown PGP windows bootguard screen but afterwards only the black screen with blinking cursor in the upper left corner.

system: Mac OS 10.6.6, Core i7 CPU, PGP 10.1.1

any suggestions?

#2 above doesn't work.  You MUST run the uninstaller. 

I don't use bootcamp (too many problems with WDE), but from previous posts, I suspect you'll need to decrypt the drive, uninstall PGP properly in both environments, de-instrument the disk (there's instructions in the knowledge base), reinstall PGP (mac first, then windows), then re-encrypt on the mac side.

ok thx a lot!

I will try that (it will take some time....)

Once you've decrypted, if everyting works, I'd also suggest making a good clone as a fallback :-)

one question: what you mean with "de-instrumenting" the disk? removing/reinstalling bootcamp with windows?

I am very new to mac and not very familar yet with this system

there are no important data yet on the Mac, but I will use timemachine (?) for a complete backup after decrypting

the system decrpyted w/o problems and I can boot again normally into both Mac and bootcamp/windows.

I have search in the (PGP)forum about de-instrumenting and found only the commands  "pgpwde --enum" for the terminals in both mac and windows.

screenshots are attached of the terminals - I have no idea how to go further about "re-instrumenting"

I would proceed in the following way:

1) uninstall PGP on windows (with standard windows-deinstallation procedure)

2) boot into Mac and uninstall PGP using the "uninstall" button under the  "about" menu

3) reboot again and starting installation on first Mac and then on Win/Bootcamp

4) encrypt HDD from PGP-mac

 

however in the knowledgebase it is decribed (under "Install PGP Desktop with an established Boot Camp installation") that PGP should be first installed in windows, then in Mac (?)

https://pgp.custhelp.com/app/answers/detail/a_id/1697

would be happy for any suggestions!

 

kind regards, Stork

This Knowledge Base Article should help regarding the uninstrument command.

Dear Tom,

thx a lot for the link!  I still dont understand the term "uninstrument" (I am native German speaker).

after decryption I dont get bootguard anymore in both Mac and Windows/Bootcamp.

After checking with pgpwde --status   the HDD is shown decrypted. "Disk 0 is not instrumented by bootguard"

so the systems looks like before starting WDE on both bootcamp and Mac HDD.

what would be the correct order of PGP installation - first on Mac or first on Bootcamp? (encryption will be done from Mac)

 

thanks a lot, kind regards, Stork

I will try - after purchasing an external HDD as backup-solution - re-encryption again (1st install on Win, 2nd install & encryption on Mac) and see what happens. if it fails only the order of installation can be changed...

I´ve spent the last days with several rounds of installation/encryption/booting/decryption using the possible orders of installation

(always encrypting from Mac;  PGP installation starting in Bootcamp then in Mac and also vice versa installation)

Result was always the same: bootloader/access is normal in Mac but in BootCamp/Win7 PGP-bootloader appears only for short time followed by black screen.

Decrypting the HDD afterwards worked always w/o problems, now I am currently decrypting again (each round about 7 hrs), the disk shows not encrypted checking in terminal window.

So far after each decryption the bootloaders in both systems did not show up, so no requirement for uninstrumenting (according to https://pgp.custhelp.com/app/answers/detail/a_id/608)

I am stuck here because I dont want neither to use FileVault on Mac (no source code published) nor to use BitLocker on Windows (same with sourcecode and no idea if it works with bootcamp)  - PGP-WDE should encrypt the whole HDD (according to user manual also with BootCamp).

I would even start "from scratch" - removing windows/bootcamp and start with installation of boot-camp --> install PGP on Mac --> install of Win on Bootcamp --> PGPinstall on Win --> encryption of HDD from PGP-Mac - if it will work (?)

question: can somebody share her/his positive experience using PGP-WDE with bootcamp and how it worked? Any chance to proceed?

kind regards, Stork

I started everything from the beginning with same result, where I have detected some issue via terminal - here the workflow:

uninstalling PGP in both OSs --> removal of bootcamp (incl Win7-64bit) --> reboot --> install bootcamp (without Win) --> install MacPGP --> install Win7-64bit on bootcamp --> install bootcamp drivers --> install WinPGP --> encrypting of HDD from MacPGP.

results: normal PGP-bootloader in Mac, PGP-bootloader in Win appears only for short time followed by black screen with cursor in the upper-left corner.

on this link I found some Terminal-comands to check situation of the disk (http://forum.pgp.com/t5/PGP-Whole-Disk-Encryption-for/WDE-Error-12293-Instrumenting-Disk-with-Boot-Camp/td-p/35242)

bootcamp is the 4th partition, so everything should be fine...

 analysis via Mac-terminal was done after PGP-WDE from Mac - it finds a "suspicious MBR at sector 0" (see below) - how to fix this?

would be very happy to receive any helpfuld comments, kind regards, Stork

 

(booting into Mac is normal, decryption works also fine - this was tested too many times already...)

 

********s-MacBook-Pro:~ ********$ diskutil list

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk0

   1:                        EFI                         209.7 MB   disk0s1

   2:                  Apple_HFS Macintosh HD            374.0 GB   disk0s2

   3:                 Apple_Boot Boot OSX                134.2 MB   disk0s3

   4:       Microsoft Basic Data BOOTCAMP                125.8 GB   disk0s4

A-Ss-MacBook-Pro:~ ********$ sudo gpt -r show disk0

gpt show: disk0: Suspicious MBR at sector 0

      start       size  index  contents

          0          1         MBR

          1          1         Pri GPT header

          2         16         Pri GPT table

         18         22        

         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

     409640  730468736      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  730878376     262144      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

  731140520       1624        

  731142144  245630976      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976773120         31        

  976773151         16         Sec GPT table

  976773167          1         Sec GPT header

*******s-MacBook-Pro:~ *******$ sudo fdisk /dev/disk0

Disk: /dev/disk0      geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

         Starting       Ending

 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

------------------------------------------------------------------------

 1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>

 2: AF 1023 254  63 - 1023 254  63 [    409640 -  730468736] HFS+       

 3: AB  255 254  63 -  255 254  63 [ 730878376 -     262144] Darwin Boot

*4: 07 1023 254  63 - 1023 254  63 [ 731142144 -  245630976] HPFS/QNX/AUX

*****s-MacBook-Pro:~ ******$

I found in others forums that the "suspicious MBR" is normal in case BootCamp is installed (?)

I have decided to start from very beginning with new installation of MacOS - result was the same as above - here the order of events:

1.new installation of Mac OX 10.6.6
2.Installation of Bootcamp
3.installation of Mac-PGP
4.Installation of Win-64bit on Bootcamp
5. Installation of BootCamp drivers
6. Installation of Win-PGP
7.encryption of HDD from Mac-PGP  (same procedure as described in manual -  
accept they dont tell anything about the bootcamp drivers...?)

result: booting into MacOS works fine, in case of Windows the bootguard  
appears only shortly, than black screen...

I am really stuck now and would kindly ask any helpful suggestions...  below again the results from the terminal

kind regards, Stork

 

analyis via terminal was done after encryption of HDD from Mac-PGP:

++++++-MacBook-Pro:~ ++++++$ diskutil list

/dev/disk0

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *500.1 GB   disk0

   1:                        EFI                         209.7 MB   disk0s1

   2:                  Apple_HFS Macintosh HD            369.0 GB   disk0s2

   3:                 Apple_Boot Boot OSX                134.2 MB   disk0s3

   4:       Microsoft Basic Data BOOTCAMP                130.8 GB   disk0s4

+++++s-MacBook-Pro:~ +++++$ sudo gpt -r show disk0

Password:

gpt show: disk0: Suspicious MBR at sector 0

      start       size  index  contents

          0          1         MBR

          1          1         Pri GPT header

          2         16         Pri GPT table

         18         22        

         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

     409640  720703104      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

  721112744     262144      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

  721374888        344        

  721375232  255397888      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976773120         31        

  976773151         16         Sec GPT table

  976773167          1         Sec GPT header

++++s-MacBook-Pro:~ +++++$ sudo fdisk /dev/disk0

Disk: /dev/disk0      geometry: 60801/255/63 [976773168 sectors]

Signature: 0xAA55

         Starting       Ending

 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]

------------------------------------------------------------------------

 1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>

 2: AF 1023 254  63 - 1023 254  63 [    409640 -  720703104] HFS+       

 3: AB  255 254  63 -  255 254  63 [ 721112744 -     262144] Darwin Boot

*4: 07 1023 254  63 - 1023 254  63 [ 721375232 -  255397888] HPFS/QNX/AUX

+++++++++-MacBook-Pro:~ +++++++++$

When you did the reinstall, did you boot from the install DVD, run disk utility and repartition (not just erase) the drive first?

reinstall was done by booting from DVD, erasing and installing, not repartition...

thx for the hint, I did not know that this is criticial, maybe i will try over weekend again

Erasing may leave residual PGP instrumentation on the disk - repartitioning removes it completely.  Make sure you choose GPT/GUID partition when you do.

Good luck!

I have repartitioned the HDD (removed BootCamp/booted from Mac-OS-DVD/disk utility - repartioning as MacOS-extended journaled format - in total only 1 partition as GPT, then even "erased" this new partition again to be sure), installed MacOS/Bootcamp/Mac-PGP/Win7-64bit on bootcamp/Win-PGP on Win7/encrypted HDD via Mac-PGP

result the same as before: booting in Mac fine via PGP-bootloader, in Win the PGP-bootloader window appears only shorty followed by black screen.

I have now decrypted the HDD overnight again

final questions:

1) I have used PGP 10.1.1 64bit for the Win7-64bit installation - however PGP is automatically installed under the (x86) program files folder - is that ok?

2) would it make sense to install 32bit PGP on Win7-64bit (if this helps) - however in the previous forum from pgp.com it was not recommended (but not under bootcamp)?

3) I still need to use windows with my mac - which virtualization softwares would you recommend (Virtualbox, Parallels, VMware fusion) in case I would not succeed with bootcamp

4) my MacBook pro 13" is "brand new" with the new Core-i7 CPU - are there any known issues in context with PGP?

still have the hope for a stupid mistake....(as mentioned in the beginning of this thread I am very new to Mac, hopefully the problem is with partioning only)

kind regards, Stork

(below the output of terminal after decryption):

diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            379.0 GB   disk0s2
   3:       Microsoft Basic Data BOOTCAMP                120.8 GB   disk0s4
Aloiss-MacBook-Pro:~ ++++++$ sudo gpt -r show disk0
Password:
gpt show: disk0: Suspicious MBR at sector 0
      start       size  index  contents
          0          1         MBR
          1          1         Pri GPT header
          2         16         Pri GPT table
         18         22         
         40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640  740234368      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
  740644008     263000         
  740907008  235866112      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  976773120         31         
  976773151         16         Sec GPT table
  976773167          1         Sec GPT header

1) This is where 64 bit PGP installs.

2) I don't believe 32 bit PGP will install on 64 bit Windows.  This is not supported.

 

4) I believe the only problem with the i core processors is that eTokens would not work for WDE on the boot drive; I think it was PGP 10.1 or 10.0.3 that corrected this problem.

Dear Tom,

thx a lot for your answers, I am still not giving up and hope for a solutions of this issue (would be nice if somebody with same machine could report her/his experience with PGP-WDE + BootCamp)

 

kind regards, Stork

Hi, i read your posts, as i have almost identical problem as you... 

I'm IT engineer... i have MacBook Pro (2011) 15" Core i7 , i tried almost same steps as you've done and still same ( i mean bootguard boots, but it dims after that and then only blinking cursor shows)

I have done all the official steps from pgp site step and still same...

Did you try older versions o PGP ? maybe there is a problem with this particular version (10.1.1) ?

I can help you by doing some steps on my side, as i'm stuck as well and i can't work without encypted hard drive, too many important data on it  ( i travel with my macbook pro a lot ) 

 

I start to wonder that maybe PGP for windows have some limitations if it comes to hard drive size ( i mean how far from the beginning of HD boot camp partition is... but when i tried to install windows as a first partition it behave little different but wasn't working as well (it freezes it self on boot guard bitmap screen))

Let me know if you interested with my help...

 

Regards.

Artur

ps.Sorry for my english... it's not my origin language...

Hi Artur,

thx for your feedback and for sharing same/similar experience!!!

in other pages on this forum posts people are successfully reporting the upgrading to Mac OS 10.6.7 together with PGP-WDE and bootcamp, so it seems that our problem is related to the very new MacBook 2011...but I have no idea about this (I was using WinXP SP2 with PGP-WDE so far, always latest version and switched very recently to my new MacBook Pro 2011 with MacOS 10.6.6 & Win7-64bit (Bootcamp) - I did not try PGP 10.0.2 which I downloaded some time ago for Mac (there were problems reported as far as I remember)

I would be happy for any help - also from Symantec/PGP as now we are two with similar issue...

 

kind regards, Stork

Hi Stork... Yesterday i've made test on my mac mini on 160GB hard drive ( with two partitions half for windows, half for mac) everything was done using this tutorial https://pgp.custhelp.com/app/answers/detail/a_id/1697/~/using-boot-camp-with-pgp-wde and it works fine from the beginning i can boot to windows and macos with encrypted drive !!! The same procedure fail on my macbook pro 2011 so there is definitelly problem with macbooks pro 2011 family... (maybe with some paticular processor...) The only thing that could be important here is the hard drive size... Yours is 500 GB mine is 750GB on mac mini i tried 160GB, maybe there is some limitations to the harddrive size ( i know that windows have several limitations if it comes to booting from partitions... MBR is quite old technology... ) Did you write anything regarding this issue to PGP technical support? Maybe we should notify them ? Kind regards. Artur.

Dear Artur,

thx for your report - I could try with a smaller BootCamp partition or also 1:1 size distribution, but each circle will take 8 hrs of encryption (same for decryption), not sure that this would deliver a solution as the partition size should not be the limiting factor to use PGP-WDE with bootcamp

I have no idea where to post technical issues on pgp.com - there is an immediate retransfer to the homepage of symantec, where it is unclear at which place to put this technical request - it would be nice if you could make an effort in this direction!  No idea how to go further without official statement from symantec..

Hi, again :) You don't need to encrypt entire hard drive... You can start encryption on mac and the click pause, restart the computer and try to boot windows. On my mac mini it works perefctly even when i pause at 1% of encryption process... In case when windows won't boot up you can then quickly decrypt the harddrive and try different setup... I think that will speed up tests :) Regards Artur Ps. Later today or tomorrow i will try to find some help on symantec page , i mean email to technical support, or i will try to phone them up.

thx for your help and the very useful hints!

I will try in the next days with different sizes of bootcamp (50Gb, 100Gb, 1:1 and more) and see what will happen, it will take some time!

 

regards, Stork

...with the same result: PGP-bootloader on Windows-BootCamp appears shortly and dims out, followed by black screen, booting with PGP-bootloader in MacOS is normal.

Encryption was done till 1% status (thx for the hint which saves enormous time!), followed by trying booting, and again decryption

am not sure the size of the partition plays a role here but who knows...

kind regards, Stork

...failed as well as all trials before (could not resist checking this till late night yesterday) - always same result: Win-PGP bootloader "comes & goes".

Procedure of installation was same as described in this link (  https://pgp.custhelp.com/app/answers/detail/a_id/1697/~/using-boot-camp-with-pgp-wde )

best regards, Stork

I've got the exact same problem, just posted over at the other thread about problems with the new 2011 Macbook Pro (sandy bridge model).

Hi guys! Yesterday i tried to replace my 750GB hard drive in my macbook 2011 to 160GB and i can confirm that problem still persist. Same blinking cursor again... Somebody on the other forums suggested that the problem with pgp for windows is that it doesn't support 4KB sectors as modern disk have. But it's not a case here, so i think that pgp is not compatible with sandy bridge architecture from some reasons... We have to wait, and there is nothing to do with this problem now until pgp (symantec) will not fix this problem in next version. Regards. Artur.

I wanted you all to know. This is a known issue with the latest version of Mac OSx 10.6.6 on these new Macbook Pro's and Bootcamp with Windows 7.

There is a patch that is currently under development and testing that should be able to resolve this problem with getting the blinking cursor while trying to boot the Windows side of of the encrypted disk.

This will be addressed in a service pack of PGP Desktop which should be out sometime this month. But this fix will also be addressed in our latest product release of PGP Desktop which should be out sometime in Q3 of this year.

If you are interested in getting signed up for the service pack to fix this. Please contact Symantec support and we will get you on a list for this bug.

EDIT: This service pack release has been delayed, due to some unforseen issues. This should be address with PGP Desktop 10.1.2 SP3. However, I do not have an exact release date for that service pack yet to date.

Hi.

 

How can i sign in for this service pack ?

Can you give me link to exact location where i should go to do this ?

 

Regards.

Artur.

You will need to call Symantec Support at 1(800) 342-0652. Support has to provide you access. Since this service pack won't be available till sometime by the end of the month. They won't be able to provide you access yet. But one the service pack comes available, we can provide you download access by calling support.

What I would do at this point is, what it out two weeks and then call support to see where we are with the service pack.

Thanks,

Ben

This is a known issue.

It was supposed to come out in PGP Desktop 10.1.2 SP2. However, there was some unforseen issues (a much larger problem) that causes customers to not be able to boot their mac's at all if they are on the new 64-bit kernel and the Intel Sandy Bridge CPU architecture. Due to this unforseen problem, this, among other things has delayed the release of our service pack 3 (PGP Desktop 10.1.2 SP3).

The ETA on this service pack could be sometime middle of this month. I'm sorry that I can't give you a more solid release date. But this date has been pushed back from the original ETA which was the end of May.

I apologize for this delay, if you have not done so already. I would encourage you to submit a support case online at https://mysupport.symantec.com

If you are bronze support, please contact support at (800) 342-0652 and ask them to log a case for you. If they tell you that you are not entitled to supoprt. Ask them to please log an exception since you need the service pack for your software to work. They have been told to let customers through.  If you continue to have problems, then leave a comment on here and I will try my best to get back to you ASAP with more information and a case#. This way, when the service pack is released, you will be notified.

Update: The fix has been released. please contact support at (800) 342-0652 and tell them that you are requesting a PGP Desktop 10.1.2 SP3 for Mac.

Unfortunately if you have Bronze support you cannot create a support ticket. You will need to contact one of the PGP techs (there is a couple on this thread you can message above) and they will have to generate a ticket for you. I have yet to receive the link to download it though.

You should be able to call support at (800) 342-0652 and let them know that you need an "entitlement exception" and that you want a case created since you need to obtain a PGP Desktop Service pack. if they are unable to help you, request to speak to their manager.  They have been told to let customers through that aren't entitled to live support, if they are requesting a service pack for these issues.

thanks for all the help - I have got the latest versions!

kind regards, Stork

Why shall I call support to download a Software Update? I did call the number above and they did not have a clue on how to help.

Why haven't you posted the update on the licensing portal which, by the way, does not distinguish between service packs since it keeps mentioning just a "10.1.2" dated from April?

If there's a new PGP version available which we need to have installed in order to fix all issues with Mac OS X 10.6.8, please post it on Licensing Portal!

Because service packs are seperate from general releases. To download the service pack, you need to request access to the download through our PDC portal. This is the Patch Distribution Center site (used to be LEMS).

Send me a PM with your details such as:

- Company Name

- Email address

- Order number

Then i can look you up in our system and provide you access to the download.  Symantec does it this way for two reasons:

- Crypto export laws require that we have a way to track who downloads the software and when

- Service packs do require a request through support because they generally like to keep track of who is using them since they aren't a "regular" release of the product and sometimes will contain fixes that are only addressed in that version, etc.

I hope that helps clear things up a little bit

Great, I'm glad to hear that we got you updated and hopefully working

MacBook Pro, 15"

2.8 Ghz Core Duo 2

8GB RAM

750GB Drive

 

Mac OS-X 10.6.6

PGP WDE 10.1.2 (Build 9) Enterprise License 

 

1. Installed MAC OS-X - now at 10.6.6

2. Installed PGP WDE 10.1.2 (Build 9) (no encryption yet)

3. Created Bootcamp parition

4. All drivers installed

5. Installed PGP WDE 10.1.2 (Build 9) on Bootcamp (No encryption yet)

 

 

Dual-boot working great back and forth no problem.  Can see both partitions/boot options if I hold down ALT during boot.  Everything perfect.

 

So I boot into MAC OS-X

1. Encrypt drive (Disk0 - no partitions available to encrypt - only option is entire drive).

2. reboot after finished

3. MAC Bootguard shows up - put passpshrase in works great

4. Reboot back into MAC OS-X second time still good

5. Reboot into windows

6. Windows Bootguard shows up - boots into windows perfectly

7. Reboot

8. Try to boot back into mac, Bootguard shows up, enter passphrase, looks like it is booting with Apple logo and wait spinner, and then turns to Circle with Slash

9. Reboot try to boot into windows

10. Windows Bootguard shows up - enter passphrase, then goes to missing operation system

 

Both partitions are pooched completely.

 

Even booting from external Mac Drive with PGP 10.1.2 allows me to see the Disk 0, but decryption of that drive gets rid of the encryptions and instrumentation, but partions are not bootable and mac partition not fixable by disk utility verify/repair.

 

I have replicated this 3 times now trying the processes in various forums and the same behaviour happens to me.  It seems that booting windows natively after this process screws up everything into a non recoverable state.

Help!

Please!

It sounds like you are having a problem similar to the issue described in this thread here.

What you need to do is request service pack 3 of PGP Desktop 10.1.2 to workaround this problem. You can do so by submitting a case online at https://mysupport.symantec.com and if you cannot submit the case there. Try calling tech support at (800) 342-0652. If you only have upgrade assurance, they may not authorize you for support. Since that only ensures that you get general release updates and not maintenance releases (such as service packs).

We will have a release coming out sometime the first part of next month which is PGP Desktop version 10.2. This will include the fix for the issue described in the above mentioned thread.

I hope this helps

Thanks for your help and information with this.  Looks like I won't be able to get the SP3 and will have to wait until next month.  I just hope I don't lose my laptop before then :)

Cheers

I'm also having some difficulty encrypting user-systems running OS X 10.6.x with Bootcamp - did you use a 3rd party NTFS driver for Mac in order to allow read/write of the Bootcamp partition by PGP Wde on the Mac side? and if so which driver did you use?

@PGP_Ben, 

 

   Installed 10.1.2 SP3 (build 50) on both MAC os-x 10.6.6 and windows 7 (bootcamp) partitions. From the MAC, started encrypting whole DISK0 (same process as identified in my above post).

 

SAME OUTCOME!

 

Both partitions are pooched as soon as I boot into windows 7 bootcamp natively.  This is getting very frustrating. I am walking around with IP on this laptop and cannot secure it in a desired fashion.

 

Please HELP!

It has been reported to have worked with many clients. I would check the build version of your PGP installation on the Mac OS x side and the Windows 7 side (it does have to be installed on both operating systems). You encrypted the FULL disk in Mac OSx side right?  Also, you could try PGP Desktop 10.2 alternatively since it includes all the fixes from SP1-SP3 on 10.1 and some new enhacements.