Windows 10 does not see a DVD drive: what is it that is decent and what should I do?

Unfortunately, when switching to the "top ten" from the seventh and eighth versions of "Windy" it happens that Windows 10 does not see the DVD-drive, although everything was fine before. Moreover, in BIOS it is defined, it is possible to boot from it, but the system itself, even though you crack, does not want to see it. What to do?

Why does Windows 10 not see the DVD drive?

To begin with, the output of the "tens", as it is commonly believed, was not sanctioned or, if you want, synchronized with the manufacturers of this type of equipment.

So it turns out that the outdated drivers do not perceive the system, but there are no new ones. Now everything is simple. Nevertheless, many users have the problem that Windows 10 does not see the DVD-drive, it remains. Let's see what can be done in this situation.

Windows 10 does not see the CD-DVD drive: the problem-solving technique

In general, the problem initially reduces only to installing drivers that correspond to the "top ten", and registering the device in the system.

The first point is solved simply by the usual installation of fresh drivers. Do not want to do this manually when Windows 10 does not see the DVD drive? No problems. Use application-automatons, like Driver Booster, which are able to update device drivers directly from the developer's site. And do not dig in the database of Windows 10 drivers, it still does not work.

On the other hand, the driver may be installed, but the device itself does not work only because it is not registered in the system, or rather in the system registry. To register, use the command line from the "Run" menu. This can be done through a combination of keys Win + R or from the right-click menu on the "Start" button. And then we enter the combination shown in the photo below.

After that, press "Enter" and exit the command console. Now it just remains 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 fix it is reduced only to installing the newest device drivers or registering the drive in the system, in order for it to recognize it.

Conclusion and total

If you look closely at the registration command, it is easy to determine what it is by entering data into the system registry, and assigning 32 bits to the controller of the DWORD parameter. By the way, many people might think that, 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 in a 32-bit system, the system simply "spits" and says that this architecture is not supported.

It goes without saying that after all the above actions, the system must be rebooted. Without this, you can not even count on the positive effect. Here, it's not even that the device will be registered, but rather that it will be later determined by the system, but it does not want to work. In this moment, the driver plays the dominant role.

If the manufacturer of the equipment declares support for the "dozens", there are no problems, and if it is, for example, specific Chinese equipment, it may very well be necessary to install "native" drivers. And they, as is known, in the "dozens" environment may not work. Moreover, the corporation Microsoft has never claimed such support, considering (and not without reason) the Chinese manufacturers its direct competitors in the computer technology market. What's worth is the recent test of the most powerful Sunway TaihuLight computer with the ability to perform 125 quadrillion operations per second with a floating point!