0XC00D2AFE

NS_E_SETUP_IGNORABLE_FAILURE (0XC00D2AFE) Windows Media Player

Windows Errors Intermediate 👁 9 views 📅 May 28, 2026

Windows Media Player install fails with this error when a skin or playlist component can't register. Almost always a permissions or corrupted component store issue.

What triggers this error

You're installing or updating Windows Media Player — usually through Windows Update or the Media Feature Pack on Windows 10/11 N editions. The installer runs fine for a bit, then hits this error right near the end. The exact message reads: "Some skin or playlist components cannot be installed." Code 0XC00D2AFE.

This happens most often after a feature update, like upgrading from Windows 10 22H2 to Windows 11 23H2. Or when you toggle Windows Features on and off. The culprit here is almost always a corrupted component store or a permissions issue in the %ProgramData%\Microsoft\Windows\WER folder.

Root cause

Windows Media Player ships as an optional feature in modern Windows. Its setup process tries to register a handful of skin (.wmz) and playlist (.wpl) components into the COM+ catalog. If the component store (CBS) has a bad manifest or a registry key is locked down, the registration fails. The installer treats this as "ignorable" — hence the error code name — but it still blocks a clean install.

Don't bother with reinstalling Windows Media Player from a third-party site. That rarely helps because the problem lives in the component store, not the player itself.

Fix it in 5 steps

Step 1: Run the System File Checker

Open Command Prompt as Administrator. Run this:

sfc /scannow

Let it finish. If it finds corrupt files but can't fix them, move to Step 2. If it finds nothing or reports fixed, reboot and try the Media Player install again.

Step 2: Repair the component store with DISM

This is the real fix in most cases. Still in an admin Command Prompt, run:

DISM /Online /Cleanup-Image /RestoreHealth

This downloads fresh component files from Windows Update. Takes 5–15 minutes depending on your connection. After it completes, run sfc /scannow one more time. Then reboot.

Step 3: Re-register Windows Media Player via Windows Features

Open Control Panel > Programs > Turn Windows features on or off. Scroll down to Media Features. Uncheck Windows Media Player. Click OK and reboot. Go back into Windows Features and re-check Windows Media Player. Click OK and let it install fresh.

Step 4: Clear the WER folder (if permissions are stuck)

Sometimes a locked WER (Windows Error Reporting) folder blocks component registration. Do this:

  1. Open File Explorer and go to %ProgramData%\Microsoft\Windows\WER
  2. Right-click the Temp folder inside it — if it exists — and take ownership (Properties > Security > Advanced > Change owner to Administrators).
  3. Delete the Temp folder. Windows will recreate it.

Then retry the Media Player install.

Step 5: Reinstall the Media Feature Pack (Windows N editions only)

If you're on Windows 10/11 N, Media Player isn't included by default. You need the Media Feature Pack from Microsoft's site. Download the correct version for your build (check Settings > System > About). Install it as an admin. If the same error pops up, run Steps 1–4 first, then try the pack install again.

Still failing? Check these

  • Third-party antivirus — Temporarily disable any real-time protection and retry. I've seen McAfee and Norton block component registration.
  • Corrupted user profile — Create a new local admin account and try the install from there. If it works, migrate your data off the old profile.
  • Pending Windows updates — Make sure you're fully updated. Run Windows Update manually and install everything, then reboot.
  • SFC/DISM still failing — If DISM can't restore health because it can't reach Windows Update, you need a Windows ISO. Mount it and run DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\mount\windows\sxs /LimitAccess pointing to the ISO's sources folder.

This error looks scary but it's just a registration hiccup. Nine times out of ten, the DISM command alone fixes it. Don't waste time uninstalling and reinstalling the player repeatedly — fix the store first.

Was this solution helpful?