PGP Whole Disk Encryption does not resume after a hard power off
|Article:TECH165872|||||Created: 2011-07-28|||||Updated: 2014-03-18|||||Article URL http://www.symantec.com/docs/TECH165872|
PGP Whole Disk Encryption does not automatically resume after a hard power off when "Force power failure safety" is enabled for the policy.
When viewing the encryption status in PGP Desktop, the Encryption Progress displays as paused, but the button to Resume encryption is not available. When clicking the Stop button, the only options are to Decrypt, Pause, and Cancel.
PGP Desktop 10.1.2 in a PGP Universal Server managed environment.
PGP Universal Server 2.12, 3.0.x, 3.1.x
Use one of the following workarounds a solution:
Encryption of the disk can be resumed by restarting the encryption process via the pgpwde command from the command line interface.
To use the pgpwde command:
1. Open a command prompt.
- Windows XP - Click Start >Run and type cmd in the Open field and then click OK.
- Windows Vista/7 – Click Start and type cmd in the Start Search/Search programs… field. Select cmd from the list of Programs.
2. Switch to the C:\Program Files\PGP Corporation\PGP Desktop directory.
3. Type pgpwde –-resume –-disk 0 –p “your passphase” and press Enter.
After resuming from the command line, the encryption progress will display normally in the PGP Desktop interface as encrypting.
Update the server policy
This issue can also be resolved by removing the "Force power failure safety" from the policy on the PGP Universal Server.
To configure the policy:
- Login to the PGP Universal Server admin interface.
- Click Consumers > Consumer Policy.
- Select the desired policy to edit.
- In the PGP Desktop section, click Desktop and then select the Disk Encryption tab.
- Scroll down and remove the checkmark next to Force power failure safety.
- Click Save to update the policy.
Note: There is some risk to this second workaround as it will disable the PGP WDE journal function and limit the ability to recover after a power failure.
Article URL http://www.symantec.com/docs/TECH165872