Laptop CD-DVD drive not recognized in Win 10 64 bit.

Reply

  #1  
Old 12-16-17, 01:38 PM
Norm201's Avatar
Member
Thread Starter
Join Date: Sep 2013
Location: United States
Posts: 7,344
Received 64 Votes on 59 Posts
Question Laptop CD-DVD drive not recognized in Win 10 64 bit.

Gentlemen, I need help.

I have two CD-DVD drives. One is built into the computer, the otheros a USB connected. Without warning something disconnected them.
This is the error code:
Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

They show-up in device manager as unknown. I have exhausted all possible ideas including the following from MS web site: https://support.microsoft.com/en-us/...other-programs
Method 1: Use the Hardware and Devices troubleshooter

Method 2: Check BIOS settings and chipset drivers

Method 3: Update or reinstall the driver

Method 4: Remove and reinstall IDE/ATAPI drivers (note: When I expand IDE/ATAPI Controllers, I do not have the ATA Channel 0, ATA Channel 1, Standard Dual Channel PCI IDE Controller selection.

Method 5: Fix corrupted registry entries (note: on this method I did not have upper or lower filters. So, as instructed I deleted the entry as instructed)

Method 6: Create a registry subkey


None of these fixes, fix it!
 
Sponsored Links
  #2  
Old 12-17-17, 05:29 AM
Bob14525's Avatar
Member
Join Date: Jun 2013
Location: USA
Posts: 1,470
Received 11 Votes on 8 Posts
Norm, this article may cover some/all of the things you've tried, but it's worth a look.

https://www.drivereasy.com/knowledge...to-windows-10/
 
  #3  
Old 12-17-17, 05:49 AM
Norm201's Avatar
Member
Thread Starter
Join Date: Sep 2013
Location: United States
Posts: 7,344
Received 64 Votes on 59 Posts
Thanks Bob, but as my post says I tried every one of these fixes.
 
  #4  
Old 12-17-17, 09:46 AM
Member
Join Date: May 2010
Location: USA
Posts: 430
Received 10 Votes on 8 Posts
Sorry for not following through to see what all those steps entail, but did any of them include uninstalling the device(s) in Device Manager and rebooting?

WinKey+R> devmgmt.msc



This doesn't do anything destructive, it just deletes the old configuration bits and driver associations and such. When Windows awakens after the reboot and finds an unemployed device hanging around, it automagically will (re-)install it and put it to work. Provided it still can find the drivers. Ordinarily (in the post-XP world) it won't even alert the user to what it's doing. The majority of all optical devices run on Windows' native drivers but if yours used proprietary drivers (if it did, you'd probably have noticed during the install), you might want to dig up replacements/updates and have them on stand-by. I've never yet seen Windows not be able to find the old drivers, but then again I've never yet seen the error message you're getting.

And RE: that error message, I wouldn't take to much stock in it. They don't bother teaching Windows how to interpret every error message that could occur (that's what keeps all their SysAdmins employed) and sometimes it's just taking its best guess. When it's a more 'exotic' error message, like this one, I always have to remind myself not to overlook the basic troubleshooting steps.
 
  #5  
Old 12-19-17, 03:20 PM
Member
Join Date: Nov 2012
Location: USA
Posts: 1,231
Received 24 Votes on 20 Posts
Windows 10 does not play nicely with cd/dvd drives on laptops.
I've tried this many times on a netbook, which doesn't work, while plugging the same usb drive into a desktop does.

Best solution I've found is to make ISO's of the important DVDs, save them to a network drive,
then copy them to the laptop and mount them in Win-10 as ISOs.

It's just not worth your time trying to get Win10 to recognize a laptop cd/dvd drive.
 
  #6  
Old 12-19-17, 03:24 PM
Norm201's Avatar
Member
Thread Starter
Join Date: Sep 2013
Location: United States
Posts: 7,344
Received 64 Votes on 59 Posts
Problem is, it did recognize it until last week.
 
  #7  
Old 12-22-17, 10:12 AM
Member
Join Date: Jan 2008
Location: Southeastern Pennsylvania
Posts: 2,947
Received 0 Votes on 0 Posts
Norm –

I hope things are working for you by now.

The fact that the internal DVD/CD drive and the external USB DVD/CD drive both stopped working would seem to point to something common to both – which I think would be the cdrom driver. In troubleshooting they have you uninstall and reinstall the cdrom driver which should have corrected your problem if in fact it was a cdrom driver problem.

The atapi driver should not have anything to do with whether or not the USB DVD/CD drive would work – but would affect the internal DVD/CDROM accessibility. The atapi driver would be used for the internal DVD/CDROM drive. However, if you did in fact add the atapi controller0 key in the registry as they suggest, then it does not seem right that you still don’t see anything listed in for the atapi controllers in Device Manager. You should see controller0 in Device Manager.

I have W7 not W10 but when I look at the registry subkey:

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

I see “default = DVD/CD-ROM drives” and “Class = CDROM” etc.

when I expand folder “0000” under that subkey I see driver information: DriverVersion, InfPath etc.
You should see something like that.

It might just be as Fred suggests, there really is another problem here, not something that a simple registry editing or driver uninstall-install procedure will fix – but that’s all they know how to try at this time.

Maybe you need to do a system restore from a restore image if you have one. This problem may have been caused by one of their automatic updates and that’s why it happened all of a sudden (when I worked as a SW guy for over 30 yrs I can’t tell you how many times I heard “ but my change wouldn’t have anything to do with that” – Oh yea? Then when you find the problem you proceed to show them the connection in the software.– LOL).

I wonder if you could back up a system image right now, then drop back to some previous image and see if the problem disappears. If it did, and you were OK with running with the older image, then you’re done. If not you could come forward to the image you saved.

But on the other hand, I really don’t understand the W10 updating philosophy. If MS forces all updates all the time, then it seems like dropping back to a prior image is almost meaningless.
 
Reply

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Thread Tools
Search this Thread
Display Modes
 
Ask a Question
Question Title:
Description:
Your question will be posted in: