STATUS_NOINTERFACE 0XC00002B9 – Fix in 3 Steps

What's Going On

STATUS_NOINTERFACE (0XC00002B9) pops up when an application or system component asks for a COM interface that isn't registered or available. Happens a lot with Windows Media Player, Outlook, or Visual Studio after a bad update or DLL swap. Some gaming launchers trigger it too. The culprit here is almost always a missing or corrupt COM registration, not hardware.

Fix 1 – Quick Registry Tweak (30 seconds)

Don't bother reinstall the app yet. Try this first – it works about 40% of the time.

1. Press Win + R, type regedit, hit Enter.
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Right-click empty space, choose New > DWORD (32-bit) Value.
4. Name it EnableLUA. Set it to 0.
5. Restart your PC.

This disables UAC temporarily. Some COM interfaces break under UAC when the app isn't elevated. After the restart, try the app that gave the error. If it works, you can keep UAC off or set it back to 1 and move to Fix 2.

Fix 2 – Re-Register COM Components (5 minutes)

If the registry tweak didn't fix it, the COM database itself is likely corrupt. Let's rebuild it.

1. Open an elevated Command Prompt (right-click Start, choose Command Prompt Admin or Windows Terminal Admin).
2. Run these commands one by one. Wait for each to finish before the next:

regsvr32 /u vbscript.dll
regsvr32 vbscript.dll
regsvr32 /u jscript.dll
regsvr32 jscript.dll
regsvr32 /u scrrun.dll
regsvr32 scrrun.dll
regsvr32 /u msxml3.dll
regsvr32 msxml3.dll

This re-registers common scripting DLLs that host COM interfaces. The /u flag unregisters first to clear stale entries. Then re-registers fresh. Restart and test.

Still broken? Most likely the COM+ catalog is hosed. Run this command:

sfc /scannow

Let it finish. If it finds corrupt files, run it twice. Then try dism /online /cleanup-image /restorehealth. After that, reboot.

Fix 3 – Rebuild COM+ Catalog (15+ minutes)

This is the nuclear option. Use it when you see the error in Event Viewer under Component Services or DCOM errors.

1. Close all open apps that use COM (browsers, Office, etc.).
2. Open an elevated Command Prompt.
3. Stop the COM+ services:

net stop COMSysApp
net stop MSDTC

4. Delete the COM+ catalog file. Yes, you're deleting the database. Windows will rebuild it on next boot. Navigate to C:\Windows\System32\com\ and delete complus.dat (or rename it to complus.old if you're nervous).
5. Restart the services:

net start MSDTC
net start COMSysApp

6. Reboot the machine.

After reboot, Windows regenerates the COM+ catalog from scratch. You'll lose any custom COM+ applications you built, but normal apps work fine.

If the error still shows up, your system files are beyond repair. Time for a repair install using the Windows Media Creation Tool. Not a full wipe – do an in-place upgrade. Takes about an hour, keeps your files and apps, but replaces all system binaries.

When to Give Up and Reinstall

If none of these work, the root cause is likely a third-party driver or shell extension that pollutes the COM namespace. Use Autoruns from Sysinternals to disable non-Microsoft shell extensions and COM objects one by one. Or just nuke and pave – sometimes it's faster.

Pro tip: Before you delete anything, export the registry key HKEY_CLASSES_ROOT\Interface and HKEY_CLASSES_ROOT\CLSID. You can restore them if things go sideways.