Skip to main content

Veeam Version Standard — Pinned Build 13.1.1.18

Field Detail
Audience T1 / T2 / T3
Version 1.0
Last Updated October 2026
Applies To Every DTC BDR running Veeam Backup & Replication
Source HALO 1179664 (v13 fleet upgrade)

The standard

Every DTC BDR runs Veeam Backup & Replication 13.1.1.18. That is the 13.1.0.411 base install plus the 13.1.1.18 patch.

  • A BDR not on 13.1.1.18 gets a Halo ticket to update it. Title it Update Veeam to 13.1.1.18 — <BDR>, then run the NinjaOne script Veeam v13 Upgrade (script 203) against it.
  • Do not upgrade past the pin without Code Commander approval. A newer build becomes the standard only when this page changes.
  • New and replacement BDRs are provisioned straight onto 13.1.1.18. Install 13.1.0.411, let the first full backup complete, then apply the patch.

This page is the single source of truth for the pinned build. Other pages link here rather than repeating the number.

How to check a BDR's version

Read the installed-programs entry. Do not read the file version of Veeam.Backup.Service.exe — it stays at 13.1.0.411 after the patch, so a fully patched BDR looks one step behind.

Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*','HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*' -ErrorAction SilentlyContinue |
  Where-Object DisplayName -eq 'Veeam Backup & Replication' | Select-Object DisplayName, DisplayVersion

DisplayVersion reads 13.1.1.18 on a compliant BDR.

Fleet-wide, the NinjaOne script Get-VeeamFleetState reports every BDR's build and position (AT_TARGET, NEEDS_PATCH, NEEDS_1_HOP). The veeamUpgradeState custom field carries the upgrade script's last result. See the Veeam BDR Script Toolkit.

Running the update

  1. Open the Halo ticket.
  2. Run Veeam v13 Upgrade against the BDR during business hours, outside 22:00–04:59. The S3 copy window keeps jobs running overnight, and the script will not install over a running job.
  3. A BDR moves one hop per run (12.3.1 → 12.3.2 → 13.1.0.411 → 13.1.1.18 patch). Re-run until the installed-programs entry reads 13.1.1.18.
  4. If a run halts, its log names the blocker. Match it in the Veeam Setup Failure Reference (13.1.1.18).

What the pin requires of a BDR

Requirement Why
Windows 11 23H2 or later Veeam 13.1 setup refuses Windows 11 22H2 (setup event 101).
33 GB free on C: for a hop, 30 GB for the patch Setup needs 32.27 GB on C: for a full hop, wherever the ISO is staged.
PowerShell 7.6 that starts The Veeam 13 PowerShell module requires it; the upgrade script and fleet scripts use it.
Every protected endpoint's agent upgradable Setup refuses while an outdated agent is registered. See Veeam Endpoint Agent Blocks the BDR Upgrade.

Change record

Version Date Author Change
1.0 October 2026 Z. Boogher Initial release. Pins the fleet to 13.1.1.18 at the close of the v13 upgrade (HALO 1179664).
Back to top