NS_E_CD_NO_READER (0XC00D11FA): CD reader won't initiate

The 30-second fix: Reboot and reseat

Before you dig into drivers or registry hacks, do the dumb thing first. Eject your CD drive tray, push it back in, then restart Windows completely. Not a shut-down-and-start — a full restart. What's actually happening here is that the CD filter driver (cdrom.sys) might have gotten stuck in a bad state after a failed read or a device removal. A restart flushes the driver stack cleanly.

If you're on a desktop, unplug the SATA cable from the drive, wait 10 seconds, plug it back in. Laptop users: reseat the drive if it's removable. I've seen this fix work for a guy who'd spent an hour in Device Manager. Don't skip it.

Still broken? Move on.

The 5-minute fix: Nuke the UpperFilters and LowerFilters registry values

This is where the real fix lives about 80% of the time. The error NS_E_CD_NO_READER (0XC00D11FA) means Windows Media Player called the CD filter, the filter said "I exist," but then couldn't create a reader object. That filter is controlled by two registry values under the CD-ROM class GUID.

1. Press Win + R, type regedit, hit Enter.
2. Navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e965-e325-11ce-bfc1-08002be10318}
3. In the right pane, look for two values: UpperFilters and LowerFilters. If either exists, right-click it and delete it. Don't delete UpperFilters.bak or LowerFilters.bak — those are backups from some driver installers.
4. Close Regedit, restart your PC.

The reason this works: Those registry values are meant for third-party packet-writing software (like Nero or Roxio) or some DVD decrypters. They tell the system to load custom filter drivers before or after the built-in CD-ROM driver. If those filters are corrupt, missing, or referencing a driver that doesn't exist anymore, the entire CD stack fails. Deleting them lets Windows rebuild the default filter chain from scratch.

Warning: If you have an actual third-party CD burning app that uses those filters (old Roxio, Nero, or CloneCD), deleting them may break that software. In practice, modern Windows 10 and 11 don't need them — they use native IMAPI. You'll fix your reader error but may lose some legacy burning features. That's an acceptable trade-off for most people.

The 15-minute fix: Replace cdrom.sys and check for hardware deadlock

If the registry trick didn't work, the issue is either a corrupt system file or a genuine hardware problem. Let's rule out corruption first.

Step 1: Run SFC and DISM

Open an elevated Command Prompt (right-click Start → Windows Terminal (Admin)). Run:

sfc /scannow

Wait for it to finish. Then run:

DISM /Online /Cleanup-Image /RestoreHealth

Restart after both complete. This repairs the cdrom.sys driver file itself if it's been mangled by a bad update or a disk error.

Step 2: Remove hidden ghost drives in Device Manager

Windows sometimes keeps orphaned CD drive entries after you swap hardware. These ghosts can confuse the filter stack.

1. Open Device Manager (right-click Start → Device Manager).
2. Click View → Show hidden devices.
3. Expand DVD/CD-ROM drives. You might see grayed-out entries. Right-click each one and uninstall.
4. Reboot. Windows will rediscover the physical drive.

Step 3: Check the drive physically

If you're still getting the error, it's probably not software. Try a known-good audio CD — not a data DVD, not a pressed disc from a magazine. Audio CDs use the simplest Red Book format. If the drive can't read that, the laser lens might be dirty or the drive is dead.

Blow compressed air into the tray slot. For laptops, a lens cleaning disc (the ones with little brushes) is cheap and worth a shot. If the drive is SATA, check the cable connection inside the PC — those SATA cables work loose over time with vibration.

When all else fails: Use a USB external drive

Honestly, internal optical drives are becoming legacy hardware. If your motherboard's SATA controller is flaky or the drive is over 5 years old, spend $20 on a USB external DVD burner. Plug it in, Windows picks it up as a new device, and the NS_E_CD_NO_READER error disappears because the driver stack is clean.

I've seen this error on a Dell OptiPlex 7060 where the internal SATA port was dying. The external drive worked perfectly. Sometimes the fix is just acknowledging the hardware's age.