Microsoft has officially acknowledged a significant visual bug introduced by the August 2024 optional preview update, KB5064081, for Windows 11, which caused display screens to exhibit a noticeable red tint under certain conditions. The company confirmed that the issue has been resolved in a subsequent update released in October.
The problem, which began appearing in user reports shortly after the rollout of KB5064081, manifested primarily during video playback and gaming sessions. Affected users described a scenario where their screens would take on a pronounced and unnatural reddish hue, significantly impairing the visual experience. While Microsoft’s official communication did not delve into granular technical details, it confirmed the existence of the “red screen” or “red shift” issue. Industry analysts and technology observers have speculated that the root cause was likely an anomaly within the brightness or color rendering algorithms, potentially triggered when the system engaged High Dynamic Range (HDR) mode. This miscalibration would result in an over-representation of red tones across the display output.
In a statement, Microsoft identified the problematic update and provided a clear path to resolution. The company stated that the flaw was successfully isolated and addressed in the later October 2024 optional preview update, known as KB5067036. For users who have not manually installed this optional update, Microsoft has confirmed that the official fix will be seamlessly integrated into the next scheduled monthly security release, the November 2024 “Patch Tuesday” cycle. This rollout strategy ensures that all users receiving automatic updates will have the red screen issue permanently resolved without requiring further action.
However, the solution has arrived with a new, albeit less severe, complication. The very same KB5067036 update that fixed the red display problem has introduced a separate bug affecting the Windows Task Manager. Numerous users have reported that after launching the Task Manager, the application becomes resistant to standard closure methods. Clicking the ‘X’ close button or selecting “End task” from the menu often fails to terminate the process, leaving Task Manager running persistently in the background. The only reliable workaround for users encountering this behavior has been to restart the system or use a more forceful method through other system monitoring tools.
Microsoft is aware of this secondary issue and has already communicated its plans for a fix. The company has indicated that a patch for the unresponsive Task Manager is in development and is scheduled for inclusion in a future update. Current projections point towards a resolution being delivered with the Patch Tuesday release scheduled for November 11, 2025. This timeline highlights the ongoing challenge for large-scale software maintainers in balancing the rapid deployment of critical fixes with the thorough validation required to prevent new regressions.
This sequence of events serves as a reminder for users, particularly in enterprise environments where stability is paramount, regarding the nature of optional preview updates. These releases, labeled as “C” and “D” updates in Microsoft’s monthly cycle, are intended for early adopters and IT professionals to test for compatibility issues before changes are broadly distributed on Patch Tuesday. The incident with KB5064081 underscores the potential risks of deploying these non-security preview updates in production environments, as they can sometimes introduce unforeseen bugs. The recommended best practice remains to await the consolidated and more rigorously tested security updates released on the second Tuesday of each month for the most stable experience.
