Where is the "Device Manager" Windows and the easiest ways to call it
Apparently, every user knows that you can view all the “iron” and virtual devices installed on Windows systems through a special applet called the dispatcher. However, not everyone is aware of where the “Device Manager” is located in the XP version of the operating system or in the modifications above. On this occasion, it is necessary to give a separate explanation regarding the physical location of the executable file, which is responsible for the operation of the dispatcher, and how to call the applet without directly launching the executable component.
Where is the "Device Manager" in terms of the physical location of the file?
In general, all the main files of executable services that are accessible to the user either through the GUI, or via the Run console, or via the command line are located in the System32 system directory, which is located in the main directory of the operating system itself.But, speaking about where the “Device Manager” is located, it should be taken into account that you will not find an executable component with the .exe extension. The fact is that the component itself belongs to the so-called documents like Microsoft Common Console and has the MSC extension.
What is most interesting, in terms of the location, the console (and this is the console) can be located simultaneously in two locations, if the computer has the Windows version with 64-bit architecture installed. The first folder is known (System32), and the second is SysWOW64, not counting the accompanying components that can be found anywhere (just search the “Explorer” for the name of the devmgmt file you are looking for, the abbreviation for which is derived from English Device Manager).
Where is the "Device Manager" in Windows: a program call the simplest method
So, with the location of the main object figured out. Now let's see how you can get to this applet using the graphical interface of the operating system itself. Where is the "Device Manager" Windows 7 in the standard location? No need to go far.
Simply call the "Control Panel", where the corresponding section will be presented.With the tenth modification, the situation is somewhat more complicated, since the “Control Panel” must be called up either via the RMB on the “Start” button, or use the “Run” menu for this with the entry of the control command.
Direct Call via Execution Console
And it is this menu that makes it quite easy to find a solution to the problem about how to call this dispatcher. In our case, it does not matter where the “Device Manager” is located, since the execution of the launch command will automatically work for the component we need, regardless of its location.
The devmgmt.msc string (the original name of the executable component plus the console extension above) is entered in the console, after which either the 32-bit or 64-bit version of the program starts (depending on which system is installed on the computer). You can run files from the above folders. Get the same.
Using the management / administration section
It’s no secret that you can use the management or administration section to call some procedures related to the system toolbox.
To do this, you need the PCM menu on the computer icon on the "Desktop" (in Windows 10 - in the "Explorer"), where the corresponding line is selected, and after calling the main editor, you are transferred to the dispatcher.
Note: you can even use the command line for access, but in this case it seems like a more complicated solution.
With questions about where the "Device Manager", figured out. Now very briefly about its purpose. In the most general sense, it is designed to control all devices that are only on the computer, regarding their switching on and off, tracking information, as well as solving all issues related to installing the necessary control software in the form of drivers. The dispatcher itself has one interesting feature that many do not know about. In the information block, you can get information about the identifiers of VEN and DEV hardware, which allow you to find a driver for almost any installed device, even if Windows cannot install it on its own. No other system tool provides such information.So to neglect such a toolkit in the absence of a disk with the original drivers is not worth it.