Knowledge Base

Dell Data Protection Personal Edition for Windows Removal Guide


This article provides information how to remove Dell Data Protection | Personal Edition (DDP | PE)


Affected Products:

Dell Data Protection | Personal Edition




Launch ddpe_xxbit_setup.exe (replace xx with your installed bit level), approve any required UAC prompts:


(Figure 1: English only - DDP | PE Removal Guide)

Installer will check pre-requisites:


(Figure 2: English only - DDP | PE Removal Guide)


(Figure 3: English only - DDP | PE Removal Guide)

The recommended way to decrypt the system is through the use of the Decryption Agent.

The Decryption Agent enables the users to continue using their system while the system is decrypted.


(Figure 4: English only - DDP | PE Removal Guide)

Personal Edition only allows for keys to be injected by leveraging the LSARecovery file.

The LSARecovery file's location is set during the initial install.

You can validate where it was backed up by checking registry.

HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CMGShield
REG_SZ: ABL
Value:<location backup="" of=""></location>

Note: If this file cannot be found, we can backup the key again using the steps in this article: How to backup encryption keys in DDP | PE

The Password for the LSARecovery file to allow decryption is the same Encryption Administrator Password used to access the policies or settings in the DDP Encryption console.


(Figure 5: English only - DDP | PE Removal Guide)

The default of "Local System Account" is usually used to perform the decrypt:


(Figure 6: English only - DDP | PE Removal Guide)

Click remove to start the shield removal and removal agent installation:


(Figure 7: English only - DDP | PE Removal Guide)

Click Finish to complete the operation. Reboot when possible to start the removal agent service.


(Figure 8: English only - DDP | PE Removal Guide)

Upon reboot the Encryption Removal Agent service will start decrypting. You can check the service status to determine when the decryption is complete and you can continue with the Windows upgrade.


(Figure 9: English only - DDP | PE Removal Guide)

Possible states include:

  • Waiting for Deactivation – DDP|E is still installed, is still configured, or both. Decryption does not start until DDP|E is uninstalled.
  • Initial sweep – The Service is making an initial sweep, calculating the number of encrypted files and bytes. The initial sweep occurs one time.
  • Decryption sweep – The Service is decrypting files and possibly requesting to decrypt locked files.
  • Decrypt on Reboot (partial) – The decryption sweep is complete and some locked files (but not all) are to be decrypted on the next restart.
  • Decrypt on Reboot – The decryption sweep is complete and all locked files are to be decrypted on the next restart.
  • All files could not be decrypted – The decryption sweep is complete, but all files could not be decrypted. This status means one of the following occurred:
    • The locked files could not be scheduled for decryption because they were too big, or an error occurred while making the request to unlock them.
    • An input/output error occurred while decrypting files.
    • The files could not be decrypted by policy.
    • The files are marked as should be encrypted.
    • An error occurred during the decryption sweep.
  • Complete – The decryption sweep is complete. The Service, the executable, the driver, and the driver executable are all scheduled for deletion on the next restart.

For additional support, US based customer can call Dell Data Protection ProSupport at: 877.459.7304 Ext. 4310039 or you may also contact us via the Chat Portal for Dell Data Protection | Personal Edition and Security Tools. For support outside the US, reference ProSupport’s International Contact Numbers list. Visit the Dell Security Community Forum to get insights from other community members and additional resources to help you manage your environment.


Article ID: SLN298374

Last Date Modified: 05/23/2017 10:25 AM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Feedback shows invalid character, not accepted special characters are <> () &#92;
Sorry, our feedback system is currently down. Please try again later.

Thank you. Your feedback has been sent.