Question Locked

tsst corp cd/dvdw ts-h552d

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
will not read any disc please help

6 replies

by Former member

Go into "device manager":
start > settings > control panel >
system > device manager. Look under "DVD/cd drives" and see if the drive in question has a red or yellow tag next to it. If it has right click on it and select "update drivers" (you might need the driver disk, if it came with it), select "browse" and select one of the drivers in the list. If it does not work, then right click on the drive in question and select "delete", this will remove the drive and then re-install when you reboot your computer.
Hope this helps you.

Please post back if you have anymore problems or questions.

by peter

the above should work (i think the option in device manager is uninstall drive though)

my workaround has been to uninstall the device through device manager, then reboot, allow windows to DISCOVER the device after reboot, on the first pop-up say yes, and on the second CANCEL. Windows will report that the "Windows was unable to install the necessary software", but the drive can still be read from and written to because generic drivers are being used.

The downside to this workaround is I'm prompted to install drivers every time the computer reboots. Luckily for me, the machine my samsung is installed in never needs to shutdown.

The disc that accompanied my drive only had a firmware update utility and Nero software on it. No drivers. Me thinks samsung was hoping M$ included compatible drivers with the OS or a service pack.

by Former member

A firmware update this will cure some issues about the drive not being recognized.

Please post back if you have anymore problems or questions.

by robo_dev

There's a weird issue that can happen with Nero where a certain registry key causes the drive to stop working.

http://support.microsoft.com/kb/314060

The first time I saw this, I swapped the drive, then the drive again, then the motherboard, and then stumbled upon this issue. It happens in either XP or Vista.

This discussion is closed to new replies.