File Share Encryption

We have multiple laptops of identical configuration operating on WIN-7 32 bit.  These are Dell mfg with two hard drives used primarily as standalone systems controlling various test benches.  All earlier installs completed encryption of both drives completely.The PGP version is 10.2.1. 

The install for this last unit fails when I attempt to start the encryption of disk 1 (i.e. 'D' drive).

When I attempt to start the process and put in the password it indicates the encryption begins, but it will not go past '0%' complete. 

I have researched here, and followed various other simialr problems, without being able to resolve my own.

I have went to the command level and issued the pgpwde resume request for disk 1, and it will also show that it was accepted and the process has started without any changes being made. 

I have rebooted (multiple times); deleted and recreated the drive; reformatted the drive; added an deleted various size forlder just to have random data there; and still have not been able to get it to encrypt.

Does anyone have any ideas as to what I should do next?

This might seem slightly off topic at first. But hear me out:

What build of 10.2.1 do you have? If it's less than build 5033 then I would recommend upgrading right away. There was a critical bug that we have seen occuring on builds of PGP Desktop 10.2.1 prior to build 5033. We fixed this issue on that build number.

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

It's not a good situation to be in (where the filesystem can become corrupted from encrypting that secondary drive).

I would highly suggest upgrading to either 10.2.1 MP5 or 10.3.0 (now called Symantec Encryption Desktop in 10.3).  Then test this out again. If you still have issues. I would recommend following the recommendations in our best practices guide, as far as defragementing the hard disk, running a disk check, etc. See here for more information on those recommendations:

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

Unfortunately this policy and the related installations are controlled by NASA HQ branch and I am unable to effect a solution that would involve a software upgrade.

Route66rider, please IM me. I work with the support engineers who help work cases for NASA and maybe we can come to some kind of solution.