Overview
- Closing Task Manager with the X button hides the window but leaves the process running, and reopening creates additional instances.
- Each orphaned instance typically consumes about 20–25MB of RAM and can use up to roughly 1.5% CPU, leading to cumulative performance hits.
- Temporary fixes include ending Task Manager from within Task Manager or running the command taskkill /im taskmgr.exe /f in an elevated prompt.
- Microsoft has not acknowledged the issue, and the KB5067036 notes still state there are no known problems with the update.
- KB5067036 was released on October 28 as an optional Windows 11 preview with Start menu changes and a Task Manager grouping fix, and users can avoid the bug by not installing it.