The Device Is Not Open: Fix Device Manager
If Device Manager will not open from Start, Run, Task Manager, or devmgmt.msc, sort the fault into three paths: launch-path failure, system-file corruption, or executable or registry blocking, then fix the matching path. Ignoring it can leave hidden hardware faults, driver conflicts, and recovery problems unresolved. This guide shows how to identify which path you have and what to try next.
What “the device is not open” usually means
Most readers mean one of two things: Device Manager will not open at all, or it opens and closes so fast that only a loading cursor appears. In Windows 11, that difference can matter. A broken Start shortcut points somewhere else from a blocked devmgmt.msc or mmc.exe launch.

Separate launch failure from a missing device category
Device Manager is the Windows utility for listing hardware devices and drivers. If it will not launch, focus on the shell, MMC snap-in, or system files first. If it opens but Bluetooth is missing, do not chase launch repairs yet; inspect whether Bluetooth hardware or drivers are actually exposed in the device tree.
A common first-timer mistake is to assume the Settings app will always show Bluetooth if Device Manager does not. That is too broad. What matters is whether the system has exposed Bluetooth hardware or drivers at all, because missing hardware, disabled adapters, and driver problems can each produce different views.
Device Manager decision checklist
Use this as a fast sorter before you start deeper repairs. Match the symptom you can verify, then test the quickest branch first. That saves time and keeps you from running repair tools that do not fit the failure.

| Symptom | Likely cause | Fastest test | Next action |
|---|---|---|---|
| Start search finds Device Manager, but clicking it does nothing | Broken shortcut, Start entry, or shell issue | Open devmgmt.msc from Run | If Run works, repair the shortcut path; if not, move to MMC or file checks |
Run dialog accepts devmgmt.msc, then flashes and closes | MMC launch blocked or damaged | Open it from Task Manager as a new task with admin rights | If it still flashes, check for executable blocking, system file damage, or malware |
SFC /scannow reports corruption it cannot fix | Deeper Windows component damage | Run DISM health checks | Use /CheckHealth, /ScanHealth, then /RestoreHealth |
| Device Manager still will not open after SFC and DISM | Persistent OS damage, blocked MMC, or a bad restore point state | Check whether it worked before on this PC | Try System Restore, then a repair install if needed |
| Device Manager opens, but Bluetooth is missing | Missing hardware exposure, disabled adapter, or driver issue | Look for Bluetooth under hidden or other devices | Inspect hardware visibility and driver state, not launch fixes |
| Nothing opens from multiple paths, including Run and Task Manager | MMC/executable blocking or broader system corruption | Try an elevated task and then Command Prompt | Move to SFC, DISM, malware checks, and repair install if needed |
Why does Device Manager flash and close?
A brief devmgmt.msc flash usually means Windows started the MMC snap-in and then stopped before the console could render. That pattern points to a damaged or blocked MMC launch path more often than a simple Start-menu shortcut problem. If the same flash happens from Run and Task Manager, treat it as more than a bad shortcut.
What a flash-and-close points
Device Manager does not have its own separate app window. It opens through mmc.exe, which loads the Device Manager snap-in. If the snap-in launches for a moment and exits, the trouble may sit in MMC, in the snap-in registration, or in a block applied to the executable itself.
Say your PC shows the cursor for a second after devmgmt.msc, then nothing. If Start search also fails, that is not the same as a damaged shortcut in one menu. It suggests the command path itself is being interrupted, so the next step should test a different launch route with elevation.
When the issue points to blocking
If the same command fails from Run, Task Manager, and Command Prompt, then the evidence starts to favor executable blocking, registry damage, or deeper Windows corruption. A Microsoft Q&A case on a similar pattern tied the issue to mmc.exe and noted that a registry block could prevent executables from opening Device Manager. (Microsoft Learn)
That does not prove malware every time. It does mean you should verify whether only MMC-based tools fail, whether other administrative consoles open, and whether security software or policy changes were made before the failure started.
How do you open Device Manager from Task Manager?
Task Manager can launch devmgmt.msc with administrative privileges, which is useful when Start search or Run is unreliable. Open Task Manager with Ctrl + Shift + Esc, choose to run a new task, and enter the command there. If Task Manager can launch it, the problem may be limited to the user shell.
Run devmgmt.msc with admin rights
- Press Ctrl + Shift + Esc to open Task Manager.
- Select Run new task.
- Type
devmgmt.msc. - Check the option to create the task with administrative privileges.
- Select OK.
If that opens Device Manager, the issue may be limited to a non-elevated launch path or a broken shortcut. If it still fails, try Command Prompt next, then Computer Management, which TechViral lists as another path to Device Manager.
Try Command Prompt or Computer Management next
Open an elevated Command Prompt and run devmgmt.msc. You can also open Computer Management and reach Device Manager from the console tree. These alternate paths help separate a bad shell shortcut from a broader MMC failure.
Microsoft says you can open Device Manager by selecting Start and entering device manager. TechViral also notes the Run dialog path with devmgmt.msc. If Start search fails but Run works, the issue is probably the shortcut or search entry, not the snap-in itself.
Can Windows repair system files stop this?
Yes. If Windows files that support the console or snap-in are damaged, SFC and DISM can clear the fault. Start with SFC /scannow. If that finds corruption or cannot fix everything, move to DISM health checks and then run the restore command.

Run SFC first
SFC /scannow checks for missing or corrupted protected system files and repairs what it can. It is the first pass because it is simple and local. If Device Manager still will not open afterward, that does not mean the repair failed; it may mean the damage is deeper than SFC can reach.
Use DISM when SFC is not enough
Guiding Tech recommends DISM after SFC when system files may block Device Manager. The usual sequence is /CheckHealth, /ScanHealth, and /RestoreHealth. The first two check whether the image is damaged; /RestoreHealth can download internal system files from Microsoft servers and replace what is missing or corrupt.
Use the commands in that order. If /CheckHealth says the image is repairable, /ScanHealth can take a closer look, and /RestoreHealth is the repair step. TechViral also recommends chkdsk C: /f when drive errors may be part of the problem, especially if the system feels unstable beyond Device Manager.
Suppose Device Manager stopped opening after a failed update and other admin tools also misbehave. That pattern points more toward system files or the Windows image than a single bad shortcut. In that case, SFC and DISM are the right branch before you try restore or repair install steps.
Use the System Maintenance Troubleshooter only if available
The System Maintenance Troubleshooter is a limited option, not a guaranteed fix. Guiding Tech includes it because it can address irregularities such as desktop shortcuts, disk volume issues, and file path problems. If it appears in Control Panel under Troubleshooting on your Windows build, it is reasonable to try before deeper repair work.
When should you use System Restore or repair install?
Use System Restore when Device Manager used to work on this PC and then stopped after a change. If the problem began after a driver update, security tweak, or other system change, rolling Windows back to an earlier restore point can remove the bad change without rebuilding the whole installation.
Choose System Restore if the PC used to work
The same source suggests System Restore as a last resort when Device Manager still will not open. That advice fits cases where the system had a known-good state. Launch it through create a restore point, then choose an earlier restore point that predates the failure.
The key question is timing. If Device Manager opened yesterday and fails today, System Restore is a sensible branch. If the problem has existed since setup, repair install or file repair is usually the better place to start.
Use repair installation through Windows Update
If SFC, DISM, and restore do not fix the issue, Windows 11 includes a repair path under Settings > System > Recovery. Look for Fix problems using Windows Update. In the Microsoft Q&A case, the suggested repair installation was the option that keeps files, apps, and settings.
That matters because it is more aggressive than a scan, but less disruptive than a clean install. It is the right move when the OS itself looks damaged and the simpler repairs did not restore MMC or Device Manager behavior.
Could malware or a blocked mmc.exe be the cause?
Yes, but treat that as a verification branch, not a default answer. A blocked mmc.exe can happen after malware, policy, or registry changes. The Microsoft Q&A thread also mentions Malwarebytes, which reportedly removed 9 PUPs during troubleshooting, but that kind of result does not prove malware is always the cause.
What to verify before blaming malware
Check whether only MMC-based tools fail, whether security software was changed, and whether the registry was edited. If Device Manager, Computer Management, and other console tools all fail in the same way, the problem may be a block against executables rather than a simple shortcut issue. If only one shortcut fails, the cause is more likely local.
If a security scan finds unwanted programs, remove them and retest. If the scan is clean but the symptom remains, go back to SFC, DISM, and then the repair install path. Do not assume malware just because the symptom looks odd. The launch pattern matters more than the guess.
Frequently asked questions
Why is Device Manager not opening in Windows 11?
In Windows 11, Device Manager usually fails for one of three reasons: the launch path is broken, protected system files are damaged, or mmc.exe is being blocked. Start by testing devmgmt.msc from Run or Task Manager, because that tells you whether the failure is local to a shortcut or deeper in Windows.
How do I open Device Manager if devmgmt.msc does nothing?
Open Task Manager with Ctrl + Shift + Esc, choose a new task, and run devmgmt.msc with administrative rights. If that fails too, try an elevated Command Prompt and then Computer Management. When every path gives the same blank or flashing response, move to SFC, DISM, and blocking checks.
Can I open Device Manager with admin rights?
Yes. Task Manager can run devmgmt.msc with administrative privileges, which is useful when the standard launch path fails. That does not guarantee success if the problem is system-file corruption or executable blocking, but it helps separate a permissions issue from a damaged launch path.
What should I do if SFC and DISM do not fix Device Manager?
If SFC /scannow and DISM with /CheckHealth, /ScanHealth, and /RestoreHealth do not solve it, try System Restore if Device Manager worked before. If that fails or is not available, use the repair path under Settings > System > Recovery and Fix problems using Windows Update.
Could malware block Device Manager from opening?
Yes, but it is less common than a broken shortcut or corrupted Windows files. A registry or executable block can stop mmc.exe and other console tools from opening. Verify the pattern first: if multiple MMC-based tools fail and a security scan finds unwanted programs, malware becomes a more plausible branch.
What if Device Manager opens but Bluetooth is missing?
Do not keep running launch repairs. That symptom means Device Manager is working, but the Bluetooth category may be hidden, disabled, or absent because no adapter is exposed. Check whether Bluetooth hardware appears under other device categories, whether the adapter is disabled, and whether the driver needs reinstalling.






