NS_E_PDA_FAIL_READ_WAVE_FILE (0XC00D117D) Fix

You're stuck with error 0XC00D117D when trying to open a WAV file in Windows Media Player. I've seen this dozens of times. Let's fix it.

First thing to know: this error almost always means the WAV file's header is corrupted or the file uses a sample rate or bit depth that Windows Media Player can't handle. The built-in player is picky – it wants standard PCM WAV files at 44.1 kHz or 48 kHz, 16-bit. Anything else and it throws this error.

The Quick Fix: Convert the WAV to a clean PCM WAV

1. Download a free audio converter. I use Audacity (it's open source, no strings attached). Install it – takes about 30 seconds.
2. Open the problematic WAV file in Audacity. Go to File > Open and pick your file. If it opens without errors, we're in good shape. If Audacity also can't read it, the file is badly corrupted – skip to the prevention section below.
3. Check the file format. At the bottom of Audacity's window, look at the Project Rate (Hz) dropdown. It'll show something like 44100 or 48000. That's good. If it shows 96000 or 192000, that's your problem – Windows Media Player doesn't support those high sample rates for sync or playback in some versions.
4. Export a clean WAV. Go to File > Export > Export as WAV.
5. In the export window, choose WAV (Microsoft) as the format. Under Encoding, pick Signed 16-bit PCM. Set the sample rate to 44100 or 48000 – whatever matches the original. Click Save.
6. You'll get a new file. Try opening that in Windows Media Player. It'll work now.

After you click Save, Audacity will create the new file. You should see it in your folder with a fresh timestamp. Double-click it – Windows Media Player should play it without any error.

Why did that fix it?

The original WAV file had a header that Windows Media Player couldn't parse. It's like a book with a torn cover – the player doesn't know how to start reading the data. Audacity reads the raw audio data and writes a fresh, standard header. Also, if the original was 32-bit float or used a non-standard encoding (like ADPCM), the player just refuses. Converting to 16-bit PCM makes it universally compatible.

I've seen this happen most often with WAV files recorded on old digital voice recorders, or files transferred from a phone that got truncated during copy. The header gets mangled, but the audio data is fine.

Less common variations of the same issue

• Corrupt file from a flash drive. If you copied the WAV from a USB drive and the copy failed silently (happens more than you'd think), the file is incomplete. Try re-copying it. Use robocopy or Teracopy to verify the copy.
• DRM-protected WAV. Some online stores (remember those?) sold DRM-locked WAV files. Windows Media Player can't play those. You'd need to strip the DRM or convert to MP3. But this is rare now.
• Third-party codec conflict. If you installed a codec pack like K-Lite, sometimes the wrong codec gets priority. Uninstall any third-party codec packs, then test again. Windows Media Player should use its built-in WAV decoder.
• Sample rate mismatch on portable devices. If you're syncing to an old MP3 player (like a Zune or an iPod), the device might only support 44.1 kHz. Convert to 44.1 kHz, 16-bit WAV. That'll fix the sync error.

Prevention – keep your WAV files healthy

Use a reliable file copying tool. Windows Explorer sometimes fails silently on large audio files. Use Teracopy or robocopy with the /V (verify) switch. Example: robocopy source_folder destination_folder *.wav /V.

Set your recording software to always export as 16-bit PCM WAV at 44100 or 48000 Hz. Avoid 32-bit float or 24-bit – while those are higher quality, Windows Media Player stumbles on them. If you need high-res, keep a master copy in FLAC and a separate WAV copy for media players.

Finally, check your WAV files with a free tool like MediaInfo before trying to play them. If MediaInfo reports anything unusual (like "Format: WAV", but "Codec ID: 0x0003" – that's 16-bit PCM – anything else is trouble).

That's it. You should be back to playing your WAV files. If not, the file might be beyond repair – try recovering it from a backup or re-recording it.