0XC00D1BD7: Can't apply time compression to a video-only session

When this error shows up

You're watching a video in Windows Media Player, maybe a webinar recording or a screen capture with no narration. You hit the speed-up button—usually the play speed slider under the Now Playing menu—and instead of doubling the pace, you get a pop-up: "It is not possible to apply time compression to a video-only session" with error code 0XC00D1BD7. Had a client last month who recorded a series of training demos in OBS with no microphone input. Every single file threw this error. Drove him nuts until we figured it out.

What's actually happening here

Time compression—that's the technical term for speeding up playback without changing pitch—works by manipulating audio data. Windows Media Player's algorithm chops up the audio stream, overlaps it, and adjusts pitch to keep it sounding natural. Problem is, if your video file has no audio track at all, there's nothing to compress. The video stream alone can't be time-stretched because video frames are discrete units—you can skip or drop frames, but you can't "compress" them the same way. So WMP throws this error instead of crashing or playing silent garbage.

The fix: three ways to solve it

Option 1: Add a silent audio track (the real fix)

This is the proper solution. You re-encode the video to include an audio stream, even if it's dead silence. I use HandBrake for this because it's free and handles everything. Here's the steps:

1. Download and install HandBrake.
2. Open HandBrake, click Open Source, select your video file.
3. Under the Summary tab, pick a preset like "Fast 1080p30".
4. Go to the Audio tab. Click Add Track. It defaults to a silent AAC track. Leave it as is.
5. Under Destination, choose a new file name so you don't overwrite the original.
6. Click Start Encode. Takes a few minutes depending on file size.
7. Open the new file in WMP. Speed control works now.

Had a client who needed to batch-process 50 files. I wrote a quick ffmpeg script for that—here's the one-liner if you're comfortable with command line:

ffmpeg -i input.mp4 -f lavfi -i anullsrc=r=44100:cl=mono -c:v copy -c:a aac -shortest output.mp4

That adds a silent mono audio track at 44.1 kHz without re-encoding the video.

Option 2: Switch to a different media player

If you don't want to mess with re-encoding, just use a player that handles video-only files better. VLC Media Player is my go-to. It doesn't rely on time compression—it just drops or duplicates frames to change speed, which works fine without audio. Download VLC from videolan.org, open your file, and use the playback speed slider in the bottom-right corner. No errors, no fuss.

Option 3: Enable a workaround in WMP (hit-or-miss)

Some versions of Windows Media Player let you force time compression even on video-only files by toggling a registry setting. I don't love this approach because it can cause stuttering, but here it is if you want to try:

1. Press Win + R, type regedit, hit Enter.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences.
3. Right-click in the right pane, select New > DWORD (32-bit) Value.
4. Name it EnableTimeCompressionForVideoOnly and set the value to 1.
5. Close regedit, restart WMP.

This doesn't work on all Windows 10 builds—I've seen it fail on 22H2. Test it before relying on it.

What to check if it still fails

If none of the above works, check these three things:

• File format: Some codecs like HEVC or VP9 might not play well with WMP at all. Convert to H.264 in HandBrake as a test.
• Windows Media Player version: WMP is deprecated in Windows 11—open it, click Help > About. If it's older than 12.0.22621.0, update Windows.
• Third-party codec packs: K-Lite or Shark007 can sometimes break time compression. Uninstall them temporarily, test again, then reinstall if needed.

Bottom line: the root cause is always a missing audio track. Skip the registry hack and just add a silent track or switch to VLC. You'll save time and frustration.