Fix NS_E_MULTIPLE_SCRIPT_BITRATES (0XC00D1BCE) in 3 Steps
This Windows Media Encoder error means your stream's script bit rates don't match. Fix it in under 30 seconds or dig into the project file.
What's actually happening here
You're encoding a stream with multiple bit rates in Windows Media Encoder (usually version 9 or 9 Series), and the encoder stops with NS_E_MULTIPLE_SCRIPT_BITRATES (0XC00D1BCE). The message says "All bit rates must have the same script bit rate." That's exactly the problem: your script stream—the one that carries closed captions, URL commands, or custom data—isn't set to the same bit rate across all your output bit rate profiles. One profile might have script at 4 kbps, another at 6 kbps. WME can't multiplex them together because the script stream is a constant bit rate stream that must be identical across all instances.
This crops up most often when you're building a multi-bit rate encoding job from scratch or importing a custom profile (.prx file) that someone else made. You'll see it right after you click "Start Encoding." The encoder won't even begin.
Fix 1: The 30-second check — verify your script settings
This is the fastest way. You're not editing anything yet, just looking.
- Open your Windows Media Encoder session (the .wme file or the current session).
- Go to Properties > Compression tab.
- Look at the list of bit rate profiles on the left. Select the first one.
- Click Edit to open the profile editor.
- In the Script tab, note the bit rate value. It's probably 4, 6, 8, or 10 kbps.
- Cancel out of the profile editor. Select the next bit rate profile. Repeat step 4-5.
- If any profile has a different script bit rate than the others, that's your culprit.
What you're looking for: every profile must show the exact same script bit rate. If you see 4 kbps in one and 6 kbps in another, move to Fix 2. If they're all the same, the problem is elsewhere — maybe your source file has a script stream that conflicts.
Fix 2: The 5-minute fix — edit the profile in the encoder
Assuming you found a mismatch, here's how to fix it without rebuilding everything.
- Back in the Compression tab, select the bit rate profile you want to change.
- Click Edit.
- Go to the Script tab.
- Change the bit rate dropdown so it matches the other profiles. If most use 4 kbps, set this one to 4 kbps. Don't overthink it — 4 kbps is the safest and most compatible.
- Click OK.
- Repeat for any other profile that's mismatched.
- Click Apply.
- Try encoding again.
The reason this works: WME requires the script stream to be identical across all bit rate options because it only encodes one script stream and then copies it into each output bit rate. If the bit rates differ, the encoder can't do the copy — it's like trying to fit a size-10 foot into a size-8 shoe.
Fix 3: The deeper fix — edit the .prx or .wme project file directly
Sometimes Fix 2 doesn't stick, especially if the profile is read-only or you're working with a heavily customized .prx file. I've seen this with profiles pulled from old production servers. Here's the nuclear option.
- Close Windows Media Encoder completely.
- Locate the project file: it's either a
.wmefile you saved, or a.prxprofile file. They're usually in%USERPROFILE%\Documents\Windows Media Encoder\or wherever you saved it. - Make a copy of the file first — you don't want to lose the original.
- Open the
.wmeor.prxfile in Notepad (or any plain text editor). It's an XML file. - Search for
<ScriptBitRate>. You'll find it inside each<Profile>or<Bitrate>section. - Change every
<ScriptBitRate>value to the same number. For example, if one says4000and another says6000, make them both4000. The value is in bits per second, so 4000 = 4 kbps. - Save the file.
- Reopen WME and load the project file. The error should be gone.
A word on why editing the XML manually is sometimes necessary: WME's profile editor has a bug where changing the script bit rate in the UI doesn't always save correctly — especially if you have multiple profiles. I've wasted an hour on that. Direct XML edit never fails.
What if the error persists?
Two edge cases I've run into:
- Script stream in the source file: If your source video already has a script stream embedded (like a .asf file with captions), WME might try to merge it. Go to Properties > Sources tab, select the video source, and under Script, choose "No script." Then use a separate script source if needed.
- Corrupted profile: Sometimes the .prx file is just broken. Build a new profile from scratch. Create a new session, choose "Custom encoding session," and manually add your bit rate profiles one by one, setting the script bit rate same on each. Export it as a new .prx.
That's it. The error is annoying but narrow. Fix the script bit rate mismatch, and you're encoding again in minutes.
Was this solution helpful?