{"id":55,"date":"2009-01-10T14:09:07","date_gmt":"2009-01-10T09:09:07","guid":{"rendered":"http:\/\/www.devicedriverfinder.com\/blog\/?p=55"},"modified":"2009-02-24T22:14:05","modified_gmt":"2009-02-24T17:14:05","slug":"fix-code-39-errors-for-cddvd-devices","status":"publish","type":"post","link":"https:\/\/www.devicedriverfinder.com\/blog\/device-errors\/fix-code-39-errors-for-cddvd-devices","title":{"rendered":"Fix Code 39 Errors for CD\/DVD Devices"},"content":{"rendered":"

When you troubleshoot computer errors, the Windows Device Manager<\/a> can be a helpful resource. It will show you which devices are working and which are not. Unknown or Other devices will list drivers which do not have a correct driver or no driver at all.<\/p>\n

A yellow explanation mark can indicate a device error. The error details for the device can then be helpful in solving the error. If you see a code 39 error for a CD-ROM or DVD drive, the message will be “Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.”<\/p>\n

The first thing to do is to run a driver check to make sure your drivers are up to date. You can manually check your drivers or use a tool like Driver Checker<\/a> or DriverScanner<\/a> to automatically check all drivers. Be sure to verify that the motherboard drivers and IDE\/ATA drivers are also up to date.<\/p>\n

If the driver update does not fix your code 39 error, there is a possibility that the registry is corrupt for the DVD\/CD-ROM class. There are different possible causes for this, one being installing, uninstalling or updating CD creating software like Nero or Roxio<\/a>. Another option is that an upgrade from XP to Vista failed to update the registry properly for the filter settings.<\/p>\n

The way to fix this is to delete some entries in the registry related to the DVD\/CD-ROM class. Make sure you make a backup of the registry first!<\/p>\n

    \n
  1. In the Windows Start<\/strong> menu, select Run <\/strong>and type “regedit<\/strong>” in the Run <\/strong>dialog box.<\/li>\n
  2. Press Enter <\/strong>or click OK <\/strong>to open the Windows Registry Editor.<\/li>\n
  3. In the Registry Editor<\/strong>, locate the following registry key:
    \nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Class\\{4D36E965-E325-11CE-BFC1-08002BE10318}<\/strong><\/li>\n
  4. There will be many such entries, so check the (Default) <\/strong>value, which should contain “DVD\/CD-ROM<\/strong>“.<\/li>\n
  5. In the right-hand pane, right-click the LowerFilters<\/strong> entry, and in the popup menu select Delete<\/strong>.<\/li>\n
  6. Repeat step 5 for the UpperFilters<\/strong> entry.<\/li>\n
  7. Now close the Registry Editor and reboot the computer.<\/li>\n<\/ol>\n
    \"Edit<\/div>\n

    After this the DVD\/CD-ROM device should no longer be listed with an error or yellow explanation mark. In some cases you might need to reinstall CD-Burning software to restore all functionality, but that won’t be a problem because it would not have been working in the first place.<\/p>\n

    You can read the Microsoft article on Vista upgrade problems causing this error here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Most device manager errors are caused by driver problems, but in the case of CD-ROM and DVD drives, there is a possibility that a code 39 error is caused by a registry problem. Learn how to fix code 39 errors in these cases.<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[7,9,8],"class_list":["post-55","post","type-post","status-publish","format-standard","hentry","category-device-errors","tag-cdrom","tag-code-39","tag-dvd"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/posts\/55","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/comments?post=55"}],"version-history":[{"count":6,"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/posts\/55\/revisions"}],"predecessor-version":[{"id":99,"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/posts\/55\/revisions\/99"}],"wp:attachment":[{"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/media?parent=55"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/categories?post=55"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devicedriverfinder.com\/blog\/wp-json\/wp\/v2\/tags?post=55"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}