Veeam B&R 13/13.1: Worker service fails with Alberta or British Columbia Standard Time
Summary
If the Windows time zone of the Veeam Backup Server is set to Alberta Standard Time or British Columbia Standard Time, new and existing workers fail to connect. The worker service does not recognise these new Windows time zone IDs. Veeam documents a temporary workaround; no fix is announced yet.
Symptoms
Workers fail with: Failed to connect to the worker service: "Alberta Standard Time" was not recognized as a valid Windows time zone ID (or "British Columbia Standard Time" in the same message).
Affected
- Veeam Backup & Replication 13 and 13.1
- Veeam Backup for Nutanix AHV
- Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization
- Veeam Sangfor aSV Plug-In, Plug-In for Xen, Plug-In for Proxmox VE, Plug-in for Scale Computing HyperCore
- Trigger: Veeam Backup Server time zone set to (UTC-06:00) Mountain Time (Alberta) or (UTC-07:00) Pacific Time (British Columbia)
Workaround
- On the Veeam Backup Server, open Settings > Time & language > Date & time.
- Turn off Set time zone automatically, otherwise Windows selects the new time zone again.
- In the Time zone list, select the fixed-offset zone for your area: for Alberta, Yellowknife and Inuvik and southeastern British Columbia locations that align with Alberta, select (UTC-06:00) Saskatchewan (Canada Central Standard Time); for most of British Columbia, select (UTC-07:00) Yukon (Yukon Standard Time).
- Note: these zones have different names, geographic mappings and historical rules, so treat them only as a temporary measure.
Fix
Not fixed yet.
Recommendation
Check the time zone of your Veeam Backup Servers, especially if they are located in Alberta or British Columbia or if automatic time zone is enabled. Apply the workaround if affected and watch KB4958 for a fix.
Sources
- Veeam KB4958 Vendor · www.veeam.com
Compiled from the sources listed and translated with AI (Claude); status and dates come from the vendor. The vendor’s statements are authoritative. Updated 1 Nov 2026, 15:35.
Where the information comes from
We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:
- Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
- other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
- community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
- targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
- early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online
Summary and translation with AI (Claude by Anthropic) – without any data of visitors.
Affected? We can help.
We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.