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, 18:24

80 entries

WorkaroundKnown issue

RD Web Access: page fails to render when XSLT is disabled in Chromium browsers

RD Web Access in Windows Server relies on XSLT (Extensible Stylesheet Language Transformations), which is being disabled in Chromium-based browsers such as Microsoft Edge and Google Chrome. Once it is disabled, the RD Web Access page fails to render and users cannot reach it. Microsoft documents workarounds and asks admins to adopt one before the browser change reaches their users.

Microsoft · RD Web Access

FixedKnown issue

Windows 11 26H2: Remote Desktop fails for non-admin users (0xC000000D)

After the September 2026 preview update, non-admin users might be unable to connect via Remote Desktop to devices that have Administrator protection enabled. Microsoft resolved the issue with updates released on 2026-10-28. For Windows 11 24H2 the release health page still shows the issue as mitigated, with a fix planned for a future update.

Microsoft · Windows 11, Version 26H2

FixedKnown issue

Windows 11 26H2: Black screen or desktop does not load after sign-in (fixed in KB5127648)

After installing Windows 11, version 26H2 and subsequent updates, some devices may fail to load the desktop after sign-in. The issue was mainly observed on Azure Virtual Desktop (AVD) hosts using FSLogix, more often with some existing user profiles. Microsoft resolved it with the updates released on 2026-10-13 (KB5127648) and later.

Microsoft · Windows 11, Version 26H2

FixedKnown issue

Windows 11 26H2: October 2026 update fixes VPN, FSLogix and S2D issues; one extra restart possible

The October 2026 Windows security update was released on 2026-10-13 for all supported Windows versions. For Windows 11, version 26H2, it fixes several known problems: Always On VPN, a black screen in Azure Virtual Desktop with FSLogix, and tiered Storage Spaces Direct virtual disks. A limited number of devices may need one additional restart during installation because of the Secure Boot certificate update.

Microsoft · Windows 11

UpcomingDated change

Intune: CNAME auto-discovery ends for Windows MDM-only enrollment on 2027-01-15

From January 15, 2027, Microsoft Intune no longer supports auto-discovery of the enrollment service via the EnterpriseEnrollment DNS CNAME record in Windows MDM-only enrollment. Users may then have to enter the enrollment server URL manually. Windows MDM-only enrollment itself remains supported and existing enrolled devices are not affected.

Microsoft · Intune

In effectDated change

Debian ca-certificates: emSign ECC Root CA G3 and Comodo AAA Services root removed (DSA-6572-1)

Debian found that several eMudhra intermediate CA certificates have been compromised. Security advisory DSA-6572-1 (published 2026-10-20) provides updated ca-certificates packages that remove the "emSign ECC Root CA - G3" and "Comodo AAA Services root" root certificates. Once the update is installed, certificates chaining to these roots are no longer trusted.

Debian · ca-certificates

WorkaroundKnown issueFix script

Exchange Server: unstable after October 2026 Windows Server updates (ec=1142)

Since the October 13, 2026 updates, Exchange servers running on affected Windows Server versions may become unstable after some time. Microsoft states this is not an Exchange update issue. A registry workaround (EpmapSavedContextCap) is available; no follow-up fix is imminent.

Microsoft · Windows Server / Exchange Server

In effectDated change

Exchange Online: EWS deprecation needs EWSAllowedAppIDs, Microsoft disables EWS in some tenants

Microsoft has started deprecating Exchange Web Services (EWS) in Exchange Online. In the multi-tenant (WW) cloud, EWSEnabled = True alone no longer keeps EWS working; an app ID allow list (EWSAllowedAppIDs) is required. Microsoft is disabling EWS in tenants where both settings are empty. Tenants already set to EWSEnabled = True are not changed until April 2027.

Microsoft · Exchange Online

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.