How to Open Device Manager from CMD

Device Manager is where you go when hardware stops behaving like hardware should. It shows missing drivers, disabled adapters, faulty USB devices, failing Bluetooth radios, and a long list of other problems that Windows often hides behind vague messages like "device cannot start."

If you already have Command Prompt or PowerShell open, the fastest route is to launch Device Manager directly.

Command to Open Device Manager

Use:

devmgmt.msc

That opens the standard Device Manager console immediately.

Why This Shortcut Matters

Typing devmgmt.msc is not just about saving clicks. It is useful when:

• the Start menu is lagging or unresponsive
• you are walking a user through support steps over chat
• you are already in an elevated shell
• you are documenting a repeatable troubleshooting process

For support work, small time savings add up fast.

What You Can Check in Device Manager

Once the console opens, focus on a few high-value checks:

Yellow warning icons

These usually indicate missing drivers, failed devices, or resource conflicts.

Unknown devices

This often means Windows detected hardware but does not have the right driver package.

Disabled devices

A network card, camera, or Bluetooth adapter may simply be disabled rather than broken.

Driver version and rollback options

Under Properties > Driver, you can inspect version, provider, update history, and whether rollback is available.

Good Cases for Opening Device Manager from CMD

Network adapter disappeared after an update

Open Device Manager and inspect Network adapters. If the adapter is disabled or has a warning icon, you are already in the right place.

USB device is detected intermittently

Use View > Show hidden devices to reveal old or disconnected device entries that may be causing conflicts.

Webcam or microphone stopped working

Check whether Windows sees the device at all before you waste time changing application settings.

Useful Companion Commands

Device Manager is the GUI view, but modern Windows also gives you useful command-line tools.

List installed drivers

pnputil /enum-drivers

List devices known to the system

pnputil /enum-devices

Show detailed PnP state for troubleshooting

pnputil /enum-devices /problem

That last command is useful when you want to identify hardware problems from a remote shell without opening the GUI first.

How to Reveal Hidden or Ghost Devices

Windows can retain stale device entries after:

• replacing a NIC
• moving a VM to different virtual hardware
• connecting many USB serial devices over time
• reinstalling drivers repeatedly

Inside Device Manager:

1. Click View.
2. Select Show hidden devices.
3. Expand the relevant hardware category.

If duplicate or stale entries are visible, remove them carefully and then rescan hardware.

Common Fixes You Can Perform from Device Manager

Update driver

Best when Windows is using an older or generic driver that does not fully support the device.

Roll back driver

Useful when the problem started right after a vendor or Windows Update driver change.

Disable and re-enable device

Often enough for adapters that entered a bad state.

Uninstall device and scan for hardware changes

Helpful for corrupted device registrations or partially installed drivers.

Common Errors and What They Usually Mean

When Device Manager Is Not Enough

If the console shows no error but the hardware still fails, the problem may be outside Windows:

• BIOS or UEFI setting disabled the device
• physical cable or port failure
• docking station or hub issue
• firmware problem
• endpoint security policy blocking the device class

In those cases, Device Manager helps confirm what Windows sees, but it is only one layer of the investigation.

Bottom Line

To open Device Manager from CMD, use:

devmgmt.msc

It is the fastest way to inspect drivers, hardware state, and common device errors. Pair it with pnputil when you need scriptable diagnostics or remote command-line troubleshooting.