Windows 11 users encountered a surprising regression in late October 2025 that left many scratching their heads and their systems bogged down with duplicate processes. The issue, centered around KB5067036, manifested when users closed Task Manager using the window's standard Close (X) button, only to discover that the underlying taskmgr.exe process continued running in the background. This created a cascade effect where repeated use of Task Manager could spawn multiple instances, consuming system resources and potentially impacting performance.

Understanding the Task Manager Duplication Bug

The KB5067036 update, intended to deliver security improvements and system enhancements, inadvertently introduced a process termination flaw in Windows 11's Task Manager. When users closed Task Manager through conventional methods—clicking the X button, pressing Alt+F4, or using the Close option from the title bar menu—the visual interface would disappear while the background process remained active. This created ghost instances that continued to consume memory and CPU cycles without any visible indication to the user.

Microsoft's official documentation for KB5067036 didn't initially acknowledge the Task Manager issue, leaving users to discover the problem through system monitoring or performance degradation. The bug affected multiple Windows 11 versions, including 23H2, 22H2, and various Insider Preview builds, suggesting a fundamental change in how Task Manager handles process termination.

How the Bug Manifests in Daily Use

Users reported several telltale signs of the Task Manager duplication issue. The most common symptom was gradual system slowdown, particularly on systems with limited RAM where multiple Task Manager instances could consume significant memory. Some users noticed the problem when attempting to open Task Manager again and finding it unresponsive or slow to launch, while others discovered the duplicate processes through third-party system monitoring tools.

Power users who frequently accessed Task Manager for system monitoring were particularly affected. Those who used the utility to quickly check resource usage or end unresponsive applications found themselves accumulating multiple taskmgr.exe processes throughout their workday. The issue became more pronounced on systems where users accessed Task Manager multiple times per hour, with some reports indicating up to 10-15 duplicate instances running simultaneously.

Immediate Workarounds and Temporary Solutions

While awaiting official fixes, the Windows community developed several effective workarounds. The most reliable method involved using Task Manager itself to terminate the duplicate processes—though this required users to first identify the issue through careful monitoring.

Manual Process Termination

Users could open Task Manager (despite potential slowness), navigate to the Details tab, locate all taskmgr.exe instances, and manually end each duplicate process. This approach required users to leave at least one instance running to maintain Task Manager functionality.

Alternative Closing Methods

Interestingly, the bug only affected certain methods of closing Task Manager. Users discovered that selecting "End Task" from within Task Manager's interface properly terminated both the window and the background process. Similarly, right-clicking the Task Manager icon in the system tray and selecting "Close window" proved effective at completely terminating the process.

Command Line Solutions

For advanced users, PowerShell and Command Prompt offered more comprehensive solutions. Running taskkill /f /im taskmgr.exe would terminate all Task Manager instances, providing a clean slate. Some users created batch files or PowerShell scripts to automatically detect and remove duplicate Task Manager processes at regular intervals.

Microsoft's Official Response and Patch Timeline

Microsoft acknowledged the Task Manager duplication issue approximately two weeks after user reports began surfacing in significant numbers. The company's initial guidance recommended using the "End Task" method within Task Manager rather than the Close button, while their engineering team worked on a permanent fix.

The resolution arrived with subsequent cumulative updates, particularly KB5067231 and later patches, which addressed the underlying process management issue. Microsoft's patch notes indicated that the fix involved modifying how Task Manager handles its own process termination sequence, ensuring that both the user interface and background process properly close when users initiate shutdown through any method.

Community Discoveries and User Experiences

Windows enthusiasts and IT professionals shared numerous observations about the bug's behavior across different system configurations. Some users noted that the issue appeared more frequently on systems with certain third-party security software installed, suggesting potential conflicts with process monitoring tools. Others observed that the duplication problem seemed less severe on systems with faster storage drives, though this correlation wasn't consistent across all reports.

Several community members developed creative solutions, including small utility applications that would automatically monitor for and terminate duplicate Task Manager processes. These third-party tools provided temporary relief for users who frequently accessed Task Manager throughout their workday.

Best Practices for Task Manager Usage

Following the KB5067036 incident, several best practices emerged for Task Manager usage in Windows 11:

  • Use End Task Instead of Close: When finished with Task Manager, use the "End Task" button within the interface rather than the X button
  • Monitor Background Processes: Periodically check for duplicate taskmgr.exe instances in the Details tab
  • Restart When Suspicious: If Task Manager feels slow or unresponsive, restart it completely by ending all instances and reopening
  • Keep Systems Updated: Ensure Windows 11 receives the latest cumulative updates to prevent known issues

Long-term Implications and System Stability

The Task Manager duplication bug, while relatively minor in isolation, highlighted the importance of thorough testing for seemingly simple system components. Task Manager, being a core Windows utility used by millions daily, demonstrated how even small changes in process management could have widespread impact.

Microsoft's handling of the situation reflected their current approach to Windows updates—rapid identification, temporary workarounds, and systematic patching through the regular update cycle. The incident also underscored the value of community reporting and the collaborative relationship between Microsoft and Windows users in identifying and resolving system issues.

For users, the experience served as a reminder to maintain regular system updates and monitor system performance for unusual behavior, even from trusted system components. The temporary workarounds developed during the KB5067036 issue period remain useful knowledge for troubleshooting other potential process management problems in Windows 11.

As Windows 11 continues to evolve, such incidents provide valuable learning opportunities for both Microsoft and the user community, ultimately contributing to a more stable and reliable operating system experience for all users.