NS_E_WMPCORE_TEMP_FILE_NOT_FOUND (0XC00D10BB) Fix

Quick Answer for Advanced Users

Delete everything in %TEMP% and %WINDIR%\Temp, then run sfc /scannow from an admin command prompt.

What This Error Means

Windows Media Player throws error 0XC00D10BB (NS_E_WMPCORE_TEMP_FILE_NOT_FOUND) when it tries to write or read a temporary file during playback, CD/DVD burning, or syncing, but the file isn't there. The trigger is almost always a corrupted or missing temp file — maybe a disk cleanup tool deleted it mid-operation, or your anti-virus quarantined it. I've seen this happen most often when someone tries to burn a CD and the temp folder doesn't have write permissions. It can also pop up if your drive is full or if Windows accounts have conflicting temp folder settings.

Main Fix: Clean and Repair Temp Folders

This is the fix that works for 9 out of 10 cases. We'll clear both user temp and system temp, then check permissions. You won't lose any important files — temp files are disposable by design.

1. Close Windows Media Player completely. Right-click the taskbar and open Task Manager — kill any wmplayer.exe processes.
2. Press Windows Key + R, type %TEMP%, and hit Enter. A folder full of junk opens.
3. Select everything inside (Ctrl+A), then hit Delete. Some files might say they're in use — just skip those. After deletion, close this window.
4. Press Windows Key + R again, type %WINDIR%\Temp, and hit Enter. This is the system temp folder.
5. Again, Ctrl+A then Delete. Skip any files that won't delete. Close this window.
6. Now we fix permissions. Press Windows Key + R, type cmd, right-click it, and choose Run as administrator.
7. Type this command and press Enter:

   icacls "%TEMP%" /grant "%USERNAME%":(OI)(CI)F /T

   You should see successfully processed 1 files.
8. Next, run a system file check:

   sfc /scannow

   Wait for it to finish — it'll take 5-15 minutes. If it finds corrupted files, it fixes them automatically.
9. Restart your computer. Try opening Windows Media Player and playing the same file or doing the same task that triggered the error.

After restart, the error should be gone. If it's not, move to the alternatives below.

Alternative Fixes

Clear Windows Media Player's Own Cache

WMP keeps its own stash of temporary data. Let's wipe that too.

1. Open Windows Media Player.
2. Click Organize (top-left), then Options.
3. Go to the Privacy tab.
4. Under History, click Clear History. Then under Location, click Clear Caches.
5. Click Apply, then OK. Restart WMP.

Repair or Reset Windows Media Player

If temp file problems persist, the player itself might be corrupted.

1. Press Windows Key + I to open Settings.
2. Go to Apps → Apps & features.
3. Scroll down to Windows Media Player. Click the three dots next to it and choose Advanced options.
4. Click Repair. Windows will fix the install without losing your library. If that doesn't work, click Reset (this resets the app, your library will be rebuilt from your media folders).
5. Restart and test.

Free Up Disk Space

If your main drive has less than 5% free space, Windows can't create temp files reliably. Check by right-clicking C: in File Explorer and looking at the free space. If it's low, run Disk Cleanup: press Windows Key + R, type cleanmgr, select the drive, and let it delete temporary files, thumbnails, and recycle bin contents.

Prevention Tips

• Don't let disk cleaners run while WMP is open. Tools like CCleaner or Windows Disk Cleanup can delete temp files that WMP is using mid-operation. Always close WMP first.
• Set a regular temp-cleaning schedule — once a month, manually clear both %TEMP% and %WINDIR%\Temp. It keeps things lean and avoids permission confusion.
• Keep 10% of your main drive free. Windows needs room to breathe. If you're constantly hitting the wall, move large files to an external drive.
• Make sure your user account has full control over your own temp folder. The icacls command from the main fix is a one-time permission booster — run it again if you change accounts or reset permissions.

That's it. Most people never see this error again after cleaning temp folders and running sfc. If you still get the error after all this, you might be dealing with a failing hard drive or a corrupted Windows user profile — but that's rare. Try creating a new local admin account and test WMP there. If it works, migrate your data over.