Fix NS_E_INVALID_VIDEO_PEAKRATE_2 in Windows

Windows Media Player or transcoding tool throws this when peak bitrate is set below regular bitrate. Quick fix: adjust peak rate in encoder settings. Deeper fix: check registry or reinstall codecs.

What's actually happening here

This error isn't a system failure or a corrupt file. It's a validation check that fires when your video encoder or Windows Media Player tries to write a stream where the peak bit rate is equal to or less than the average video bit rate. In MPEG-4 and WMV encoding, peak rate is the ceiling—it has to be higher than the target rate. If it's not, the encoder refuses to run and throws NS_E_INVALID_VIDEO_PEAKRATE_2.

You'll see this most often when you're converting a video with a tool like Windows Media Encoder, Expression Encoder, or a third-party app that uses the Windows Media format SDK. It also pops up in some DVD authoring software that calls into the same codec pipeline.

Fix 1: Check your encoder settings (30 seconds)

If you're using a conversion tool, this is almost always the fix. Open the video encoding profile and look for two fields: Video bit rate and Video peak bit rate. The peak must be strictly greater than the regular bit rate. A common mistake is setting both to the same value, or leaving peak rate at zero, which some apps interpret as 'no peak'—and that also triggers the error.

For a typical 4 Mbps average, set peak to 6 Mbps. The exact ratio doesn't matter, just that peak > average. If you're using a constant bit rate (CBR) profile, switch to variable bit rate (VBR) mode—CBR doesn't have a separate peak rate, and some tools still try to set one, causing the mismatch.

Fix 2: Repair Windows Media Player components (5 minutes)

Sometimes the error shows up even when your settings look correct. That points to a broken Windows Media codec registration, often after a Windows update or a third-party codec pack messed with the registry.

First, try re-registering the Windows Media format components. Open Command Prompt as administrator and run:

regsvr32 wmp.dll
regsvr32 wmvdmoe2.dll
regsvr32 wmvcore.dll

Reboot and test again. If that doesn't help, reset Windows Media Player itself. Go to Settings > Apps > Windows Media Player > Advanced options and hit Reset. That clears its internal database and re-reads the codecs fresh.

If you've installed a codec pack like K-Lite or CCCP, uninstall it temporarily. Those packs override Microsoft's codecs with older or modified versions, and the peak rate validation sometimes gets broken in the process. After uninstalling, test your conversion. If it works, you've found the culprit—you can live without the pack or install the latest version that supports the proper registry entries.

Fix 3: Registry tweak for custom profiles (15+ minutes)

If you're building your own encoding profile or using a custom app that writes directly to the Windows Media registry keys, you may have a malformed profile entry. The relevant keys live under:

HKEY_CURRENT_USER\Software\Microsoft\Windows Media\Profiles

Open Registry Editor and navigate there. Look for an entry that matches your video profile name. Under it, find the VideoPeakBitrate DWORD. Set its value to a number greater than the VideoBitrate DWORD in the same key. If VideoPeakBitrate doesn't exist, create it as a DWORD (32-bit).

Be careful—the values are in bits per second, not kilobits. So for a 4 Mbps average (4,000,000 bps), set peak to 6,000,000. After editing, restart any app that uses the profile. If you're not comfortable editing the registry, it's safer to just delete that profile entry and recreate it through your app's UI, because a typo there can cause more errors than the one you're fixing.

One more thing: if you're a developer and you're hitting this via the Windows Media SDK, the fix is the same—your WM_MEDIA_TYPE structure must have dwBitrate (average) and dwPeakBitrate set correctly, with peak > average. The SDK will return this error code if you pass a profile with peak = 0 or peak < average.

Last resort: Clean reinstall of codecs

If none of the above works, you might have a corrupted codec binary. Windows Media Player's codecs are part of the OS, but you can force a repair by running sfc /scannow from an elevated command prompt. That checks system file integrity and replaces damaged files. It takes a while, but it's a sure way to eliminate file corruption as a cause.

Remember, the error is just a sanity check. It's your encoder telling you that the bitrate math doesn't add up. Get the peak above the average, and you're past it.