Fix NS_E_INVALID_AUDIO_PEAKRATE (0xC00D1BBA) Error

Simple Fix (30 seconds): Reset the Media Library

I know this error is infuriating — you're trying to play a video or audio file, and Windows Media Player just spits out "The audio peak bit rate setting is not valid." Nine times out of ten, it's because the media library database got corrupted. Maybe you installed a codec pack, or Windows Update did something behind your back. The quickest fix is to wipe that library and let WMP rebuild it.

1. Close Windows Media Player completely. Check Task Manager to make sure it's not lurking in the background.
2. Press Win + R, type %LOCALAPPDATA%\Microsoft\Media Player, and hit Enter.
3. Delete everything in that folder. Yes, all of it. Don't worry — WMP will recreate these files the next time it starts.
4. Open Windows Media Player again. It'll take a minute to rebuild the library (depending on how many files you have), but the error should be gone.

This tripped me up the first time too — I thought I'd lose my playlists. You won't. The database just gets refreshed. If the error's still there, move to the next step.

Moderate Fix (5 minutes): Check Audio Driver and Default Format

If resetting the library didn't work, the problem might be your audio driver reporting garbage to the system. This happens a lot with Realtek or Conexant audio chips on older Windows 10 builds. Here's what to check:

1. Right-click the speaker icon in the taskbar and select Sound settings.
2. Under Advanced, click More sound settings.
3. In the Sound window, select your default playback device (usually Speakers or Headphones) and click Properties.
4. Go to the Advanced tab. Look at the Default Format dropdown. If it's set to something like "24 bit, 192000 Hz (Studio Quality)", drop it down to "16 bit, 44100 Hz (CD Quality)". Click Apply and OK.
5. Test the file that was throwing the error. If it works, great. If not, try another format like "16 bit, 48000 Hz (DVD Quality)". Some codecs get wonky with high sample rates.

Pro tip: If you've recently updated your audio driver and this error started, roll back the driver. Go to Device Manager, find your audio device under Sound, video and game controllers, right-click, choose Properties, then the Driver tab, and click Roll Back Driver. This saved me on a Dell Inspiron 5570 after a botched Realtek update.

Advanced Fix (15+ minutes): Registry Edit for Peak Bit Rate

If you're still seeing the error, the system's registry has a rogue entry for the peak bit rate. This is rare — I've only seen it on machines that had third-party audio editors like Audacity or Adobe Audition installed and then removed. The fix is a registry tweak. Back up your registry first. Messing this up can break your audio entirely.

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to this path:
   HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences
3. Look for a DWORD value named AudioPeakBitrate. If it's there, right-click it and delete it.
4. If you don't see that key, navigate to:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Player\Settings
5. Search for any DWORD named AudioPeakBitrate or PeakBitrate and delete them. These shouldn't exist by default — if they're there, something (like a codec pack) put them there.
6. Close Regedit and restart your computer.

After the reboot, try playing the file again. This fix has worked for me on Windows 10 22H2 and Windows 11 23H2 systems that had the error after installing the K-Lite Codec Pack.

Still stuck? Try these last resorts

• Use a different player. VLC Media Player doesn't give a damn about Windows' bit rate settings — it uses its own decoders. Download VLC, open your file, and be done with it. This isn't really a fix, but it's faster than fighting the system.
• Reinstall the media codec. If you have a codec pack like K-Lite or Combined Community Codec Pack, open its uninstaller and choose to "reset all settings" rather than uninstalling. Then reinstall with default options.
• System Restore. If the error started after a Windows Update, roll back to a restore point from before that update. Type rstrui in the Run dialog, pick a point from before the error appeared, and restore.

Hope one of these gets you sorted. The peak bit rate error is stubborn, but it's almost always a corrupt library or a driver quirk — not a real file problem. Drop a comment below if you found another fix — I'm always updating this.