How Can We Help?

Search for answers or browse our knowledge base.

Documentation | Demos | Support

< All Topics

How to remove the Symantec DLP Endpoint Agent (Windows)

The DLP agent is intentionally designed to be difficult to remove for security purposes. Below are the different methods used to uninstall the DLP agent.

Note: Administrative privileges will be required.

Windows Agent Uninstall

Method 1: Use Uninstall_agent batch file

We provide an uninstall_agent.bat / uninstall_agent64.bat with the agent install files.

Follow these steps to use this batch file:

  1. Obtain the batch file from the agent install files that were used when installing the agent. See Agent Install Files Information.
  2. If the agent was installed with an uninstall password then add that information to the batch file
  3. Copy the batch file to the client computer
  4. Run the batch file with administrator privileges.

Method 2: Msiexec command line uninstall

This method requires the uninstall password, unless there is not one configured or it has been disabled (see below). There are two options for uninstall via msiexec. The first one is to uninstall using the GUID. The second one is to provide the original .msi file.

GUID Uninstall

  1. Login as an administrator user.
  2. Start a command prompt (Administrator command prompt if Windows Vista or higher).
  3. Run the command: msiexec /x {PRODUCT_ID.EN_US}

Example 14.6 mp2 silent uninstall command line:

msiexec /uninstall {BF9489ED-B077-4EA3-9A72-3AE1DC96E6CD} /q UNINSTALLPASSWORD=””

NOTE: Substitute the appropriate value from the following table for {PRODUCT_ID.EN_US} in the command line above (include the curly braces).

Version Product ID
8.1 {69E7464F-6E7E-4607-9C9E-085DA243D807}
9.0 (9.0.1) {0C9B68A6-63B4-473F-B281-24774FBBFF73}
9.0.2 {1BE4CCA3-9B6C-4943-B03E-19CBFA51A88F}
9.0.3 {D26F44C8-44BB-47FA-81E8-8F5EDA53E3AA}
10 {BB81F635-3CDB-405A-9AF3-0428D42EA605}
10.5.x (10.5.0, 10.5.1, 10.5.2, 10.5.3) {ADBACBC0-05F4-4610-BBB7-007A543D5B47}
11 {BC705572-C8CD-49e4-9693-BDC8E4D35570}
11.1.x (11.1.0, 11.1.1, 11.1.2) {2AF3B399-42A5-42bd-A5E0-72B657110363}
11.5.x (11.5.0, 11.5.1) {2AF3B399-42A5-42bd-A5E0-72B657110363}
11.6 {8790B246-A2CF-43b1-BDB0-2B4383BB9785}
11.6.1 {9E983F62-FFE9-4A92-AA24-2CA97B353A73}
11.6.2 {E818C222-AC57-46B4-9689-83DFB591D8F4}
11.6.3 {70365353-32F7-4367-8E71-ABDC966D0488}
12 {D39272A1-C04C-4295-8558-79E1991BA4FC}
12.0.1 {1C4B1778-B5E7-4A2F-98D2-F8FBDE968B6C}
12.5 {B29DE059-FEC4-4304-96BB-50308729BEDE}
12.5.1 {9967A8CA-E48C-4AE9-99C8-6A48AF57669A}
12.5.2 {D37485C2-CC03-4EEB-9BFA-E1409AE00A6C}
12.5.3 {96CF9953-B3BF-44AF-A173-4615878CD7BE}
14.0.0 {D38C2A80-D5BB-5654-DA40-748217D55C12}
14.0.1 {8CFAB030-FA5E-43B5-AC38-4992D050866E}
14.0.2 {C4D24B06-0D75-4853-B716-A8AD33C7B919}
14.5 {3B85F620-7485-4F58-8984-1E2C386C4BAC}
14.5 MP1 {FA2F2911-4C34-46B3-A020-98DE32CA705E}
14.6 {09338028-1DB6-4C5E-A5FC-D4F0142BF212}
14.6 MP1 {D675A448-C21A-47C9-9F9D-1FF04A02570A}
14.6 MP2 {BF9489ED-B077-4EA3-9A72-3AE1DC96E6CD}
14.6 MP3 {40523681-A23A-4B45-B7EB-2BCBCEB0FD9F}
15.0 {679AB287-7757-4321-A90A-55B6AE200476}
15.0 MP1 {EA83ED79-E1E7-4C7E-8B92-8DD2B2634FC9}
15.1 {554BE59C-56FA-485D-B8C9-7EAC54CB43DD}
15.1 MP1 {099385D0-F0AD-45C9-A0A1-F18CD845F21C}
15.1 MP2 {3CD80E90-4C66-4DC9-BF1F-AE37C62FA064}
15.5 {12F26F08-FE80-44EF-91BB-06CD0F5E1B16}
15.5 MP1 {11012518-A235-4178-8041-ACA48E052C60}
15.5 MP2
15.7 MP1

You can identify which version of the Endpoint Agent is installed by looking at the file version properties of the edpa.exe or by navigating to the registry key:


Search for the value called “DisplayName” that contains the string “AgentInstall”. The uninstall command (including the Product ID) will be under that key’s UninstallString.

MSI File Uninstall

The .msi file uninstall is useful if the local copy of the install has been removed from the system and when using the GUID method causes a “This installation package could not be opened” error message.

To uninstall with the .msi copy down the AgentInstallX_X_X.msi file (Example: AgentInstall64_15_0.msi) that was used to install the agent on the machine. Note that it must be the same version .msi as the installed agent version. Then run the following command:

msiexec /x AgentInstall64_15_0.msi -l*v uninstall.log

The above methods will prompt for an uninstall password if one is configured. If you are unsure what the uninstall password is then can either disable the uninstall password or setup a new uninstall password. These options are only available in DLP 15 and above.

To apply a new uninstall password from the console go to System > Agents > Agent Password.

Once on this page click configure then check the “Apply New Uninstall Password” box. After that, type in the new uninstall password then re-enter the new password in the next field. Now click save. The updated uninstall password will go down to all agents with a good status. If the agent is disconnect and unable to connect it will keep the old uninstall password.

To disable the password go to System > Agents > Overview and select the agents that you want to disable the uninstall password on. Next click the Troubleshoot button and select “Disable Uninstall Password”.

Method 3: Contact Support

Support has additional tools and resources to help remove agents that will not uninstall using the above method. Contact support for further assistance and reference this knowledge base article.

Alternative solution: Disable the agent

As an alternative solution, the agent can also be deactivated. This will stop the services and the agent machine can be used as though the agent was not installed and no policies will be enforced.

To disable the agent go to System > Agent > Overview. Click the box next to the target agent, and the select the shutdown option.

This option can temporarily stop the agent until the machine is restarted, or permanently shut down the agent by stopping the service and setting it to manual.

Was this article helpful?
3.8 out of 5 stars
5 Stars 33%
4 Stars 33%
3 Stars 0%
2 Stars 33%
1 Stars 0%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents