Veeam Installer Service Missing After v11a Upgrade — "Failed to connect to the deployer service" (6160 / 11731)
Audience: T2 / T3 Version: 1.0 Last Updated: November 2026 Applies To: Windows servers in a Veeam Backup & Replication (B&R) protection group, B&R v13.1 (originally deployed from v11a)
Overview
This guide covers a protected Windows server where the Veeam Installer Service (VeeamDeploySvc) is missing after a failed component upgrade. A left-over v11a uninstall registration makes B&R think the service is still installed. B&R then skips the upload and fails to connect to a service that doesn't exist. Rescanning will not fix it.
Common symptoms:
- Protection group rescan or agent install fails with:
Unable to install backup agent: failed to connect to <host> Error: Failed to connect to the remote components. (Failed to connect with deployment kit on <host>:6160: [<host>] Failed to connect to the deployer service.) (Failed to connect with deployment kit on <host>:11731: ...) - From the B&R server, ports 135 and 445 test open, but ports 6160 and 11731 test closed
- On the target,
Get-Service VeeamDeploySvcreturns nothing and nothing listens on 6160 or 11731, but the Veeam Installer Service firewall rules exist C:\Windows\Veeam\BackupcontainsVeeamDeploymentSvc.exe.v11a-oldandVeeamDeploymentDll.dll, but noVeeamDeploymentSvc.exe- The Uninstall registry still lists Veeam Installer Service 11.0.1.x (key name
VeeamDeployerService), next to a much newer Veeam Backup Transport (12.x or 13.x) - Renaming the
C:\Windows\Veeam\Backupfolder and rescanning gives the same error, and the folder is not recreated, because B&R never uploads
Root cause:
During an earlier B&R upgrade (from v11a), the component update on the server failed partway through. It renamed the old service binary to .v11a-old, removed the service, and dropped the new DLL, but it never wrote the new VeeamDeploymentSvc.exe or registered the service. The v11a Uninstall entry was left behind. On each rescan, B&R reads that entry, decides the Installer Service is present, skips the deployment kit upload, and tries to connect on 6160 and 11731. With no service there, the connection fails.
Part 1: Confirm the diagnosis
From the B&R server:
Resolve-DnsName <host>
135,445,6160,11731 | % { Test-NetConnection <host> -Port $_ | Select RemoteAddress,RemotePort,TcpTestSucceeded }
- If 135 and 445 pass but 6160 and 11731 fail, continue with this guide.
- If 135 or 445 fail, the problem is SMB, RPC, or credentials. See the transport section of Veeam Agent — Corrupt Install: Force Removal & Clean Redeploy (Error 1605).
- ⚠️ Check
Resolve-DnsNamefor more than one A record. If the host resolves to more than one IP, B&R may connect to the wrong one. Add a temporary hosts-file entry on the B&R server that points the host at the correct IP. Clean up DNS afterward: remove the stale record, or turn off DNS registration on the secondary NIC.
On the target server:
Get-Service VeeamDeploySvc -ErrorAction SilentlyContinue # expect: nothing
netstat -ano | findstr ":6160 :11731" # expect: nothing
Get-ChildItem C:\Windows\Veeam\Backup -Recurse | Select FullName,Length,LastWriteTime
Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*,
HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* |
? DisplayName -like 'Veeam*' | Select DisplayName,DisplayVersion,PSChildName
The pattern to look for: no service, a .v11a-old binary with no current .exe, and Veeam Installer Service 11.0.1.x still registered.
Also rule out endpoint security. Defender ASR event 1121, Defender detections 1116 or 1117, and Blackpoint alerts around the time of the failure should all come back clean. If any of them show a block, fix the exclusion first.
Part 2: Clear the broken state (target server)
⚠️ Export the registry key before deleting it.
# 1. Move the half-upgraded kit folder aside
Rename-Item C:\Windows\Veeam\Backup C:\Windows\Veeam\Backup.broken-<yyyymmdd>
# 2. Remove the stale v11a Installer Service registration (exe-based entry, not an MSI GUID, so msiexec /x does not apply)
reg export "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\VeeamDeployerService" C:\Windows\Temp\VeeamDeployerService-uninstall.reg
Remove-Item 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\VeeamDeployerService'
# 3. Confirm no service remnant (should be False)
Test-Path HKLM:\SYSTEM\CurrentControlSet\Services\VeeamDeploySvc
If step 3 returns True, run sc.exe delete VeeamDeploySvc and reboot before continuing. A service that is marked for deletion blocks re-creation until the server restarts.
Part 3: Install the Installer Service manually with the deployment kit
Don't depend on push deployment for this one. Install the v13 Installer Service and its certificates directly.
3.1 Generate the kit (B&R server)
Generate-VBRBackupServerDeployerKit -ExportPath "C:\DTC\VeeamDeploy" -AllPlatforms
⚠️ Use -AllPlatforms, or make sure the Windows kit is included. Without it you can end up with only the Linux kit (.deb, .rpm, install-deployment-kit.sh), which won't install on Windows.
The export contains a Windows folder (OpenSSL and Installer Service packages, plus InstallDeploymentKit.bat) and a Certificates folder (server-cert.pem, server-key.pem, client-cert.pem).
3.2 Install (target server)
Copy the Windows and Certificates folders side by side to the target, for example to C:\Temp\VeeamKit\.
Option A: script. Open InstallDeploymentKit.bat in Notepad and confirm the folder paths it expects. Then run it from an elevated command prompt inside the Windows folder.
Option B: manual. In an elevated PowerShell:
cd C:\Temp\VeeamKit\Windows
# Install OpenSSL first, then the Installer Service (use the actual file names)
msiexec /i .\<OpenSSL-package>.msi /qn /l*v C:\Windows\Temp\veeam-openssl.log
msiexec /i .\<VeeamInstallerSvc-package>.msi /qn /l*v C:\Windows\Temp\veeam-installersvc.log
# Install the certificates
$svc = 'C:\Windows\Veeam\Backup\VeeamDeploymentSvc.exe'
$cert = 'C:\Temp\VeeamKit\Certificates'
& $svc --install-server-certificate "$cert\server-cert.pem" --key "$cert\server-key.pem"
& $svc --install-certificate "$cert\client-cert.pem"
Restart-Service VeeamDeploySvc
3.3 Verify the service
Get-Service VeeamDeploySvc # Running
netstat -ano | findstr ":6160 :11731" # LISTENING on 6160
Only 6160 needs to be listening. 11731 is a fallback. Running Test-NetConnection <host> -Port 6160 from the B&R server should return True.
Part 4: Deploy the agent (B&R server)
- Rescan the protection group. The server should be discovered with no deployer error.
- If the rescan finds the server but doesn't install the agent, right-click the computer and choose Install agent. Discovery doesn't always push the agent, especially for a computer that previously failed deployment.
- Check the protection group's Options step. If Install backup agent isn't ticked, rescans only inventory machines and never install.
- Complete any remaining server setup, such as configuring the local backup repository if that step was never done.
Verification
- Agent install completes with no deployer or RPC errors.
- The server shows the current v13-generation agent and Transport versions under the protection group.
- Run the backup job (or wait for its schedule) and confirm the first backup session succeeds. A green deployment isn't the finish line; a completed restore point is.
Cleanup
- Delete the kit from the target (
C:\Temp\VeeamKit) and from the B&R server (C:\DTC\VeeamDeploy), unless you're reusing it. It contains the server private key (server-key.pem). - Remove the temporary hosts-file entry once the duplicate DNS record is fixed.
- Delete
C:\Windows\Veeam\Backup.broken-<yyyymmdd>once the backups are healthy.
Quick Reference
Signature: 135 and 445 open, 6160 and 11731 closed. No VeeamDeploySvc. .v11a-old binary with no current .exe. Installer Service 11.0.1.x still in Uninstall.
Fix: rename the kit folder → delete the VeeamDeployerService Uninstall key → Generate-VBRBackupServerDeployerKit -AllPlatforms → install OpenSSL, the Installer Service, and the certificates on the target → restart VeeamDeploySvc → rescan, then Install agent → first backup succeeds → delete the kit.
Rule of thumb: if the rescan doesn't recreate C:\Windows\Veeam\Backup, B&R isn't uploading. Either a stale registration says the service is installed, or DNS is sending B&R to the wrong IP.
Fleet note: any server first deployed under v11a can be in this state. To find them, look for VeeamDeploymentSvc.exe.v11a-old with no VeeamDeploymentSvc.exe next to it, or an Installer Service registration at 11.x alongside a Transport at 12.x or later.
Related Documents
- Veeam Agent — Corrupt Install: Force Removal & Clean Redeploy (Error 1605)
- Veeam Server Jobs Fail in Seconds — Outdated Data Mover / Host Rescan Required
- Veeam v13 Fleet Upgrade — Runbook & Milestone Tracker
- Adding & Replacing Computers in Veeam BDR
- Veeam & BDR Troubleshooting Guide
Document History
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | November 2026 | Scott Leister | Initial creation from a live incident (2026-11-16): a physical server's protection group agent install failed on 6160 and 11731 after a broken v11a → v13 Installer Service upgrade (failed 2026-10-20). Resolved with a manual deployment kit install and an explicit Install agent. |
Confidential — Internal Use Only