File Share Encryption

Laptop: Dell M4600 with SSD primary HD and non-SSD secondary HD. 
PGP Client: 10.2.1  (build 4461)
 

BSOD (image attached) after PGP encrypts secondary drive sucessfully, shutdown, power up, log-in past PGP (pre-windows) and log into windows, then system receives BSOD.  Power back up and error "Missing Operating System"
Primary hard drive (SSD) encrypts with PGP with no issues.

In the BIOS, boot sequence - only mini SSD is checked, everything else is unchecked.
AHCI

Unable to access crash dump file, currently running PGP Recovery disk to decrypt.

We've used this version of PGP on over 100 laptops and this configuration for some reason isn't working.
Tested on 3 laptops already, all with the same results.

Help

This sounds like http://www.symantec.com/docs/TECH177656

It would be interesting to try either a newer build, or even PGP Desktop 10.2.0 MP4 to see if the problem remains.

that case http://www.symantec.com/business/support/index?page=content&id=TECH177656
says they receive a bsod everytime they reboot and "After rebooting the computer again and the operating system successfully loads."

In our case, the OS doesn't load and our BSOD only appeared once (after the 2nd HD was successfully encrypted, then reboot/shutdown)

Thanks for the clarification.  Although, I'm not seeing anything specific to this, I'd suggest trying the current release of 10.2.1 MP5, build 5033.

If you are eligible for the free upgrade/update, it should be available at Fileconnect. 

what would cause PGP to fail once we encrypted the 2nd drive?

PGP encrypts the primary drive (SSD) with no issues.  Once we encrypt sucessfully the 2nd drive and reboot, BAM!!! BSOD and Missing Operating System error.

Sorry for the delay in response to your your thread. There are several forum threads out on this same issue. This is a problme that was address with PGP Desktop 10.2.1 MP5 or newer. the latest version available today is Symantec Encryption Desktop (formerly PGP Desktop) 10.3.0. If you upgrade that version, this will solve your problem from occuring again. It was an issue with adding multiple users to a secondary drive on the machine.