Windows 11 24H2/25H2 Update Causes Task Manager To Stay Running After Close

Microsoft’s latest preview update for Windows 11 has introduced an unexpected glitch that’s frustrating users worldwide.

Released on October 28, 2025, as KB5067036 for OS Builds 26200.7019 and 26100.7019, this non-security patch targets versions 24H2 and 25H2.

Designed to enhance functionality, performance, and reliability, it instead leaves the Task Manager process running in the background even after users attempt to close it.

Reports from early adopters highlight this issue, which could lead to unnecessary resource drain and system instability.

The update rolls out in phases a gradual rollout to select devices followed by a normal broad release.

It includes updates to AI components like Image Search, Content Extraction, Semantic Analysis, and Settings Model, all bumped to version 1.2510.1152.0.

Additionally, it bundles a servicing stack update (KB5067035) to streamline future installations.

Microsoft emphasizes that these changes aim to deliver smoother AI-powered experiences on Copilot+ PCs, but the Task Manager bug has overshadowed these improvements.

The Bug In Detail

Users notice the problem immediately after installing KB5067036. When they invoke Task Manager via Ctrl+Shift+Esc or the taskbar and then close it, the process taskmgr.exe persists in the background.

This can be verified by reopening Task Manager or using tools like Process Explorer.

The glitch stems from incomplete cleanup in the update’s window management code, potentially tied to enhanced multitasking features in 25H2.

While not a security risk, it hogs CPU cycles and memory, especially on systems with multiple open applications.

Microsoft acknowledges known issues in the release notes, though specifics on this Task Manager quirk remain sparse.

Early feedback on forums like Reddit and Microsoft Community points to it affecting both x64 and ARM-based devices.

No widespread crashes have been reported, but prolonged background activity might exacerbate battery life concerns on laptops.

Workarounds And Fixes

For now, affected users can manually end the taskmgr.exe process through another instance of Task Manager or via Command Prompt with the command “taskkill /f /im taskmgr.exe.”

Restarting Explorer.exe or rebooting the system provides temporary relief. Microsoft advises holding off on installation until a follow-up patch arrives, expected in the next monthly cycle.

As Windows 11 evolves with AI integrations, such teething issues remind users of the risks in preview updates.

Check the Windows release health dashboard for ongoing status. This bug underscores the importance of testing before full deployment in enterprise environments.