Microsoft's latest Windows 11 update just broke one of the most essential system tools. The optional KB5067036 update is causing Task Manager to spawn duplicates every time users try to close it, creating a performance nightmare that's eating up CPU and RAM resources across affected systems.
Microsoft's latest Windows 11 update has turned Task Manager into the very problem it's supposed to solve. The optional KB5067036 update, released October 28th, is causing the system utility to multiply like a digital hydra every time users attempt to close it.
The bug breaks the familiar 'X' button that normally shuts down Task Manager. Instead of closing, the application stays running in the background while spawning additional instances with each attempted closure. For users who regularly rely on Task Manager to monitor system performance or kill unresponsive applications, this creates a snowball effect of resource consumption.
Reddit users first flagged the issue, with reports quickly spreading across Windows 11 communities. The Verge's Tom Warren confirmed the bug affects systems running the preview build, adding credibility to the growing pile of user complaints.
What makes this particularly frustrating is the irony - Task Manager exists to help users manage runaway processes and system resources. Now it's become the runaway process itself. Each duplicate instance continues consuming CPU cycles and RAM, potentially degrading system performance for users who don't realize what's happening.
The timing couldn't be worse for Microsoft. The company has been pushing Windows 11 adoption hard, with recent data showing the OS finally gaining meaningful market share. But bugs like this reinforce the perception that Windows updates remain a gamble for everyday users.
According to the official KB5067036 changelog, the update was supposed to fix Task Manager grouping issues where some applications weren't properly associated with their processes. There's no mention of any other Task Manager modifications, suggesting this multiplication bug was an unintended side effect of that fix.
Microsoft hasn't officially acknowledged the problem yet. The KB5067036 support page still states the company "is not currently aware of any issues with this update," though that's likely to change as reports multiply.
Fortunately, tech-savvy users have already found workarounds. Instead of clicking the standard close button, affected users can terminate Task Manager instances by selecting the "End task" button within the application itself. For those comfortable with command line tools, running 'taskkill /im taskmgr.exe /f' in Command Prompt will forcibly close all running Task Manager instances simultaneously.
