// Define dataLayer and the gtag function. window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} // Set default consent to 'denied' as a placeholder // Determine actual values based on your own requirements gtag('consent', 'default', { 'ad_storage': 'denied', 'ad_user_data': 'denied', 'ad_personalization': 'denied', 'analytics_storage': 'denied' });

Symantec Backup Exec: Saying “Uninstall” and Mean It

Honest backup solutions are the best ones. Not allowing the user to completely uninstall anything he doesn’t longer need is definitely is a bad taste. But at the end of the day maintaining the computer is still a user business. So, how can the life become easier, at least, a little bit?

Small Windows Logo Download for Free

Version 8.5.8 , built on October 31, 2024. 118 MB
30-day full-featured trial period

Handy Backup is among the fair-players. When you select the "Uninstall" option, there wont be anything reminding you of our solution in less, than five minutes. But, unfortunately, not everyone can boast with such an attitude.

Unfortunately, you may meet up some Symantec Backup Exec issues during its using.

So, how to completely uninstall, say, Symantec Backup Exec? The answer is right here!

Symantec Backup Exec Uninstall Instruction

Method 1

NOTE: This process will replace any missing or corrupted files and registry keys and a complete re-configuration.

  1. Reinstall Backup Exec 11d and above with same settings as the previous installation.
  2. When prompted to select a BEDB (Backup Exec Database) Database Server select the same option as used with the prior installation.
  3. Uninstall Backup Exec through Add / Remove Programs. (Programs and Features in Windows 2008/Vista/7)

Method 2 (use only if Method 1 is unsuccessful):

  1. Save any need items of the BE environment. (Settings, Database, Job Logs, Catalogs, Reports, etc)
  2. Stop all Backup Exec Services, SQL Server (BKUPEXEC), MSSQL$BKUPEXEC, and MSSQL$BKUPEXECDLO Services.

    Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

  3. Remove the following Backup Exec Registry Keys:
    HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec for Windows
    HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\DLO
    HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\VxPush
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Symantec Backup Exec 11.0
  4. Delete any folders identified as Backup Exec or SQL, if SQL is also being uninstalled.
    HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\
    -27C846ACBA6625648A529949BAF5D651
    -30BF39ED4133E2E4F8549EDB77C6D152
  5. Also search through the other GUIDs to find all the ones for Backup Exec(Right click the HKEY_LOCAL_MACHINE\software\classes\Installer\Products key, Click Find , Type Backup, Click Find, Now check every Key that it finds before deleting. Check the right hand pane, look for the key "ProductName" It should say "Symantec Backup Exec Media Server or Remote Agent depending on what was installed. Make Sure to Right Click on the GUID in the left hand pane and Delete.")
    Please Note : Do not remove the following registry key, if Backup Exec needs to be installed again:
    287320 HKEY_LOCAL_MACHINE\Software\Symantec\CRF

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SCSIChanger
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
    (delete each key in the list below)
    ●Backup Exec
    ●BackupExecAgentAccelerator
    ●BackupExecAgentBrowser
    ●BackupExecDeviceMediaService
    ●BackupExecJobEngine
    ●BackupExecManagementService
    ●BackupExecRPCService
    ●bedbg
    ●bevssprovider
    ●Backup Exec VSS Provider
    ●DLOAdminSvcu
    ●DLOMaintananceSvc
    ●SCSIChanger

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents\(delete each key in the list below)
    • Value key:
      Software\Symantec\Backup Exec For Windows\Backup Exec\SNMP\Events
    • Value key:
      Software\Symantec\Backup Exec For Windows\Backup Exec\SNMP\TapeAlert
  6. Remove the SQL Instance in one of the following ways:

    a. If there is no other SQL instance on this machine delete:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    ---OR---

    b. If there are other SQL Instances, follow this procedure:

    • Navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

    • i. Right-click the InstalledInstances value, and then click Modify from the shortcut menu. The Edit Binary Value dialog box appears.
    • ii. Remove the BKUPEXEC from the Value data box, and then click OK.
    • iii. Right-click the BKUPEXEC key, and then click Delete from the shortcut menu. The Confirm Key Delete dialog box appears.
    • iv. Click Yes.
    • v. Navigate to the following registry location, and delete BKUPEXEC from the Default value.
      - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\Service Manager
    • vi. Right-click the Default value if it is BKUPEXEC, and then click Delete from the shortcut menu. The Confirm Value Delete dialog box appears.
    • vii. Click Yes.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQLServer\Component Set

    • i. Perform a search in the registry by highlighting 'My Computer', by going to Tools - Find search for BKUPEXEC and Delete all values identified.


    NOTE: Be sure to Check "Keys", "Values". and "Data" under Tools | Find | Look at
    NOTE: You will not be able to delete any of the values identified as legacy registry keys. Just page through these to the next set.

    ---OR---

    c. If using a SQL instance other than the BKUPEXEC instance:

    • i. Detach the BEDB database. (Refer to SQL documentation on how to detach a database from a SQL instance.)
    • ii. Remove the BEDB files bedb_dat.mdf and bedb_log.ldf from SQL instance data and log folders.
    • iii. If there are additional SQL instances on this server other than BKUPEXEC,
      NOTE: Browse to \Program Files\Microsoft SQL Server. That folder contains all SQL instances on the server.
      Instances named MSSQL$BKUPEXEC are related to an install of Backup Exec 10.0 and SQL 2000 and can be removed without consequences.
      SQL instances for SQL 2005 will be named MSSQL.1. MSSQL.2 and so on for each instance.
      Inside each instance folder, the name of the instance will show (Eg. BKUPEXEC, ACT!, ETC)
    • iv. Delete the one that is identified as being the Backup Exec one and make note of the number.
      - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
    • v. Delete the SQL folder with the same MSSQL number that is identified in the Program Files folder

  7. Remove all Backup Exec files from install directories (Note: %SystemRoot% is typically C:\Windows)
    • Backup Exec Installation Directory. The default installation directory is C:\Program Files\Symantec\Backup Exec
    • Backup Exec Maintenance Installation Files (if present)
      - %SystemRoot%\Installer\{BEA465C8-2923-42C6-9141-BE44739A6A80} (32-bit system)
      - %SystemRoot%\Installer\{ACE16FD9-EB87-42F4-9CB5-6FA8C820C9CD} (64-bit system)
    • Also, Create a new column in the installer by right-clicking on the column headers.
      - Choose "Author" Drag that column all the way to the left so that it is next to the MSI files.
      - Mouse over the msi files. if the MSI are identified as belonging to Backup Exec or Veritas, Delete them
    • Backup Exec Drivers located in %SystemRoot%\System32\Drivers
      - *.VSD (all files with a .vsd extension)
      - SCSICHNG.INF
      - SCSICHNG.SYS
      - oemtap.inf
      - oemtap0.inf
      - %systemroot% assembly, make sure there are no entries in there that are called Backup Exec or BKUPEXEC, if they are there, delete them.

      NOTE: If the SQL Services startup properly and there no SQL Warnings or errors in the Windows Event Log or SQL Error Logs, it may not be necessary to perform step 8. Also, if errors do occur while removing SQL Express, it is not recommend to delete or modify any SQL Files or registry values without first opening a support case with Microsoft.

    • Remove SQL Express BKUPEXEC and BKUPEXECDLO instances through Add/Remove Programs (Programs and Features in Windows 2008/Vista/7). These need to be removed in reverse order of how they appear in Add/Remove Programs (or Programs and Features)
      • Microsoft SQL Server 2005
      • Microsoft SQL Server Native Client
      • Microsoft SQL Server Setup Support Files (uninstallation of Microsoft SQL Server 2005 should remove this item)
      • Microsoft SQL Server VSS Writer (uninstallation of Microsoft SQL Server 2005 should remove this item)
    • Delete the Backup Exec icon from the Desktop.
    • Delete the Backup Exec program group from:
      \Documents and Settings\All Users\Start Menu\Programs
    • Reboot the system.

Did you uninstall Symantec Backup Exec? Download Handy Backup right now!

What to do next after Symantec Backup Exec uninstallation?

Download Handy Backup - try the latest version of Handy Backup!

Who uses Handy Backup?