0XC00D000C

Fix NS_E_NOFUNNEL (0XC00D000C) – No Data Connection in Windows Media Center

Network & Connectivity Beginner 👁 0 views 📅 Jun 8, 2026

This error hits when Windows Media Center can't fetch guide data or stream. The fix is simple: reset the Media Center database and check your network.

If you're staring at the NS_E_NOFUNNEL error in Windows Media Center, I feel your pain. It's one of those cryptic messages that makes you want to throw the remote through the screen. But here's the thing—it's almost always fixable without reinstalling Windows or calling a priest.

The Quick Fix: Reset the Media Center Database

This is the #1 cause. Media Center's database gets corrupted or stuck on bad guide data. I've seen this more times than I've seen blue screens on a Tuesday. Here's what to do:

  1. Close Media Center completely.
  2. Hit Windows Key + R, type cmd, and press Enter.
  3. In the command prompt, run this:
    mcupdate.exe -database -reset
  4. Wait for it to finish—could take 30 seconds to 2 minutes. You'll see no confirmation, just the prompt returns.
  5. Open Media Center again. It'll rebuild the database from scratch. Give it a minute to re-download guide data.

If that doesn't cut it, open Media Center, go to Settings > General > Windows Media Center Setup > Reset to Default. Yes, you'll lose your recording schedules and tuner settings, but it's a total reset. Write your settings down first if you're picky.

Why This Works

The NS_E_NOFUNNEL error basically means Media Center can't establish a data connection to Microsoft's guide servers or your network. The database reset wipes out any corrupted or stale metadata that's blocking the handshake. I've had a client whose guide data was stuck on a three-month-old schedule because of a botched update. Reset fixed it instantly.

The "Reset to Default" option goes further—nukes everything and forces a fresh setup. Use that if the command-line reset doesn't do the trick.

What If That Doesn't Work? Check the Network

Sometimes the problem isn't the database—it's your router or firewall. Media Center uses ports 80, 443, and 7777 to fetch guide data and streams. If you're behind a corporate firewall or a cheap router that blocks outbound connections, you'll get this error.

Quick test: from the same PC, open Internet Explorer and go to http://services.mediacenter.microsoft.com. If that page doesn't load, your network's the issue. Try these:

  • Disable your firewall temporarily (just to test). If it works, add an exception for Media Center.
  • Reboot your router. Seriously, I've seen DNS caching cause this. Unplug it for 30 seconds.
  • Run ipconfig /flushdns in command prompt.
  • Set your DNS server to Google's (8.8.8.8 and 8.8.4.4) if your ISP's DNS is flaky.

The Less Common Culprit: Corrupted Media Center Installation

I've run into this a few times—a Windows update or a third-party codec pack breaks Media Center's internals. The error pops up even after database resets and network checks. This is rare, but it happens.

Fix: uninstall Media Center via Control Panel > Programs and Features > Turn Windows features on or off. Uncheck Media Features > Windows Media Center, reboot, then re-check it and reboot again. This re-registers the core components without touching your personal files.

If you're on Windows 8 or 10 (where Media Center was a paid add-on), you might need to reinstall the Media Center pack. On Windows 7, it's built-in, so the feature toggle works fine.

How to Prevent This From Happening Again

  • Keep Windows updated. Microsoft patched guide-related bugs in some updates. I've seen a specific KB update (KB3068708) cause issues, but later patches fixed it.
  • Don't use Media Center on a machine that goes to sleep or hibernates overnight. Guide data downloads fail silently, and the database gets stale. Set power settings to never sleep.
  • If you use third-party firewalls like ZoneAlarm or Norton, make sure Media Center is in the allowed apps list. Those suites love blocking background services.
  • Rebuild the database every 3-6 months as maintenance. Run mcupdate.exe -database -reset even if everything's fine—it's quick and prevents corruption.

That's it. If none of this works, your PC might have deeper issues—bad hard drive sectors where the database lives, or a failing network card. But for 95% of cases, the database reset or network check gets you back to watching TV. No need to panic.

Was this solution helpful?