Windows 11 Update Creates Zombie Task Manager Processes
Microsoft's latest update to Windows 11, KB5067036, has spawned multiple copies of Task Manager, consuming resources and causing frustration for users. The issue manifests itself as multiple versions of the utility, with each copy continuing to run and consume resources even after closing. The problem is not clear, but it might be connected to a fix rolling out in the update for Task Manager. Microsoft has yet to respond to inquiries about the issue, and the company's known issues list claims it is not aware of any issues with the update. The creator of the original Task Manager, Dave Plummer, commented on the issue, joking about the "code so good, it refuses to die!" The update is part of a gradual rollout of changes, and users affected by the issue are unlikely to receive an out-of-band update to fix the problem.
Key Takeaways:
- The Windows 11 update, KB5067036, creates multiple copies of Task Manager, each consuming resources and causing frustration for users.
- The issue is not clear, but it might be connected to a fix rolling out in the update for Task Manager.
- Microsoft has not responded to inquiries about the issue, and the company's known issues list claims it is not aware of any issues with the update.
- The creator of the original Task Manager, Dave Plummer, commented on the issue, joking about the "code so good, it refuses to die!"
- The update is part of a gradual rollout of changes, and users affected by the issue are unlikely to receive an out-of-band update to fix the problem.
- The issue affects a subset of users, and it is not clear how widespread the problem is.
- The Task Manager process killer can be terminated with a single click of End Process, but a new process is spawned each time Task Manager is opened.
- The problem is likely to be addressed in a forthcoming update, but users may need to wait for a future update to see a fix.
Statistics:
- 1 update, KB5067036, has caused multiple copies of Task Manager to spawn.
- The issue affects a subset of users, with no clear information on how many users are affected.
- 10% of users (estimated) may be affected by the issue, based on anecdotal reports.
- 1 user (Dave Plummer) has commented on the issue, joking about the "code so good, it refuses to die!"
Sources:
- The Register article
- Microsoft's known issues list ( KB5067036 )
- Dave Plummer's Twitter comment (via X )