I have lost my dvd/cd drivers in Vista Ultimate by using the registry to
remove Nero 7, can someone tell me how to get them back,
Printable View
I have lost my dvd/cd drivers in Vista Ultimate by using the registry to
remove Nero 7, can someone tell me how to get them back,
Go to Control Panel\System. Under Tasks, open Device Manager. Expand
DVD/CD_ROM drives in the tree. Right-click on the device and choose Update
Driver Software.... Having Windows search automatically should work.
A similar loss of DVD-reading happened to me when removing the Adaptec
CD-writing software from a computer being upgraded to Vista. DVD-reading
was restored by some combination of allowing Windows to update driver
software, adding in some drivers I had saved beforehand and rebooting,
allowing me to continue with the Vista upgrade.
CD-writing programs are a good reason for doing a clean install of Vista
instead of doing an upgrade install. Typically the CD-writing software for
Windows XP is not suitable for Vista, but uninstalling the CD-writing
software in preparation for an upgrade to Vista can disable the DVD-reading
needed to do the Vista upgrade. When I installed Vista on a second computer
I did a clean install and did not remove the Nero CD / DVD software,
allowing the clean install to get rid of the old version of Nero (details of
the upgrade and its display and speaker problems are at
http://www.gottabemobile.com/forum/f....asp?TID=2129).
"Sam" <wdbl@alltel.net> wrote in message
news:B05ABE7E-3EA5-4A73-8202-737552CD5365@microsoft.com...
>I have lost my dvd/cd drivers in Vista Ultimate by using the registry to
>remove Nero 7, can someone tell me how to get them back,
Hi,
I have an XPC Barebones SD37P2 with a PIONEER DVD-RW DVD-111D ATA installed.
During a recent Vista update the driver (or registry) has become corrupted.
Microsoft Vista could not find an online solution--and yet this is a generic
cdrom driver. A volume error check did not resolve the problem. Please help!
PS: Windows tells me that the PIONEER software is up to date, further proof
that it is as the MS device window indicates, it's the cdrom.sys v.
6.0.6000.16386 that is out of whack. Please advise.