ERROR_THREAD_WAS_SUSPENDED (0X000002BB) Fix: Thread Suspended at Termination

Cause #1: Antivirus or security software suspending system threads

This is the most common trigger I've seen across hundreds of help desk tickets. Antivirus programs — especially third-party ones like McAfee, Norton, or even some Avast versions — can intercept thread operations. When your system tries to terminate a thread that the antivirus has suspended (usually during a scan or real-time protection check), Windows throws ERROR_THREAD_WAS_SUSPENDED (0X000002BB).

I know this error is infuriating because it can pop up during normal shutdown or when closing a program. It tripped me up the first time too: I spent hours chasing driver issues before realizing my antivirus was the problem.

How to fix it

1. Temporarily disable real-time protection — In Windows Security, turn off real-time scanning. Reboot and see if the error returns. If it doesn't, your AV is the culprit.
2. Remove third-party antivirus completely — Use the official removal tool for your AV (e.g., McAfee Consumer Product Removal Tool). Don't just uninstall through Settings — that often leaves drivers behind. Then restart.
3. Stick with Windows Defender — Microsoft's built-in solution rarely causes thread suspension issues. I recommend it unless you have a specific corporate policy requiring another AV.

Cause #2: Corrupted or conflicting device drivers

Drivers — especially for network adapters, graphics cards, and USB controllers — sometimes suspend threads during power transitions. If the error appears when you plug in a USB device or wake your PC from sleep, suspect the driver stack. This is more common on Windows 11 22H2 and later builds.

Here's the real fix: update the problematic driver without relying on Windows Update alone.

Steps

1. Open Device Manager (devmgmt.msc).
2. Look for any device with a yellow exclamation mark. Expand Network adapters, Display adapters, and Universal Serial Bus controllers.
3. Right-click each device and select Update driver → Browse my computer for drivers → Let me pick from a list of available drivers. Choose the most recent one.
4. If that doesn't work, download the driver directly from the manufacturer's site (Intel, NVIDIA, Realtek, etc.) — not from Microsoft's catalog. Reboot after each update.

Skip the automatic driver update tools; they often install generic drivers that cause more thread suspensions than they fix.

Cause #3: Buggy third-party services or shell extensions

Services that hook into system processes — like cloud sync tools (Dropbox, OneDrive), mouse or keyboard customization software (Logitech Options, Corsair iCUE), or even older Adobe background services — can suspend threads during termination. I've seen this error spike with Logitech G Hub on Windows 11.

Diagnostic approach

1. Open Task Manager (Ctrl+Shift+Esc), go to the Startup tab, and disable all non-Microsoft services. Restart.
2. If the error disappears, re-enable services one by one until the error returns. That's your offender.
3. For software like iCUE or Logitech Options, check for an update or switch to a lighter alternative (like OpenRGB for lighting, or just use Windows default mouse settings).

One more thing: run sfc /scannow from an elevated Command Prompt. It rarely fixes thread suspension errors directly, but it does catch corrupted system files that might contribute to instability. Won't hurt, might help.

Quick-reference summary

Still stuck? Drop the exact trigger scenario in the comments — waking from sleep? Closing a game? That context helps pinpoint the fix faster. Good luck!