Key Takeaways
1. The KB5067036 update for Windows 11 causes Task Manager to clone itself instead of closing when the “X” button is clicked, leading to multiple instances running in the background.
2. Each additional Task Manager instance consumes memory, which can slow down system performance.
3. Users can check if they’re affected by opening Task Manager and closing it with the “X” button to see if another instance appears.
4. The temporary workaround is to avoid the “X” button and instead use “End Task” or the command “taskkill /im taskmgr.exe /f” in the command prompt to close Task Manager.
5. Microsoft has not yet acknowledged this bug, despite it being verified by users.
Microsoft’s Preview KB5067036 update for Windows 11 appears to have created a strange glitch that leads to multiple Task Manager instances running behind the scenes when you close it with the “X” button.
Bug Replication
According to Windows Latest, each time you click the “X” button to exit Task Manager, it merely clones itself. This creates an additional background process that eats up memory and could cause performance slowdowns.
We verified this on a test machine and confirmed that the bug is still present. Microsoft has not yet recognized this problem.
How to Check
To find out if you’re impacted by this glitch, you can open Task Manager by right-clicking on the taskbar and choosing Task Manager, or by using the Ctrl+Shift+Esc combo on the keyboard, or the Ctrl+Alt+Del shortcut and selecting Task Manager from the list.
Once you’re in, close the application using the “X” button and see if another instance appears in the running processes. If you frequently open Task Manager to monitor processes, this could lead to performance drawbacks since each instance consumes a bit of RAM, and that can accumulate quickly.
Workaround Solutions
Currently, the only temporary fix seems to be avoiding the “X” button and instead manually right-clicking on each Task Manager process to choose “End Task” for closing it. You can also execute the taskkill command by typing taskkill /im taskmgr.exe /f into the command prompt.
Recently, Microsoft rolled out an emergency update this month that resolved issues with USB devices not being recognized in the Windows Recovery Environment.
Source:
Link
















