Fix NS_E_PUBLISHING_POINT_STOPPED (0XC00D145E) on Windows Media Services

1. The Permissions Problem (Most Common)

Nine times out of ten, NS_E_PUBLISHING_POINT_STOPPED happens because the Windows Media Services (WMS) service account doesn't have read access to the content folder. You’ll see this after moving content to a new drive or folder. The service just stops the publishing point dead — no warning, no retry.

Fix it: Check the service account for WMS. Open services.msc, find Windows Media Services, go to the Log On tab. Default is NT AUTHORITY\NETWORK SERVICE. If someone changed it to a domain account, that account needs explicit read permissions on the content folder.

For the default account, open the content folder (e.g., C:\WMPub\WMRoot), right-click → Properties → Security. Add NT AUTHORITY\NETWORK SERVICE with Read & execute and List folder contents. Apply, restart the WMS service, try again.

Still broken? Check the physical path

Open IIS Manager → Windows Media Services → your publishing point. Right-click → Properties → Source. The Content directory must be a real, accessible path. No trailing spaces, no network drives that require a different set of credentials. If it’s a UNC path (\server\share), the service account must have share-level AND NTFS-level read access. I’ve seen admins give NTFS permissions but forget share permissions. Don’t do that.

2. Corrupted WMS Configuration or Cache

If permissions look fine, the WMS configuration store got corrupted. Common after a crash, improper shutdown, or failed Windows Update. The symptom: the publishing point starts, runs for a few seconds, then stops with 0XC00D145E.

Fix it: Reset the WMS configuration. Open Command Prompt as Administrator and run:

net stop wmserver
net stop wmservice

cd %windir%\system32\Windows Media\Server\

ren Admin"."bak Admin".old
ren Cache"."bak Cache".old

net start wmservice
net start wmserver

This renames the admin and cache folders. WMS will recreate them on restart. You’ll lose any custom publishing point settings (not content), so after restart, re-create the publishing point. If that’s too aggressive, try just clearing the cache:

net stop wmserver
net stop wmservice
del /q /s %windir%\system32\Windows Media\Server\Cache\*.*
net start wmservice
net start wmserver

That often fixes it without blowing away your admin settings. Test after restart. If the error persists, go nuclear with the full Admin rename.

3. Port Conflict or Binding Issue

Less common, but I’ve seen it: the publishing point’s HTTP or RTSP port got grabbed by another service. Typically after installing IIS, SQL Server Reporting Services, or a third-party streaming app. The publishing point starts, tries to bind, fails, and stops.

How to check: Open a command prompt and run:

netstat -ano | findstr :8080
netstat -ano | findstr :554

Replace the port numbers with whatever your publishing point uses (default HTTP is 8080, RTSP is 554). If you see anything listening on that port that's not WMS, that's your culprit. Use tasklist | findstr PID to identify the offender.

Fix it: Change the publishing point's port. In IIS Manager → Windows Media Services → publishing point → Properties → Network. Change HTTP to something like 8081, or RTSP to 555. Restart the service. If you must keep the original port, stop the conflicting service. For IIS, that’s usually the World Wide Web Publishing Service — don’t stop it unless you know what you’re doing.

Quick-Reference Summary Table

Last resort: Reinstall Windows Media Services. Open Server Manager → Remove Roles and Features → uncheck Windows Media Services. Reboot, then re-add. This is overkill 95% of the time, but if you’ve exhausted everything above, it works. Don’t blame me for the downtime.