NS_E_INVALID_PLAY_STATISTICS (0XC00D1587) fix when streaming audio stops logging
This error pops up when Windows Media Player or a streaming app can't save play statistics. Usually happens after a sudden crash or network drop mid-stream. Fix is simple: clear the media player cache or reset the stats file.
When you see this error
You're streaming music through Windows Media Player or a similar app. Maybe you're listening to a podcast or a radio stream. Suddenly the app freezes for a second, then pops up an error: NS_E_INVALID_PLAY_STATISTICS (0XC00D1587). The stream keeps playing sometimes, but the app stops logging what you listened to. That means no play count, no last played date, nothing. I had a client last month whose whole playlist history vanished because of this – he had to re-add everything manually.
This usually happens after:
- The network drops for a second mid-stream
- You close the app without stopping the stream properly
- A system crash or forced reboot while media was playing
Root cause in plain English
The error means the media player can't write the play statistics (like how many times you played a song or how long you listened) to its internal log file. The stats file is a tiny database that the app updates after each play session. When the app crashes or the stream cuts out, that file gets corrupted. It's like trying to save a file while the power goes out – the data gets scrambled.
On Windows, these stats are usually stored in C:\Users\[YourName]\AppData\Local\Microsoft\Media Player. The corruption is specific to that folder, not your whole system. So no need to reinstall Windows or anything drastic.
The fix: clear the media player cache
Step 1: Close any media apps
Make sure Windows Media Player, Groove Music, or any other player that uses the stats is closed. Check the system tray and force close if needed. Use Task Manager to be sure.
Step 2: Open the stats folder
Press Win + R, type this, and hit Enter:%LocalAppData%\Microsoft\Media Player
That opens the folder with the corrupted stats file.
Step 3: Delete the stats file
Look for a file named CurrentDatabase_372RSSS.wmdb (or something similar with a long random name). Delete it. Don't worry – Windows will recreate it next time you play something. Also delete any *.wmdb files in that folder. There might be a few.
If you can't delete because it's in use, restart your PC and try again. Had that happen many times.
Step 4: Clear the library cache too (optional but smart)
Open Windows Media Player. Go to Organize > Manage libraries > Music. Remove your music folders from the library temporarily. Then add them back. This forces the player to rebuild the database from scratch. It's a bit slow but guarantees no leftover junk.
Step 5: Test the fix
Play a song or stream for at least 30 seconds. Then close the app and reopen. Check if the play count updated. If it did, you're good. If not, move to the next step.
What to check if it still fails
If the error comes back, you've got a deeper issue. Here's what I'd check next:
- Permissions on the Media Player folder – Right-click the folder, go to Security, and make sure your user has Full Control. Sometimes after a Windows update, permissions get messed up.
- Antivirus blocking the file – Some AV software treats the stats file as suspicious because it's a database. Temporarily disable your AV and test again. I've seen Norton block it once.
- Windows Media Player version – Go to Settings > Apps > Optional features and check if Media Player shows any pending updates. Or just reinstall it via Turn Windows features on/off (uncheck then recheck Media Features).
- Corrupted user profile – If none of that works, create a new local user and test the player there. If it works in the new profile, your old profile is toast. Migrate your data.
One more thing: if you're using an old third-party player (like Winamp or something), check its own settings for where it stores play stats. That error might come from the OS, not the app itself. But 90% of the time, deleting the .wmdb files fixes it. Save yourself the headache and just clear the cache. You'll be back to normal in two minutes.
Was this solution helpful?