Yeah, This Error Is Annoying
You try to kill a stuck process, and Windows throws up STATUS_NOTHING_TO_TERMINATE (0x00000122). I've been there. It feels like the OS is gaslighting you—saying there's nothing to terminate while the process still shows in Task Manager. Let's fix it.
The Quick Fix: Force the Handle
The real culprit is often a handle leak or an orphan thread that the kernel can't clean up. The fastest way out is using Process Explorer (from Microsoft's Sysinternals suite). Don't bother with Task Manager—it won't help here.
- Download Process Explorer
- Run it as Administrator (right-click → Run as administrator)
- Find the process that's stuck (look for a yellow or red highlight—those are your problem children)
- Right-click the process → Kill Process
- If that still gives you 0x00000122, right-click again → Properties → Threads tab
- You'll likely see zero threads. That's the error in action.
- Right-click again → Suspend → wait 2 seconds → then Resume → then Kill Process
That suspend-resume trick forces the kernel to re-evaluate the thread state. I've seen it work on Windows 10 22H2 and Windows 11 23H2. No reboot required.
Why This Happens (The Short Explanation)
Every Windows process needs at least one thread to be terminable. When a thread exits abnormally—say from a buggy driver, a corrupted heap, or a race condition—the process object gets orphaned. The kernel sees the process handle but can't find any threads to signal. So it hands you 0x00000122 and walks away.
This is common after:
- A driver update that borks something (especially graphics drivers)
- A Windows Update that didn't finish cleanly
- Running a legacy 16-bit application (yes, some people still do)
- Antivirus software hooking into process creation
Less Common Variations
1. The Service Won't Die
Sometimes it's a Windows service. Use sc queryex [service name] in an elevated Command Prompt. If it shows a PID but no threads, run taskkill /f /pid [PID]. If that fails, use sc stop [service name] then sc delete [service name] if you're done with it.
2. The Orphaned Handle in Registry
This one's rare but nasty. A process holds a registry key open and dies. The key stays locked. Open Regedit, go to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager, and look for PendingFileRenameOperations. If it's populated with a file path from the dead process, clear the value. Reboot.
3. Graphics Driver Hang
If the stuck process is a game or a GPU-heavy app, the graphics driver might have left a thread hanging. Run DDU (Display Driver Uninstaller) in Safe Mode, then reinstall the latest driver from your GPU vendor. Don't use Windows Update drivers—they're garbage for this.
Prevention (Because You Don't Want This Again)
- Keep drivers updated—especially chipset and graphics. Use the manufacturer's site, not Windows Update.
- Avoid forced shutdowns. When you hold the power button, you risk leaving threads in limbo.
- Run CHKDSK periodically. Corrupted files can cause thread creation failures.
chkdsk /f /ronce a quarter. - Use Sysinternals tools for advanced troubleshooting. They're free, official, and better than anything else.
- If you see this error repeatedly on the same app, report it to the vendor. It's almost always a bug in their code.
That's it. The suspend-resume trick in Process Explorer is your best friend here. Try it before you restart—you'll save yourself a login cycle.