With the recent rollout of the Windows 11 November 2025 Update (Build 26200.7171/26100.7171 or newer), Microsoft has successfully addressed a perplexing issue that plagued users: the Task Manager’s inability to close properly when the Close (X) button was clicked. This glitch led to significant performance degradation, particularly for those managing numerous Task Manager processes, each consuming valuable RAM and CPU resources.
In a series of tests conducted by Windows Latest, the problematic behavior of the Task Manager was first observed following the installation of the October optional update (KB5067036). This update inadvertently caused multiple invisible instances of the Task Manager (taskmgr.exe) to accumulate in the background, further straining system performance.
What went wrong with the Task Manager?
After applying the October 2025 Update, Windows Latest identified that in 30 out of 100 virtual machines, the Task Manager process remained active even after being closed. Each attempt to reopen the Task Manager resulted in a new visible instance while the previous one lingered, contrary to the expected behavior of having only one active instance at any time.
Our tests revealed that each hidden Task Manager instance consumed approximately 20-25 MB of RAM and utilized around 0 to 1.5% of CPU resources. For users who frequently access the Task Manager throughout the day, this accumulation could lead to noticeable declines in system performance, particularly on lower-end hardware configurations with 8GB or 16GB of RAM, which are often already taxed by demanding workflows.
What caused the ghost Task Manager instance issue?
The October update, KB5067036, was intended to fix a grouping issue within the Task Manager that incorrectly associated some applications with their respective processes. For instance, Spotify-related processes were mistakenly grouped under File Explorer. While this was a nuisance, Microsoft managed to address it in the optional update. However, the fix inadvertently caused the Task Manager to remain active in the background when closed, rather than terminating as intended.
Microsoft later corroborated the findings from Windows Latest, issuing a statement that highlighted the issue: “After installing Windows Updates released on or after October 28, 2025 (KB5067036), you might encounter an issue where closing Task Manager using the Close (X) button does not fully terminate the process…This results in multiple lingering instances of taskmgr.exe, consuming system resources and potentially degrading device performance.” The company noted that while occasional openings and closings of the Task Manager would not significantly impact performance, a buildup of instances could lead to noticeable slowdowns in other applications.
This was evidenced by our tests at Windows Latest, where we opened the Task Manager 500 times, confirming that each instance remained active and continued to draw from system resources.
Microsoft confirms it fixed the duplicate Task Manager bug, and our tests verify the fix is working
In a follow-up statement, Microsoft assured users that the Task Manager should no longer adversely affect performance in certain scenarios. The resolution is included in the November update KB5068861 (OS builds 26200.7171 or 26100.7171), which effectively restores the expected functionality of the Task Manager.
Post-update tests conducted by Windows Latest indicated that the Task Manager now closes as intended when the “X” button is clicked, eliminating the ghost processes that previously plagued users. For those who have yet to install the November update, it is advisable to do so to avoid the lingering Task Manager instances.
To check for the ghost instance issue, users can press Ctrl+Shift+Esc to open the Task Manager, click the Close (X) button, and then reopen it to see if multiple instances appear in the Processes tab. If the count increases with each reopening, it’s a clear indication of the bug’s presence.
For those hesitant to install the update, manually terminating each instance via “End Process” is not an efficient use of time. Additionally, the November update introduces several new features, including a fully customizable Start menu, new colored battery indicators, and a variety of other enhancements and fixes.
Have you encountered any new issues following the November 2025 Update? We welcome your feedback in the comments below.
Tested: The Task Manager bug that slowed your PC is gone in Windows 11 Build 26200.7171
With the recent rollout of the Windows 11 November 2025 Update (Build 26200.7171/26100.7171 or newer), Microsoft has successfully addressed a perplexing issue that plagued users: the Task Manager’s inability to close properly when the Close (X) button was clicked. This glitch led to significant performance degradation, particularly for those managing numerous Task Manager processes, each consuming valuable RAM and CPU resources.
In a series of tests conducted by Windows Latest, the problematic behavior of the Task Manager was first observed following the installation of the October optional update (KB5067036). This update inadvertently caused multiple invisible instances of the Task Manager (taskmgr.exe) to accumulate in the background, further straining system performance.
What went wrong with the Task Manager?
After applying the October 2025 Update, Windows Latest identified that in 30 out of 100 virtual machines, the Task Manager process remained active even after being closed. Each attempt to reopen the Task Manager resulted in a new visible instance while the previous one lingered, contrary to the expected behavior of having only one active instance at any time.
Our tests revealed that each hidden Task Manager instance consumed approximately 20-25 MB of RAM and utilized around 0 to 1.5% of CPU resources. For users who frequently access the Task Manager throughout the day, this accumulation could lead to noticeable declines in system performance, particularly on lower-end hardware configurations with 8GB or 16GB of RAM, which are often already taxed by demanding workflows.
What caused the ghost Task Manager instance issue?
The October update, KB5067036, was intended to fix a grouping issue within the Task Manager that incorrectly associated some applications with their respective processes. For instance, Spotify-related processes were mistakenly grouped under File Explorer. While this was a nuisance, Microsoft managed to address it in the optional update. However, the fix inadvertently caused the Task Manager to remain active in the background when closed, rather than terminating as intended.
Microsoft later corroborated the findings from Windows Latest, issuing a statement that highlighted the issue: “After installing Windows Updates released on or after October 28, 2025 (KB5067036), you might encounter an issue where closing Task Manager using the Close (X) button does not fully terminate the process…This results in multiple lingering instances of taskmgr.exe, consuming system resources and potentially degrading device performance.” The company noted that while occasional openings and closings of the Task Manager would not significantly impact performance, a buildup of instances could lead to noticeable slowdowns in other applications.
This was evidenced by our tests at Windows Latest, where we opened the Task Manager 500 times, confirming that each instance remained active and continued to draw from system resources.
Microsoft confirms it fixed the duplicate Task Manager bug, and our tests verify the fix is working
In a follow-up statement, Microsoft assured users that the Task Manager should no longer adversely affect performance in certain scenarios. The resolution is included in the November update KB5068861 (OS builds 26200.7171 or 26100.7171), which effectively restores the expected functionality of the Task Manager.
Post-update tests conducted by Windows Latest indicated that the Task Manager now closes as intended when the “X” button is clicked, eliminating the ghost processes that previously plagued users. For those who have yet to install the November update, it is advisable to do so to avoid the lingering Task Manager instances.
To check for the ghost instance issue, users can press Ctrl+Shift+Esc to open the Task Manager, click the Close (X) button, and then reopen it to see if multiple instances appear in the Processes tab. If the count increases with each reopening, it’s a clear indication of the bug’s presence.
For those hesitant to install the update, manually terminating each instance via “End Process” is not an efficient use of time. Additionally, the November update introduces several new features, including a fully customizable Start menu, new colored battery indicators, and a variety of other enhancements and fixes.
Have you encountered any new issues following the November 2025 Update? We welcome your feedback in the comments below.