Unfortunately, when switching to the “top ten” with the seventh and eighth version of “Windows”, it happens that Windows 10 does not see the DVD drive, although everything was fine before. Moreover, it is defined in the BIOS, you can boot from it, but the system itself, even though you crack it, does not want to see it. What to do?
Why can't Windows 10 see a DVD drive?
To begin with, the output of the “tens”, as is commonly believed, was not authorized or, if you like, synchronized with manufacturers of equipment of this type.
So it turns out that the system does not perceive outdated drivers, but there are no new ones. Now everything is simple. Nevertheless, for many users the problem that Windows 10 does not see the DVD drive remains. Let's see what can be done in this situation.
Windows 10 does not see CD-DVD drive: troubleshooting technique
In general, the problem initially boils down only to installing drivers corresponding to the "top ten" and registering the device in the system.
The first item is solved quite simply by the usual installation of fresh drivers. Don't want to do this manually when Windows 10 doesn't see the DVD drive? No problems. Use automation applications like Driver Booster, which can update device drivers directly from the developer's site. And do not dig into the Windows 10 driver database, it still does not work.
On the other hand, the driver may have been installed, but the device itself does not work just because it is not registered in the system, or rather, in the system registry. To register, use the command line call from the Run menu. This can be done through a combination of Win + R keys or from the right-click menu on the Start button. And then enter the combination shown in the photo below.
After that, press "Enter" and exit the command console. Now it remains just to reboot the system, and the problem that Windows 10 does not see the DVD drive will completely disappear. Actually, the search for a solution to eliminate it comes down only to installing the latest device drivers or registering the drive in the system so that it recognizes it.
Conclusion and Summary
If you carefully look at the registration command, it is easy to determine what it means to enter data into the system registry, and with the controller assigned the DWORD parameter of 32 bits. By the way, many might think that, as they say, in a 64-bit system, 32-bit registration is not applied. Deep delusion. In the "top ten", most drivers have a 32-bit architecture and work without problems. But on the contrary, when a 64-bit driver is installed on a 32-bit system, the system simply “spits” and says that such an architecture is not supported.
It goes without saying that after all the above steps, a system reboot should be performed. Without this, the positive effect can not even be expected. It’s not even a matter of registering the device, but rather of the fact that it will be determined later by the system, but will not want to work. In this moment the driver plays the leading role.
If the equipment manufacturer claims to support the “dozens,” there is no problem, but if, for example, it is specific Chinese equipment, it may very well be that you will have to install “native” drivers. And they, as you know, in the environment of “tens” may not work. Moreover, Microsoft itself has never declared such support, considering (and not without reason) Chinese manufacturers as its direct competitors in the computer technology market. What is the recent test of the most powerful Sunway TaihuLight computer with the ability to perform 125 quadrillion operations per second floating point!