Fix 0XC00D1360 Windows Media Player Download Timeout

Quick answer: Close WMP, delete everything in %windir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\Media Player\ and %windir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\DRM\, restart WMP as admin, then retry the download.

What's going on with this error

You get error 0XC00D1360 when Windows Media Player tries to download a song or video from a subscription service (like a rental or purchased track) but the server doesn't respond in time. This usually happens after you've been using WMP for a while, or after a Windows update changes how network permissions work. The real culprit is almost always a corrupted DRM (Digital Rights Management) store or a stale network connection that WMP can't shake off.

Don't bother reinstalling WMP or running the troubleshooter first. Those waste time. The DRM store gets corrupt from bad shutdowns, antivirus interference, or Windows updates that don't clean up old licenses. Once it's corrupt, WMP waits forever for the server, then times out.

Fix steps

Close Windows Media Player completely. Check Task Manager (Ctrl+Shift+Esc) to make sure no wmplayer.exe or ehshell.exe processes are running. If they are, right-click and end them.
Press Win+R to open the Run dialog. Type %windir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\Media Player\ and hit Enter. This opens a hidden folder. You might see a permissions popup—click Continue.
Select all files and folders inside that folder (Ctrl+A) and delete them. Don't worry, WMP re-creates these as needed. If you get a "file in use" error, reboot Windows and try again from step 1.
Now go to the DRM folder. Press Win+R again and type %windir%\ServiceProfiles\LocalService\AppData\Local\Microsoft\DRM\. Hit Enter. Delete everything inside this folder too. After deleting, you should see an empty folder (or just a hidden desktop.ini file).
Reboot your computer. This is not optional. It clears any cached network handles the DRM store was holding onto.
After reboot, open Windows Media Player as administrator: right-click its shortcut and select "Run as administrator." Accept the UAC prompt.
Go to the Library tab and try downloading the same item again. The download should start immediately. If it doesn't, move to the alternative fixes below.

Alternative fixes if the main one doesn't work

Reset network stack

If the DRM store reset didn't help, your network stack might have stale DNS or proxy settings. Open Command Prompt as administrator (right-click Start > Command Prompt (Admin) or Terminal (Admin)) and run these commands one at a time:

netsh int ip reset
netsh winsock reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew

After each command you'll see a confirmation message. Reboot after running all four.

Check proxy and firewall

Some antivirus tools (especially Norton and McAfee) block WMP's DRM requests. Temporarily disable your real-time protection and try the download again. Also go to Internet Options (search "Internet Options" in Start), click the Connections tab, then LAN settings. Make sure "Automatically detect settings" is checked and the proxy fields are blank unless you know you need a proxy.

Re-register WMP components

Open Command Prompt as admin and run:

regsvr32 wmp.dll
regsvr32 wmpdxm.dll
regsvr32 wmpps.dll

You'll get a success message for each. Then restart WMP.

How to stop this from happening again

The main trigger for this error is a Windows update that changes network permissions without cleaning old DRM files. To avoid it, always let Windows updates finish completely before using WMP. Also, don't force-close WMP while it's downloading—use the Stop button instead. If you use a third-party antivirus, add WMP to its exclusion list under "allowed programs."

One more tip: if you're on a metered connection (like mobile hotspot), WMP's subscription service might time out because Windows throttles background downloads. Turn off metered connection detection in Settings > Network & Internet > Properties for your Wi-Fi.

This fix works for Windows 10 build 1909 and later, and Windows 11 all versions. It also fixes error 0xC00D11B1 and 0xC00D11B2, which are related timeout codes.