Fix NS_E_LOGFILEPERIOD (0XC00D0048) in Windows Media

You're seeing error NS_E_LOGFILEPERIOD (0XC00D0048) when trying to log streaming media data? It's annoyingly vague but easy to fix.

This error pops up when Windows Media Services or a related app tries to set a log file rotation period that's outside the allowed range. The registry value LogFilePeriod must be between 1 and 365 days. If it's 0, negative, or blank, you get this error.

The fix: Edit the LogFilePeriod registry value

1. Press Windows Key + R, type regedit, then hit Enter. If you see a User Account Control prompt, click Yes.
2. In Registry Editor, go to this key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media\WMServer\Logging
3. In the right pane, look for a value named LogFilePeriod. If it's not there, right-click in the empty space, choose New > DWORD (32-bit) Value, and name it LogFilePeriod.
4. Double-click LogFilePeriod. Set the Base to Decimal. Type a number between 1 and 365. Most people use 1 (daily) or 7 (weekly). I recommend 1 for most setups — keeps logs small and manageable.
5. Click OK, then close Registry Editor.
6. Restart the Windows Media Services service: Press Windows Key + R, type services.msc, hit Enter. Find Windows Media Services, right-click it, and choose Restart.

After the restart, try whatever operation was giving you the error. It should work now.

Why this happens

The LogFilePeriod setting controls how often Windows Media creates a new log file. The system expects a positive integer. If someone (or some script) set it to 0, left it blank, or put in a negative number, the service throws error 0XC00D0048. I've seen this most often after a botched install of third-party media software that tweaks logging settings without checking values.

The real fix is making sure the value is in the valid range. Simple as that.

Less common variations

LogFilePeriod missing entirely

If the LogFilePeriod value doesn't exist at all, Windows Media Services often uses a default — but that default might conflict with other settings. In that case, create the DWORD value as described above and set it to 1.

Error appears after an update

Some Windows updates reset or corrupt registry keys. If the error started after a cumulative update, check if the WMServer key structure is intact. You might need to manually recreate the Logging subkey if it vanished. To do that:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media\WMServer
Right-click WMServer, choose New > Key, name it Logging. Then add the LogFilePeriod DWORD inside it.

Multiple values or incorrect type

I've seen cases where LogFilePeriod is set as a String instead of a DWORD. The service won't read a string properly. Delete the string value and create a DWORD in its place. Also check if there are duplicate entries — delete any extra copies.

How to prevent this from coming back

• Backup your registry before installing any third-party media tools. Right-click the WMServer key, choose Export, save it. If something goes wrong, double-click the .reg file to restore.
• Don't set LogFilePeriod to 0 even if you think "no rotation" is a good idea. The service won't accept it. Instead, set it to a high number like 365 if you want logs to rotate yearly.
• Use Group Policy if you manage multiple machines. Under Computer Configuration > Administrative Templates > Windows Media Services, you'll find logging policies that can enforce a valid range.
• Check event logs after any Windows Update related to Media Services. Look for Event ID 102 or 103 under Windows Media Services source. They'll tell you if a registry value got reset.

That's it. The error is stubborn but the fix is dead simple once you know where to look. Don't waste time reinstalling anything — this is always a registry issue.