STATUS_CTX_INVALID_MODEMNAME 0xC00A0009 Fix

What's Happening Here

You're trying to start a Remote Desktop session and get STATUS_CTX_INVALID_MODEMNAME (0xC00A0009). The message says "The modem (%1) was not found in the MODEM" — which is Microsoft's way of admitting it's looking for a modem driver or device that doesn't exist anymore. This doesn't mean you need a modem. It means some leftover config from an old dial-up connection or a third-party RDP wrapper is confusing the Terminal Services client.

I've seen this most often after someone installs a remote-access tool like LogMeIn or TeamViewer and then uninstalls it badly, or after a Windows upgrade that mangles the registry. The fix is surgical: remove the phantom modem reference.

30-Second Fix: Check Your Remote Desktop Client Version

Before you dive into registry surgery, make sure you're not running an ancient RDP client. Microsoft broke modem handling in older versions, and a simple update can wipe the error.

1. Open Settings > Apps > Optional features.
2. Scroll to Remote Desktop Connection and click Uninstall.
3. Reboot, then go back to Optional features and click Add a feature.
4. Search for "Remote Desktop Connection", check it, and install.

This re-registers the RDP client from scratch. It wipes any stale modem entries. If the error persists, move on.

5-Minute Fix: Delete the Modem Registry Key

The real culprit is almost always a registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\Modem. That key tells RDP to use a specific modem device name. If the device is gone, you get the 0xC00A0009 error.

1. Press Win + R, type regedit, hit Enter.
2. Navigate to:
   Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns
3. Right-click the Modem subkey and choose Delete.
4. Close Regedit and reboot.

The reason this works: without the Modem key, the Terminal Services client falls back to its default behavior — no modem reference, no error. You don't lose any RDP settings; cached server lists stay in HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client, which isn't touched.

15-Minute Fix: Check for Stale Dial-Up Connections

If the registry key isn't there or deleting it didn't help, the modem name could be embedded in a network adapter's properties. This happens if you had a dial-up connection or a VPN that created a fake modem device.

1. Open Control Panel > Network and Sharing Center > Change adapter settings.
2. Look for any connection named something like "Remote Access", "VPN", or "Dial-up". Right-click it and choose Properties.
3. Under Networking tab, check if Remote Desktop Services is listed. If so, uncheck it.
4. Also check for any modem devices in Device Manager under Modems. If you see one you don't use, right-click and Uninstall device.

What's happening here is that RDP binds to any available modem-like device. Even if you don't have a physical modem, a software modem from an old VPN client can confuse it. Removing those bindings kills the error at the source.

Still Stuck? Nuke the RDP Configs

If you've done all three steps and still see the error, someone's got a corrupted RDP session file or a group policy forcing a modem. Try this nuclear option:

1. Open File Explorer and go to %USERPROFILE%\Documents\. Delete all .rdp files there.
2. Open Regedit and delete the key HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers. This wipes your saved server list. You'll have to re-enter them, but it's worth it.
3. Run gpedit.msc (Pro/Enterprise only) and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. Look for any policy that mentions "modem" and disable it.

The 0xC00A0009 error is almost never a real hardware problem. It's a config ghost. Exorcise it with the steps above and you'll be back to RDP in minutes.