0XC00D1126: Windows Media Player offline error fix
NS_E_WMPIM_USEROFFLINE shows when WMP can't reach the internet even if you're online. It's usually a proxy or firewall block.
When this error hits
You're trying to stream or sync media in Windows Media Player on Windows 10 (version 21H2 or later) or Windows 11, and suddenly you see the error: NS_E_WMPIM_USEROFFLINE (0XC00D1126) with the message "Windows Media Player has detected that you are not connected to the Internet". Yet your browser works fine. You can watch YouTube or check email. But WMP insists you're offline. It's infuriating, I know. I've seen this on corporate laptops with strict VPNs and on home machines with aggressive security suites.
What's actually happening
WMP uses the WinHTTP stack to check internet connectivity, not the standard WinINet that browsers use. WinHTTP is more sensitive to proxy misconfigurations and firewall blocks. If you've got a proxy set in Internet Options (like a corporate proxy or a tool like Fiddler), or your firewall is blocking WMP's outbound port 80/443, you'll get this error even when everything else works. Another common trigger: third-party VPNs or security software (e.g., Norton, McAfee, or even some antivirus suites) that isolate WMP's process from the network.
Fix it in 5 steps
Skip the obvious restart—that rarely helps here. Do these in order.
1. Disable the proxy for local addresses
Open Internet Options (search for it in Start or run inetcpl.cpl). Go to the Connections tab, click LAN settings. Uncheck "Use a proxy server for your LAN". If you need the proxy for work, leave it checked but also check "Bypass proxy server for local addresses". Click OK, then apply. Restart WMP.
2. Reset WinHTTP proxy
Open Command Prompt as Administrator (right-click Start > Terminal Admin). Run:
netsh winhttp reset proxyThis clears any proxy stored at the system level. On Windows 11 22H2 and later, this is often the real fix. If you're on a corporate network, you might need to re-run this after VPN connects. I'd add a batch script to do it automatically if you toggle VPN often.
3. Check Windows Firewall
Press Windows + R, type wf.msc, hit Enter. Look for inbound rules blocking wmplayer.exe. Right-click and disable any block rule. Also check outbound rules—some security suites create hidden rules that block WMP specifically. If you see it, turn it off temporarily to test. If that fixes it, permanently delete the rule.
4. Flush DNS and reset Winsock
This is a shotgun approach, but it works when network isolation occurs due to corrupted socket state. In the same Admin Command Prompt:
ipconfig /flushdns
netsh winsock resetThen restart your PC. WMP will rebuild its network stack.
5. Exclude WMP in your security software
If you use Norton 360, McAfee Total Protection, or even Windows Defender's tamper protection (which is rare but happens), add C:\Program Files\Windows Media Player\wmplayer.exe to the exclusion list. This prevents the security suite from isolating WMP's network access. On Defender, go to Virus & threat protection > Manage settings > Add or remove exclusions.
If it still fails
Check if you're behind a captive portal (like hotel Wi-Fi or a guest network). WMP can't handle those. Temporarily connect your phone's hotspot to bypass. Also verify your date/time is correct—WinHTTP uses certificates for connectivity checks, and a skewed clock breaks them. If all else fails, run sfc /scannow and then DISM /Online /Cleanup-Image /RestoreHealth to repair any corrupted system files. And if you're on Windows 10 N (the EU version without Media Player), you'll need to install the Media Feature Pack from Microsoft's website—that version literally lacks the networking components WMP needs.
Was this solution helpful?