Fix ERROR_SEM_NOT_FOUND (0x000000BB) on Windows 10/11

You saw 0x000000BB and thought, 'What now?'

I know this error is infuriating. It usually pops up when you're trying to run an older application or a driver installer, and suddenly everything grinds to a halt. The error message says the system semaphore name wasn't found. That's a fancy way of saying something's messed up with how Windows manages shared resources. Let's fix it.

The quick fix: Reboot and reinstall the problematic app

This sounds like a cliché, but it works more often than not. A semaphore is a kernel object that coordinates access to shared memory. If a program or driver left a stale semaphore handle, or the name got corrupted, a reboot clears the slate. Here's what I do:

1. Close all running applications.
2. Restart your PC. Not a shutdown and power-on—a proper restart (Start > Power > Restart). Windows 10 and 11 differ slightly in how they handle 'Fast Startup,' so a restart is better.
3. After the reboot, uninstall the application that triggered the error. Go to Settings > Apps > Apps & features, find the app, and uninstall it.
4. Reinstall the app from the official source. If it's an old game or a legacy driver, make sure you're using the version compatible with your OS build.

If the error disappears, you're done. But if it persists, we need to dig deeper.

Why this happens: The semaphore name is just a string

Semaphores in Windows are named kernel objects—like 'Global\MyApp_Semaphore'. The kernel maintains a table of these names. When an app calls CreateSemaphore or OpenSemaphore with a name that doesn't exist, you get error 0x000000BB. Common triggers include:

• A program that crashed and left a corrupted handle in memory.
• Antivirus software (like Norton or McAfee) interfering with object creation.
• A driver that failed to install correctly, especially older printers or VPN clients.
• Running a 32-bit app on a 64-bit system where the semaphore namespace gets redirected (the 'Global\' prefix issue).

I once saw this on a Windows 10 machine with a 2012-era Cisco VPN client. The driver created a semaphore with a very specific name, but a Windows update changed the namespace redirection. The fix? Update the VPN client to a newer version.

Less common variations: When the app isn't the culprit

1. Antivirus blocking kernel object creation

Some aggressive antivirus suites, especially those with 'behavior monitoring,' block semaphore creation as a false positive. You can test this by temporarily disabling real-time protection. If the error stops, add the program's folder to your antivirus exclusions.

2. Corrupted system files

If a system file that manages kernel objects (like ntoskrnl.exe) is corrupted, you'll see this error across multiple apps. Run these commands in an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

This fixes the Windows image and then scans for file corruption. It takes 10-15 minutes, and you may need to reboot afterward.

3. Driver conflicts from old hardware

I've seen this error with older sound cards or USB controllers that use custom drivers. Go to Device Manager, find the device (look for yellow exclamation marks), right-click and select 'Update driver' > 'Browse my computer for drivers' > 'Let me pick from a list' and choose the basic Microsoft driver. If that fixes the error, the custom driver was the problem. You can then check the manufacturer's site for an updated version.

4. Registry corruption in semaphore-related keys

This is rarer, but the semaphore object names are stored under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\ObjectDirectories. If a key is missing or has wrong permissions, apps can't create or open semaphores. You can use Process Monitor to trace which object the failing app is trying to open, then check that directory key. Usually, a system restore point from before the issue started is a safer fix than editing the registry.

Prevention: Keep your drivers and apps current

The best way to avoid 0x000000BB is to not let your system get stale. I've learned this the hard way. Set Windows Update to install driver updates automatically. For older apps, run them in compatibility mode for the OS they were designed for (right-click the exe > Properties > Compatibility > Run this program in compatibility mode for Windows 7 or 8). Also, avoid using 'kernel-level' antivirus software—Windows Defender is good enough for 99% of users. And if you're troubleshooting, always restart before uninstalling. That alone has saved me hours.

If none of this works, you might be dealing with a hardware issue—faulty RAM can corrupt kernel objects. Run a memory test (Windows Memory Diagnostic tool) to be sure. But in 80% of cases, the reboot or reinstall does the trick. Good luck.