Microsoft has confirmed that the August 2026 security update can trigger a Windows Server 2016 CompatTelRunner crash on systems where the Compatibility Appraiser diagnostic service is running. The good news, if you can call it that, is that the crashes are cosmetically ugly but functionally harmless, at least according to Microsoft itself.
The issue manifests as recurring Application Error events in the Windows Event Log: Event ID 1000, with exception code 0xc0000409, tied to the CompatTelRunner.exe process. That process belongs to Microsoft Compatibility Appraiser, a background component of Windows Compatibility Telemetry that checks whether a device meets the hardware and software requirements for the next major cumulative update or feature upgrade. When the August update conflicts with it, the process crashes on a loop, filling event logs with warnings.
What the Service Alert Actually Says
The issue is tracked under Service Alert WI1467310, as Windows Report noted when it spotted the alert. Microsoft’s own wording is worth reading carefully: ‘Although recurring CompatTelRunner.exe failures might generate Application event log entries, they do not affect device functionality. The associated event log warnings can be safely dismissed temporarily until we release a resolution in an upcoming update.’
That last phrase (‘temporarily’) is doing a lot of work. Microsoft has not shared a timeline for a permanent fix, saying only that one will ship in a future Windows update. So for now, administrators on affected systems are being asked to tolerate the log noise.
The problem is not limited to bare-metal installations. Microsoft says the known issue affects both physical devices and virtual machines, including VMware and Azure environments, which widens the potential blast radius considerably for organisations running Server 2016 workloads in the cloud or on virtualised infrastructure.
A Pattern of August and Recent Patch Problems
This is not an isolated stumble. In June, Microsoft fixed a separate Windows Server 2016 known issue that caused June 2026 security updates to fail outright on systems that were not fully up to date. More recently, Microsoft warned customers of application crashes on some Windows Server 2025 systems, tied to memory management changes introduced in a recent update.
That Server 2025 problem is more severe in character. It affects applications using Address Windowing Extensions (AWE), a set of extensions that allows them to access more than 4GB of physical memory within a 32-bit virtual address space. On impacted systems, administrators are seeing memory corruption errors, access violation exceptions carrying 0xC0000005 error codes, SQL Server crash dumps, and SQL Server services stopping or restarting unexpectedly. That is a different category of pain from a crashing telemetry runner.
The CompatTelRunner issue was surfaced publicly by Microsoft MVP Susan Bradley, who spotted the service alert. Her flagging of these kinds of advisories has become something of a public service for administrators who would otherwise miss the quieter corners of Microsoft’s support documentation.
The Clock Is Already Running on Server 2016
There is a broader context worth keeping in mind here. According to Microsoft Support, Windows Server 2016 reaches end of support on 12 January 2027. That gives organisations running the platform less than a year to either migrate or make extended support arrangements. Patching a crashing telemetry process on an OS that is approaching end of life is, frankly, the kind of maintenance task that tends to crystallise upgrade decisions.
Meanwhile, September’s Patch Tuesday (the release cycle that followed the August update that caused all this) turned out to be a record-breaker. Windows Report reports that Microsoft’s September 2026 Patch Tuesday addressed 966 vulnerabilities, making it the largest Patch Tuesday release the company has ever shipped. Whether that scale of patching produces its own crop of known issues in the weeks ahead remains, for administrators, a question they would probably rather not have to ask.
Microsoft says the CompatTelRunner fix will arrive in an upcoming update; with January 2027 on the horizon for Server 2016, that update cannot come too late.
