Hi, I've got a weird problem. I've just got XP set up -- installed on a new computer. When I load a CD Rom into the drive, the computer reads all the files, and then displays the CD volume name next to the drive icon in Win Explorer. When I double click on it to open it, nothing happens. When I right click, select either open or explore, nothing happens either. However, when the CD Rom has an autoplay file in it, the CD Rom actually runs it the moment the CD is loaded. And it reads the CD normally when I access it via command prompt. Is this a Win XP problem, driver issue, or hardware defect?

go here and follow instruction for removing upper and lower filters http://support.microsoft.com/default.aspx?scid=kb;EN-US;q270008 this is the solution i had the same problem

I had the same problem, but I've fixed it. I don't know exactly what caused it, but I can tell you how I fixed it. I went to www.xp-erience.org and downloaded the latest ASPI Layer drivers. I installed these and rebooted the machine. It still didn't work. Next I Uninstalled the DVD drive from Device Manager and got it to scan for changes again to reinstall it. It now works. I hope this helps. I'm not using a CDR drive so none of the registry edits helped, but this did. May the force be with you.

This is a WIERD problem! I had the same thing going on. I had 1 machine that the user could not view cd rom contents. It did not matter what the format (CD,CD-R, etc). If I logged in as the "Administrator" user, I could read any CD. I still could not view a CD even after I gave the user administrator rights to the machine. I followed the directions above. I first removed the upper and lower filter keys from the registry per the Micro$oft article. That did not work by itself. I then tried a modification of Tim's fix above. I just removed the device in the device manager. I rebooted the machine and XP found the device again. As far as I can tell, it reinstalled the same driver. I did not make any driver updates like Tim did. It worked just fine after that! I think that reinstalling the device driver did more to fix the problem than anything in the registry.