CD or DVD Drive Not Showing in Windows 11 & 10? Fix

If your CD or DVD drive has vanished from File Explorer or shows up in Device Manager with a yellow warning triangle, the fix is almost never a broken drive. In the overwhelming majority of cases, Windows has quietly disabled the drive at the registry level — usually because a disc-burning program, a virtual drive tool, or an update itself corrupted two filter values that sit above your driver in the registry, or flipped a single value that limits how many optical devices Windows will recognize. Reinstalling drivers rarely touches either of those, which is why so many people give up and assume the hardware died. Most of the time, it didn't.

Jake called me on a Saturday because a customer had walked in with a laptop, a stack of blank DVDs, and a deadline — wedding photos, burned to disc, needed by that evening. The laptop's drive showed up fine in File Explorer the week before. That morning it was gone. Not "not reading discs" gone — gone from the computer entirely, like it had never been installed. Jake tried the obvious things: restart, check the tray button, blow into the slot like it's 2004. None of it works, because none of it is the actual problem.

The actual problem, in almost every case we've seen written up about this since Windows 10 shipped, sits in the registry, not in the drive. Windows manages every optical drive through a class driver, and two things above that driver — a pair of filter values and a device-count value — are what decide whether the drive appears at all. Software conflicts, faulty updates, and even some security tools can corrupt or strip those values without touching a single physical component. The drive spins up fine if you could see it. Windows just won't show it to you.

Ethan, who's fixed enough of these to have opinions, put it more bluntly when I described Jake's case to him. "People blame the drive because the drive is the thing they can see," he said. "The registry is invisible, so nobody suspects it — that's exactly why it's the first thing I check." Jake wasn't convinced at first. "Isn't it more likely something just wore out?" It's a fair instinct — optical drives are mechanical, after all. But a drive that disappears completely from Device Manager, rather than degrading — failing to read, making noise, spinning up slowly — has a software fingerprint, not a mechanical one. Mechanical failure looks like a struggling device. This looked like a device that was never there.

Which symptom matches what you're seeing?

"Not working" covers at least four different problems, and they don't share a fix. Match yours before you touch anything.

If you're not sure which row you're in, open Device Manager first and just look. On Windows 11, right-click the Start button and choose Device Manager from the list — right-clicking Start opens a menu of admin tools, which hasn't changed since Windows 8. On Windows 10, the same right-click menu works. Expand DVD/CD-ROM drives. If that category doesn't exist at all in the list, your drive isn't just broken — Windows isn't even trying to enumerate it, which points straight at the registry causes below.

Two checks before you touch the registry

Skip these and you can waste an hour on registry edits for a problem that was never software.

Check the BIOS/UEFI setting

On a desktop, restart and enter your BIOS or UEFI setup (the key varies by manufacturer — usually Delete, F2, or F10 during the very first boot screen). Look for the SATA or storage configuration page and confirm the port your optical drive is connected to is set to enabled, not disabled or hidden. Some motherboards disable unused SATA ports by default to save a fraction of boot time, and a drive connected after the fact can land on a port that's still switched off in firmware. This is a one-time check; if it's already enabled, move on.

Check the physical connection, if you can

On a desktop tower, a loose SATA data cable or power cable is a real and common cause, especially after moving the PC or opening the case for a RAM or GPU upgrade. Reseating both cables costs nothing and rules out the simplest explanation. On a laptop with a sealed optical bay, skip this — there's nothing to reseat, and every laptop drive failure past this point is either the driver, the registry, or genuine hardware death, in roughly that order of likelihood.

The registry fix (Windows 11)

This is the fix that solves the drive's disappearance for the majority of people who hit this, and it works the same way whether the drive vanished after a feature update, after installing burning software, or for no reason you can point to.

Method A — remove the corrupted filter values

Press Win + R to open the Run box — a small dialog that launches a program or system tool directly by name, without going through the Start menu. Type regedit and press Enter. Approve the User Account Control prompt; the Registry Editor needs administrator rights because it can change settings for every user and every piece of hardware on the machine.

Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}

That long key in curly braces is the Class GUID for DVD/CD-ROM drive controllers — every device Windows classifies as an optical drive controller is registered underneath it. In the right-hand pane, look for two values named UpperFilters and LowerFilters. Not every system has both; some only have one. Right-click each one you find and choose Delete. These values normally point to small driver helper modules layered above and below the main driver — things like DVD region-code filters or virtual-drive drivers. When a program that installs one of those filters is uninstalled badly, or when an update overwrites the value with a broken reference, the filter points at a module that no longer exists, and Windows refuses to load the drive rather than load it incompletely.

Close Registry Editor and restart the PC. On restart, Windows rebuilds the driver stack for the class without the broken filters, and the drive should reappear in File Explorer and Device Manager on its own, with no further steps.

The whole of Method A, in one glance:

1. Press Win + R, type regedit, press Enter, approve the prompt.
2. Navigate to the DVD/CD-ROM Class GUID key shown above.
3. Right-click the key, choose Export, and save the backup .reg file.
4. In the right pane, delete UpperFilters and LowerFilters (only these — leave UpperFilters.bak-style names and everything else alone).
5. Close the Registry Editor and restart the PC; the drive should be back in File Explorer.

Method B — the device-count key, if Method A doesn't apply

If UpperFilters and LowerFilters aren't present, or deleting them didn't bring the drive back, the second known cause is a device-count limit under the ATAPI service key. Open an elevated Command Prompt or PowerShell window — right-click Start, choose Terminal (Admin) on current Windows 11 builds, or Windows Terminal (Admin) on slightly older ones — and run:

reg.exe add "HKLM\System\CurrentControlSet\Services\atapi\Controller0" /f /v EnumDevice1 /t REG_DWORD /d 0x00000001

This single line does, in one step, what would otherwise take several manual clicks through Registry Editor: it creates a Controller0 key under the ATAPI service if one doesn't already exist, and sets a DWORD value called EnumDevice1 to 1 underneath it. That value tells the primary IDE/ATAPI controller it's allowed to enumerate a second device on the channel — without it, or with it set to 0, Windows will only look for one device and silently ignore the drive if it's the second one on that controller. Restart after running the command.

Method B, in one glance:

1. In regedit, go to the atapi key and open (or create) Controller0 beneath it.
2. Create a new DWORD (32-bit) value named EnumDevice1 and set it to 1.
3. Close the Registry Editor and restart — Windows re-enumerates the drive on boot.

The registry fix (Windows 10)

These steps are the same on both Windows 11 and Windows 10 — the registry paths, the regedit tool, and the reg.exe command haven't changed. The only difference is how you get to an elevated Command Prompt: on Windows 10, right-click Start and choose Command Prompt (Admin) or Windows PowerShell (Admin), since Windows 10 doesn't have the unified Terminal app pinned to that menu by default the way current Windows 11 builds do.

Windows 10 reached the end of free security updates on October 14, 2025. It still boots and runs, and this registry fix still applies exactly as described above — but if you're troubleshooting a Windows 10 machine anyway, it's worth knowing where you stand. Devices on Windows 10 version 22H2 can still enroll in Consumer Extended Security Updates through Settings > Windows Update, and as of this writing that coverage runs to October 2027. If the PC you're fixing is also a candidate for a Windows 11 upgrade, that's a separate check — but it's not urgent just because the drive stopped showing up; the two problems aren't related.

Fix 2: uninstall and rescan the driver

If your drive does show up in Device Manager but carries a yellow warning triangle, you're not in registry-fix territory — the driver stack is loading, it's just failing. Double-click the drive entry and look at the Device status box on the General tab. Windows describes the failure there in plain language, and it's worth reading rather than skipping straight to reinstalling. A message pointing at corrupted registry entries for the driver usually leads back to the same filter values covered above. A message saying the driver couldn't fully start the device often means a stale or mismatched driver version is installed. A message saying Windows thinks the hardware was removed, even though it's still connected, is resolved in most cases by the uninstall-and-rescan steps below. And a status tied to the device having been connected while the PC was off or asleep often clears with nothing more than a restart.

To uninstall and rescan: right-click the drive entry in Device Manager and choose Uninstall device. Leave the "delete the driver software" checkbox unchecked unless you already downloaded a fresh driver from your manufacturer — you want Windows to reinstall its own built-in driver first, since third-party optical drive drivers are rarely necessary on Windows 10 or 11. Once it's uninstalled, click the icon at the top of Device Manager labeled Scan for hardware changes (it looks like a monitor with a magnifying glass). Windows re-detects the drive and reinstalls the driver fresh. This clears out a corrupted driver installation without needing to touch the registry directly, and it's worth trying even if you already ran the registry fix above — the two problems can coexist.

Fix 3: check the IDE ATA/ATAPI controllers

Further down the Device Manager list, expand IDE ATA/ATAPI controllers. This is where the physical channel your optical drive connects through gets managed, separately from the drive itself. If any entry here also has a warning triangle, the drive problem is downstream of a controller problem, and no amount of reinstalling the DVD driver will fix it until the controller itself is working. Right-click each controller entry, choose Properties, and check its status the same way. If a controller shows an error, uninstall and rescan it the same way described for the drive — controllers almost always reinstall cleanly, since Windows ships built-in drivers for standard ATA/AHCI controllers and rarely needs anything downloaded.

When burning or virtual-drive software is the real cause

This is the part almost nobody mentions, and it's the actual root cause behind a large share of the "filter values got corrupted" cases above. Software that mounts virtual CD/DVD images — the kind that lets you "insert" an ISO file without burning it — works by installing its own filter driver into that same UpperFilters/LowerFilters chain, sitting logically above your physical drive's driver. When that software is uninstalled cleanly, it removes its own entry from the filter value and leaves the rest intact. When it's uninstalled badly — forced closed, removed via a third-party uninstaller, or wiped out by a system restore — it can leave a dangling reference that breaks the entire filter chain, taking your physical drive down with it even though the physical drive was never the problem.

Disc-burning suites do the same thing from the other direction: some install a lower filter that intercepts write commands so they can add features like bootable-disc creation. If you've ever installed and later removed a burning program around the time your drive disappeared, that's the more likely trigger than an update. The registry fix above still applies and still works — you're just now doing it with the correct suspect in mind. If you plan to reinstall similar software afterward, install directly from the publisher's site rather than a bundled installer, since bundled installers are a common source of the badly-behaved uninstall that causes this in the first place.

External and USB optical drives

Most laptops sold in the last several years don't have a built-in optical drive at all, which is why Jake's shop keeps a shelf of USB external DVD writers for exactly this situation. External drives fail differently from internal ones:

• Try a different USB port first, ideally one directly on the laptop chassis rather than through a hub or docking station. External optical drives draw more power than a flash drive, and some USB hubs and older docks can't supply enough current to spin the disc reliably, which shows up as the drive disconnecting and reconnecting in Device Manager under Universal Serial Bus controllers.
• Check for a Y-shaped USB cable. Some external drives ship with two USB connectors specifically to pull extra power from two ports at once. If only one is plugged in, the drive may power on enough to be detected but not enough to spin a disc.
• The registry fix above still applies to external drives — they're enumerated under the same Class GUID as internal ones once Windows recognizes them as an optical drive.

"My laptop never had a drive to begin with"

Worth saying plainly, because it comes up constantly: if your machine is a thin-and-light laptop, an ultrabook, or almost anything sold new in the last several years, there is no optical drive to fix. Manufacturers stopped including them as standard well before Windows 11 existed, in favor of thinner chassis and USB-C ports. If Device Manager has never shown a DVD/CD-ROM category on that specific machine, none of the fixes above will conjure a drive that isn't physically installed — the two paths from here are a USB external drive, covered above, or skipping the disc entirely and using the ISO file directly, which both Windows 11 and Windows 10 can mount natively by right-clicking the file and choosing Mount, no third-party software required.

Virtual machines and Remote Desktop

Two setups behave differently enough from a normal desktop that it's worth separating them out. If you're running Windows inside a virtual machine — Hyper-V, VirtualBox, or similar — the "DVD drive" your guest operating system sees isn't physical hardware at all; it's a virtual optical drive defined in the VM's own settings, usually pointed at an ISO file or left empty. If that drive disappears inside the guest, check the VM's settings panel first, not Device Manager inside Windows — the virtual drive has to be attached at the hypervisor level before Windows inside the VM can ever see it, and no registry edit inside the guest will attach hardware that the hypervisor hasn't offered it.

If you're connecting to another PC over Remote Desktop and expected to see that PC's local optical drive, that depends on resource redirection being turned on in the Remote Desktop connection settings before you connect — under the Local Resources tab, in the "Local devices and resources" section. If it wasn't enabled at connection time, turning it on afterward won't retroactively redirect the drive; you have to disconnect and reconnect with it checked.

Do you need a third-party tool for any of this?

Honestly, no. Every fix above uses tools already built into Windows — Registry Editor, Device Manager, Command Prompt or PowerShell. There are free device-manager and driver-cleanup utilities that promise to automate this, and some of them do work, but they're solving a problem that's already a five-minute manual fix once you know the two registry values involved. The one place a third-party tool genuinely earns its download is disc-burning software itself, if you don't want to rely on Windows' built-in burning, which is functional but bare-bones. For that, stick to well-known publishers and install directly from their own site rather than a download aggregator — aggregator-bundled installers are exactly the kind that leave behind the dangling filter references described above when they're removed.

Before you hand a burned disc to a customer

Jake's actual job that Saturday wasn't just the registry fix — it was making sure the disc he handed back only had wedding photos on it, not anything left over from a previous job on the same machine. On a shared or shop PC, it's worth double-checking the burn queue and clearing out temporary files after each job, rather than assuming a fresh burn only ever includes what you just selected. It's a small step, but it's the difference between a customer trusting the shop with their next repair and not.

Frequently asked questions

Will deleting UpperFilters or LowerFilters break anything else?

No, as long as you're editing them under the DVD/CD-ROM Class GUID specifically. Deleting them removes whatever helper driver was layered on the CD/DVD driver stack; Windows rebuilds the stack with just its own built-in driver on restart. If a program that relied on that filter (a burning suite, a virtual-drive tool) is still installed, it may need reinstalling to add its filter back — but your physical drive itself won't be affected either way.

Do I need to restart after every step, or just once at the end?

Once, after you've made all the registry changes you plan to make in that session. Restarting between individual edits doesn't do any harm, but it's not necessary and just slows you down.

The Class GUID key in the registry doesn't exist on my PC at all. What now?

That would be unusual — that key exists on every Windows 10 and 11 installation regardless of whether an optical drive is present, since it's a system class key, not a per-device one. If you genuinely can't find it, double-check you're looking under HKEY_LOCAL_MACHINE and not HKEY_CURRENT_USER, and that the braces and hyphens in the GUID match exactly what's shown above.

I don't have administrator access on this PC. Is there another way?

Not one you should use. Every fix above requires administrator rights because it touches system-wide hardware configuration, not per-user settings. If you're on a managed or work PC without admin rights, this is one to hand to IT rather than work around — there's no safe non-admin path to editing HKEY_LOCAL_MACHINE.

Can a Windows Update cause this on its own, without any software involved?

Yes. A driver update pushed through Windows Update can, in rare cases, install a newer inbox driver that doesn't correctly preserve the existing filter values during the swap. It's less common than a software-related cause, but it happens, and the fix is identical either way.

My drive shows up but the tray won't eject.

That's a mechanical or driver-communication issue rather than a registry one. First try ejecting through Windows — right-click the drive in File Explorer and choose Eject — rather than the physical button, since a driver in a bad state sometimes won't respond to the hardware button. If that also fails, most optical drives have a small pinhole for a manual mechanical eject, usually done with a straightened paperclip while the PC is powered off.

Is it safe to just delete the whole Class key instead of the individual filter values?

No, don't do that. The Class key itself holds every property Windows needs to identify the entire category of optical drive controllers, not just the two filter values. Deleting the key wholesale, rather than the two specific values inside it, can prevent Windows from recognizing any optical drive controller until the key is rebuilt, which isn't a simple undo. Delete only the named values, never the key.

Does this fix work on Windows 11 Home the same as Pro?

Yes, identically. Everything covered here uses Registry Editor, Device Manager, and Command Prompt or PowerShell — none of which are restricted by edition. That's different from some other Windows fixes that need Group Policy Editor, which is Pro-and-above only.

I ran the EnumDevice1 command and nothing changed.

Confirm two things: that you actually restarted afterward, and that your drive is genuinely the second device on its controller channel rather than the first. If it's the only optical drive on that channel, this specific fix doesn't apply to your situation — go back to Method A and the filter values instead, or move to the driver uninstall/rescan step.

Can I just buy a cheap replacement drive instead of troubleshooting?

You can, and for a drive that's genuinely mechanically dead — grinding noises, discs not spinning at all, a tray motor that's stopped working — that's the right call, since internal SATA optical drives are inexpensive. But if the drive worked recently and simply disappeared from Windows, replacing the hardware won't fix a registry-level problem; the new drive will vanish the same way the old one did, because the cause was never the drive.

Will a system restore point fix this instead?

Possibly, if you have a restore point from before the drive disappeared and the cause was a specific software install or update. It's a legitimate option, but it also rolls back every other change made since that point, not just the one that broke your drive, so it's a broader fix than most people want for a single missing device. The registry edit is more targeted.

Does this affect Blu-ray drives too?

Yes. Blu-ray drives are enumerated under the same DVD/CD-ROM Class GUID in Windows, so every fix above applies to them without any changes.

I'm on Windows 10 and worried about being unsupported. Does that affect this fix?

No, the fix works the same regardless of update support status — Registry Editor, Device Manager, and Command Prompt aren't part of the security servicing that ended. It's a fair moment to think about whether to enroll in Extended Security Updates or plan a Windows 11 move, but that's a separate decision from getting your drive back today.

Is it safe to delete UpperFilters and LowerFilters?

Under this one Class GUID, yes — those values are add-ons that burning and virtual-drive software installed, not part of Windows itself. The worst realistic outcome is that a disc-burning program stops working until you reinstall it, which recreates its filter cleanly. The safety rule is scope: delete them only under the DVD/CD-ROM key shown in Method A, never under other Class GUIDs, and keep the exported backup from step 3 either way.

Will the registry fix survive future Windows updates?

Usually, yes — monthly updates don't touch these values. The two things that can bring the problem back are a major feature update and reinstalling the same burning or virtual-drive software that corrupted the filters the first time. If the drive vanishes again, it's the same five steps; nothing about the fix stops working the second time.

My drive is visible again but still won't burn discs — why?

Because visibility and burning are different jobs. The registry fix puts the drive back in File Explorer; burning still depends on the disc, the lens, and any burning software's own filter drivers. Work through the software section above — leftover virtual-drive tools are the usual culprit — then try a known-good disc before blaming the hardware.

Revision note. Originally published March 13, 2017, when this drive-vanishing problem was showing up mid-upgrade from Windows 7 to Windows 10. Rewritten August 26, 2026 for Windows 11 and Windows 10. The underlying cause hasn't moved — it's the same UpperFilters/LowerFilters registry values and the same device-count key — but what triggers it has shifted from OS upgrades to feature updates and leftover burning software, since most machines finished migrating off Windows 7 long ago. If you're here at 11pm with a deadline and a drive that just isn't there, you're not doing anything wrong; this one really is fixable in ten minutes.