Optical Drive Needs Disable / Enable For Access

I can not access anything on an optical disk until the device is first disabled and then enabled in Device Manager.
The drive is visible in File Explorer but shows no contents except an .ini file.
The drive works fine otherwise and works properly as a boot device.

I have tried Update driver and also Uninstall device followed by system restart.
I have looked for another driver, but can't find one.

The driver is:

• Microsoft
• 6/21/2006
• 10.0.15063.0

I found others that have reported this problem on the web, which is where I found the disable/enable trick, but not an actual fix.

Any help or ideas?
Thanks.

 

What version of windows and do you know what drives they are.

If not use speccy to scan them for more info.
http://www.majorgeeks.com/files/details/speccy.html

 

Windows 10 Home 64-bit
version 1703 (OS build 15063.608)

ASUS DRW-24B1ST
https://www.newegg.com/Product/Product.aspx?Item=N82E16827135204

 

Does this happen with different optical disks?

 

Firmware updated?
https://www.asus.com/us/Optical-Drives-Storage/DRW24B1ST/HelpDesk_Download/

 

Yes

Thanks. Already looked there. No firmware availabale to download.

 

Version 1.00 2014/03/181.54 MBytes
ASUS DRW-24B1ST Firmware v1.00

 

That firmware is listed for Windows 7 and earlier.
I have Windows 10 64-bit. I do not see anything listed for Win-10 (or Win-8).

NOTE:
The date of the firmware version at the ASUS site does not match the date shown at other download sites.
http://www.driversguru.com/manufacturer/asus-pid-R>3792800>3793459>3796995
http://www.firmwarehq.com/Asus/DRW-24B1ST/files.html

There is even a later version, v1.03, dated 2010-02-09, but not for Windows 10.
I bought the drive in November 2013.

 

That is because they stopped updating that drive, so modern OSes have passed it by. They are not going to keep rewritting old fimware installers for old hardware & new OSes.
I'd try use one of the other falshes, run it compatibilty mode for XP or 7.

 

UPDATE: 2017 Sep 25 04:03 pm

I attempted to install both of the available firmware updates, v1.00 and v1.03.
Using the Properties dialog for each, I did not see how to run it in Compatibility Mode.
Neither firmware update was successful.

I found that Uninstall device in Device Manager, followed by Action -> Scan for hardware changes, has the same result as Enable/Disable.

Thanks for the help.

 

Open regedit and navigate to this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
Take a screenshot and post it.

 

OK, Eldon, here you go.

 

Ok.
I thought the problem might be related to UpperFilters /LowerFilters which are known to be the cause of numerous problems. But they are not presnt on your system - that's good.

However, the same key on my system shows an additional value - Installer32.


Do the following:

1. Right-click 4D36E965-E325-11CE-BFC1-08002BE10318 and click Export. Give the file a name and save it somewhere.
2. Right-click 4D36E965-E325-11CE-BFC1-08002BE10318 > Delete.
3. Unzip CD-ROM.zip.
4. Right-click CD-ROM.reg > Merge.

Restart your computer.

 

Hey, I like this! It got interesting.

Had some trouble deleting the registry key. There was an access denied error for some portion (Properties sub-key).
I restarted in Safe Mode, but that did not help.
Then I did an Uninstall device for the CD-ROM in Device Manager. Delete key (in Registry Editor) still produced an error.
I was able to delete each individual value separately in the first key, then Delete key and sub-keys worked.

I don't have an actual "merge" option for right-click on a .reg file.
I used Open with -> Registry Editor and then merged the file.

I addition to the missing Installer32 value, the first (Default) value was incorrect.


Success!
Congratulations, Eldon
You da man. It worked.
Don't be surprised if this thread gets more views over the next weeks and months.
This may be the only commonly accessible solution available on the Web right now.

How did you know which key to look at?

Thanks, bud.
I thought it was game over, no solution.

 

Some years ago looking for a solution to an UpperFilters/LowerFilters problem, I found the key and made a note.
While your issue was not related to the filters, it turned out there was a problem with the registry key.

Great that the problem is fixed.

 

I been around computers since the 80's and been using windows since 1.1 and never heard of these filters.

Guess you can learn some thing new every 20 years lol.

 

This particular problem was not caused by the UpperFilters/LowerFilters.

FYI The correct terminology is Upper Filter Drivers and Lower Filter Drivers.
They augment a driver's functionality.

https://www.techspot.com/community/topics/understanding-device-drivers-and-filters.137665/