- Veeam Support Knowledge Base
- Cannot Register Management Service. The Specified Service Has Been Marked for Deletion.
Cannot Register Management Service.
The Specified Service Has Been Marked for Deletion.
| KB ID: | 1929 |
| Product: | Veeam Backup & Replication | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 |
| Published: | 2014-09-24 |
| Last Modified: | 2026-06-08 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
Failed to prepare VM for processing: Unable to perform installation
Unable to register and start service. Attempt 10 of 10
Cannot register management service. Service name: [VeeamVssSupport].
Cannot create service. Machine: [hostname.domain.tld]. Service name: [VeeamVssSupport]. Service binary path: [C:\Windows\VeeamVssSupport\VeeamGuestHelper.exe]. Service account: [].
Cannot create service.
Win32 error:The specified service has been marked for deletion.
Code: 1072 (System.Exception)Cause
The VeeamVssSupport service cannot be installed because the VeeamVSSSupport service is still present from a previous job run and is marked for deletion by the OS. The service becomes marked for deletion by the OS when the OS fails to process the service delete request that the previous job run sent.
By default, Non-Persistent Runtime Components are used by Veeam Backup & Replication when performing Application-Aware Processing. A connection is made to the Guest OS during each backup job run, and the VeeamVSSSupport service is installed. When the VM is done being processed, Veeam Backup & Replication sends a request for the VeeamVSSSupport service to be deleted.
Solution
More Information
This error may also occur if certain critical OS services cannot start because they've been disabled.
- Volume Shadow Copy — Default Startup Type: Manual
- Windows Management Instrumentation — Default Startup Type: Automatic
- COM+ Event System — Default Startup Type: Automatic
If this issue frequently recurs for a specific VM, consider switching from Non-Persistent Runtime Components to Persistent Runtime Components. When using Persistent Runtime Components, the VeeamVSSSupport service is not removed after each job run and remains present in the Guest OS, ready for the next job run.
To enable the use of Persistent Runtime Components:
- Ensure the VeeamVSSSupport service is not stuck marked for deletion. If it is, reboot the VM.
- Enable the Use persistent guest agent setting within the job for that VM.
- To use persistent agent components, consider the following:
- For Veeam Backup & Replication 13
Generate the Deployment Kit on the backup server and then run it on the protected Windows machine. The Deployment Kit typically contains necessary binaries and supporting files, authentication certificates, and a sample service configuration script (InstallDeploymentKit.BAT) for automated installation. For more information, see Using Veeam Deployment Kit. - For Veeam Backup & Replication 12 and older
Manually install the Veeam Installer Service on the VM
The VeeamInstallerSvc.msi is located on the Veeam Backup Server in:
C:\Program Files\Veeam\Backup and Replication\Backup\Packages
- For Veeam Backup & Replication 13
With "Use persistent guest agent" enabled in the job and the required packages installed, during the next job run, the VeeamVSSSupport service will be created and will remain after the job completes.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
