NS_E_LOG_NEED_TO_BE_SKIPPED (0XC00D1588) — Fixed

Corrupted Recording Log — The Usual Suspect

This error shows up when Windows Media Center tries to read a recording log that's been damaged — usually from a power outage, a failed disk write, or Media Center crashing mid-recording. The culprit here is almost always a single corrupted .wtv or .dvr-ms file that WMC can't process. Don't bother reinstalling Media Center or running a system restore — that rarely helps.

Here's the fix that works 9 times out of 10:

1. Open Windows Media Center.
2. Go to Tasks > Settings > TV > Recorder > Recording Defaults.
3. Click Reset Recording Defaults. This clears the cached recording metadata but leaves your actual recordings alone.
4. Restart Media Center and try playing the recording again.

Still broken? You need to delete the actual recording log file. Press Windows + R, type %ProgramData%\Microsoft\eHome\, and hit Enter. Look for a folder called Recording Logs. Delete everything inside it — don't worry, these are just metadata files. WMC will rebuild them on the next launch.

Corrupted Database — When the Log Isn't the Problem

If deleting the recording log didn't do it, the issue is likely in the Media Center database itself. This happens when the database file McuDb.sdf gets corrupted. You'll see the same error, but the log deletion won't touch it.

To fix it:

1. Close Media Center completely.
2. Open an admin Command Prompt: right-click Start, select Command Prompt (Admin).
3. Run this command to rebuild the database — it takes about 30 seconds:

%windir%\ehome\mcupdate.exe -DatabaseReset

Let it finish, then restart Media Center. You'll lose your recording series and scheduled recordings — but not the actual video files. You'll have to re-add your guide and recording schedules afterward. Annoying, but it beats a full Windows reinstall.

If that command fails, try the more aggressive version:

%windir%\ehome\mcupdate.exe -ForceUpdate

This forces a full guide download and rebuilds the database from scratch. Takes longer but works when the first option chokes.

Third-Party Codec Conflicts — The Sneaky One

Sometimes the error isn't from corruption at all. It's a codec conflict. I've seen this most often on systems with Shark007 or K-Lite codec packs installed alongside Media Center. The codec pack overrides the default Media Center codec for WTV files, and Media Center can't parse the log.

Here's the quick test: uninstall any third-party codec packs. Reboot. Try the recording again. If it works, you know the culprit. You can either keep the recording stock or reinstall the codec pack but disable its WTV codec handling — look for a setting like "Use default Media Center codec" in the codec config tool.

If you don't have codec packs, check for software that installs its own decoders — things like MPC-HC, VLC, or even some video editing apps. They can register their own filters and mess with WMC.

Quick-Reference Summary

Start with the log deletion — it's the fastest and least destructive. If that doesn't cut it, move to the database reset. Codec issues are rarer but worth checking if nothing else works.