0X800D0060

NS_W_UNKNOWN_EVENT (0x800D0060) Fix: 3 Easy Steps

Windows Errors Beginner 👁 0 views 📅 Jun 8, 2026

This error pops up when Windows Media Player can't handle a custom event in a media file. Three quick fixes—usually the first one works.

1. Corrupt or Custom Metadata in the Media File

This is the culprit nine times out of ten. The error means Windows Media Player ran into a file event it doesn't recognize—usually a custom event header added by editing software like Adobe Premiere, Sony Vegas, or even some camera apps. The player can't process it, so it throws 0x800D0060.

The fix: Strip the metadata. Use ffmpeg or a simple tool like MP3tag (free). Here's the fast way with ffmpeg:

ffmpeg -i "input.wmv" -c copy -map_metadata -1 "output.wmv"

That copies the video and audio streams without copying any metadata. If you don't have ffmpeg, download it from ffmpeg.org. Run this in Command Prompt (as admin) or PowerShell. Replace the file names with your actual file paths.

If the file plays fine after that, you're done. The error won't come back unless you re-add the metadata. Skip the rest of this article.

2. Corrupt Windows Media Player Library Database

If the error shows up when you're browsing your library—not just playing a specific file—the library database might be corrupted. This happens when WMP crashes or you force-close it mid-scan. The database gets out of sync, and WMP confuses a normal file for something unknown.

Fix: Reset the library. Close WMP completely. Then open an elevated Command Prompt (right-click Start, choose Command Prompt or Terminal as Admin) and run:

regsvr32 jscript.dll
regsvr32 vbscript.dll
reg delete "HKCU\Software\Microsoft\MediaPlayer\Player" /f

This deletes the player registry key—don't panic, WMP will rebuild it when you restart. Then relaunch WMP. It'll take a minute to rescan your library, but the error should be gone.

Note: This resets your playlists and most settings. You'll need to re-add your media folders. Annoying, but it works.

3. Missing or Outdated Media Foundation Codecs

Less common, but real. If you're playing a file with a newer codec (like H.265/HEVC or VP9) on an older Windows 10 build (pre-1809), WMP might not have the right decoder. The error mimics the metadata issue because the file's header includes a codec event tag the player can't parse.

Fix: Install the HEVC Video Extensions from the Microsoft Store. It's free, but Microsoft hides it. Use this direct link: HEVC Video Extensions. If that fails, try the VLC media player—it handles more codecs than WMP ever will.

Alternatively, update Windows. Go to Settings > Update & Security > Windows Update. Check for updates. A major update like 22H2 includes newer codec support that often resolves this.

Quick-Reference Summary

Cause Fix Difficulty
Corrupt metadata in the file Strip metadata with ffmpeg: ffmpeg -i input.wmv -c copy -map_metadata -1 output.wmv Beginner
Corrupt WMP library database Reset library: delete registry key HKCU\Software\Microsoft\MediaPlayer\Player Intermediate
Missing codec (HEVC/VP9) Install HEVC Extensions from Microsoft Store Beginner

That's it. Start with the first fix—it's the one that actually fixes it. The other two are backups for edge cases. If none of these work, the file itself is likely broken beyond repair. Get a fresh copy from the source.

Was this solution helpful?