All CDRom Drives Not working in Win XP

WinXP SP1+ All Critical Updates - DX9
p3 733
Radeon 8500DV
Teac W540E CD-R 40/12/48

Hi, My problem is that out of the blue my cd rom drives do not show up in windows, I've had them work perfectly in the past and work good sar far on this new install, about a month old. They still are visible in device manager but have an exclaimation point to indicate a problem. All have this error message.

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

The troubleshooter is of course usless because I uninstall all of them and reboot and get the same thing still. I should also add that DaemonTool's virtual CD-ROMs are also disabled. so that makes 5 cd drives all not work.

Suspecting an old DVD drive might be at fault I disabled the DVD drive by unplugging its power and IDE. Even with only that drive left I get this problem.

I also tried the primitive method deleting registry values pretaining to things where my CD drives names were. Rebooted, had no effect. I had backed backed these up and restored them.

Booted off windows XP CDRom, Suspected the drivers might have been corrupted as it is an old hard drive and have recently had problems with this. Unfortunatley I couldn't get these drivers off the CD in the recovery console because it doesn't let you leave the windows directory. But obviously the CD Drive works because it loaded all the files as if going to prepare for an install.

So question is if its the bad driver files, names are

how can I reload these, I was only able to find on the win CD and copy to floppy renamed of course from file.ex_ format

No recent installations Either, DX 9 was, a few days ago but I don't know how this could have had anything to do with CDROM besides I tried a restore point and it couldn't load the restore point proporly. I think it only keeps 1 days ago.

So if its the drivers I need some way to reinstall them. I'm kinda out of ideas here, maybe also registry settings but I wouldn't know what to do beyond what I tried. The fact that even the virtual CD Roms were down should tell us something. If you have any ideas post em.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alternatively here is a vb script to do the above:

CD-ROM Access Is Missing and Messages Cite Error Code 31, Code 32, Code 19, or Code 39 After You Remove Easy CD Creator in Windows XP;EN-US;314060


The information in this article applies to:
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional

This article was previously published under Q314060
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

For a Microsoft Windows 2000 version of this article, see 270008.

After you remove either compact disc (CD) recording software or other software from your computer, your computer may exhibit the following behavior:
In My Computer, there is no access to your CD-ROMs.
In Device Manager, the following error message appears in connection with any CD-ROM device that is part of your computer system:

The device is not working properly because Windows cannot load the drivers required for this device (Code 31).
Device Manager displays the following error message:

A driver for this device was not required, and has been disabled (Code 32 or Code 31).
You may also receive an error Code 39 message that indicates that the driver is corrupted.

Device Manager displays the following error Code 19 message, which means that the registry returned some unknown result:

Your registry might be corrupted. (Code 19)
You may also receive the following error message:

Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this behavior, follow these steps:
Start Registry Editor (Regedt32.exe).
Locate the UpperFilters value under the following key in the registry:


On the Edit menu, click Delete, and then click OK.
Locate the LowerFilters value under the same key in the registry:


On the Edit menu, click Delete, and then click OK.
Quit Registry Editor.NOTE: After you remove the Upperfilters value and the Lowerfilters value, if you notice lost functionality in a particular program, such as CD recording software, you may need to reinstall that software. If the problem recurs, consult with the software vendor for assistance.

Restart your computer.
This is a known issue that can occur when you remove Easy CD Creator version 5.01 or earlier or DirectCD version 3.01c or earlier. This issue may also occur with Easy CD Creator version 5.01 and with DirectCD 3.01d or later.
There may be other third-party CD-writing software products that exhibit similar behavior. Some or all of the troubleshooting steps in this article might apply if such a product also adds entries under the UpperFilters or LowerFilters value in the registry, either by adding its own filter drivers or by removing the registry keys and values outlined in this article that begin with:


WARNING: Make sure that you perform a backup of your registry before making any changes. The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Last Reviewed: 10/25/2002

COPYRIGHT NOTICE. Copyright 2002 Microsoft Corporation, One Microsoft Way, Redmond, Washington 98052-6399 U.S.A. All rights reserved.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MeckrosAuthor Commented:
Wow I sure went through a lotta trouble for nothing, I guess I didn't search quite good enough, thanks a lot.
Who knows what other wacky fixes I might have tried.
Hehehehe I know what mean.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.