IT SBIT Services
Schneeberger
DEEN
Known update issues

Known issues after updates

What stops working after updates from Windows, Microsoft 365, Exchange, VMware, Veeam and other major vendors – with status, workaround and fix, continuously from the vendors’ official sources, complemented by reports from forums and the community and by targeted web research. Anything the vendor has not confirmed yet is labelled as a community report.

Sources last checked: 1 Nov 2026, 20:49

4 entries

WorkaroundKnown issue

Veeam ONE 13.1.0.7233: scanners still report finding (Reporter shows 13.1.0.7034)

After installing Veeam ONE 13.1 Patch 0 (build 13.1.0.7233), some vulnerability scanners keep reporting the finding for CVE-2026-65641. The Veeam ONE Reporter executable stays at version 13.1.0.7034 because the patch does not modify it. This is a false positive; Veeam documents an exception in the scanner as the way to handle it.

Veeam · Veeam ONE

WorkaroundKnown issue

Veeam Backup for Microsoft 365: repair SharePoint/OneDrive/Teams files backed up corrupted (KB4835)

Due to the issue described in KB4835, SharePoint, OneDrive and Teams files and list attachments may have been backed up with corrupted content. Veeam KB4874 describes how to identify and repair them with an Integrity Check and a repair session. The article was updated on 2026-10-27 for version 8.6, which adds support for JET-based and immutable repositories.

Veeam · Veeam Backup for Microsoft 365

FixedKnown issue

Veeam KubeVirt Proxy 1.0.3: fixes leaked data mover pods, slow snapshot detection, missing VM settings

Veeam KubeVirt Proxy (KVP) 1.0.3, released on 2026-10-27, resolves three issues: leaked backup data mover pods that block new backups, slow detection of snapshot status changes, and VirtualMachine settings missing from backups. The Veeam Plug-In for KubeVirt (also known as Veeam Plug-In for Red Hat OpenShift Virtualization) uses this proxy. The release also updates the ubi10/ubi-minimal package to address CVE-2026-114406 and CVE-2026-77214.

Veeam · Veeam KubeVirt Proxy

WorkaroundKnown issue

Veeam B&R 13/13.1: Worker service fails with Alberta or British Columbia Standard Time

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.

Veeam · Veeam Backup & Replication

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.