A non-functioning Device Manager usually points to system or driver-level problems — and most causes are fixable. If Device Manager doesn’t work on Windows 10, this article explains why it happens and gives clear, step-by-step fixes you can follow, from quick checks to advanced repairs.
You’ll learn the common causes (corrupted system files, disabled services, driver conflicts, permissions, updates, hardware issues, malware, and more) and how to resolve each one safely.
Key Takeaway
The most effective first step is to run system repairs and restart the key Windows service for hardware management: run sfc /scannow, DISM /Online /Cleanup-Image /RestoreHealth, then ensure the Plug and Play service is running; if that doesn’t help, update or reinstall drivers from an elevated Device Manager session or use System Restore.
Quick Fix Guide
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| Corrupted system files | Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth then reboot. |
| Plug and Play / services disabled | Enable and start the PlugPlay service in services.msc and restart. |
| Outdated or corrupted drivers | Update, roll back, or uninstall problem drivers in Device Manager. |
| Not running as administrator / permissions | Open devmgmt.msc or Device Manager with Run as administrator. |
| Group Policy or registry restriction | Check gpedit.msc and relevant registry keys for device installation restrictions. |
| Recent Windows Update conflict | Uninstall the recent update via Settings > Update & Security > Uninstall updates or use System Restore. |
| Device Manager MMC or snap-in corrupted | Recreate the devmgmt.msc snap-in via mmc or copy from another PC. |
| Hardware or connection issue | Check physical cables/ports and test device on another computer. |
| Malware or third-party interference | Run a full scan with Windows Security or reputable antimalware tools and disable conflicting software. |
Detailed Fixes for “tu mets ici le problème du 9 reasons why Device Manager doesn’t work in Windows 10 (and how to fix it)”.
Below are the nine common reasons and how to fix each one. Follow steps in order from simplest to most advanced.
1. Corrupted system files
Why this causes the problem
- Device Manager relies on system libraries and management components. If Windows system files are damaged, the MMC snap-in or driver APIs may fail.
Step-by-step solution
- Open an elevated Command Prompt: press Win, type cmd, right-click Command Prompt, choose Run as administrator.
- Run the System File Checker: type sfc /scannow and press Enter. Wait until it completes.
- If SFC reports issues it can’t fix, run DISM: type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This can take 10–30 minutes.
- After DISM finishes, run sfc /scannow again.
- Reboot the PC and check Device Manager (press Win + X > Device Manager or Win + R then devmgmt.msc).
Notes
- Run these commands with internet access for DISM to download healthy components.
- Keep a restore point or backup before major repairs.
2. Plug and Play or other essential services disabled
Why this causes the problem
- Device enumeration and management require the Plug and Play service and related service dependencies. If disabled, Device Manager may not populate or function.
Step-by-step solution
- Press Win + R, type services.msc, and press Enter.
- In Services, find Plug and Play (service name PlugPlay). Double-click it.
- Set Startup type to Automatic, click Start if it’s stopped, then click OK.
- Also ensure Remote Procedure Call (RPC) is running and set to Automatic; Device Manager depends on RPC.
- Reboot and check Device Manager.
Notes
- If services immediately stop after you start them, check the Event Viewer (Windows Logs > System) for errors.
3. Outdated or corrupted drivers
Why this causes the problem
- Bad drivers can crash the Device Manager UI or hide devices. A corrupted driver package can prevent the device from enumerating.
Step-by-step solution
- Try opening Device Manager: Win + X > Device Manager. If it opens, expand problem categories (yellow exclamation marks).
- Right-click the suspect device and choose Update driver > Search automatically for updated driver software.
- If updating fails, choose Uninstall device and check Delete the driver software for this device (if present), then restart. Windows will attempt to reinstall drivers.
- For OEM drivers, download the latest drivers from the manufacturer website and install manually. Use the Browse my computer for drivers option or the downloaded installer.
- If a new driver caused the issue, use Properties > Driver > Roll Back Driver.
Commands/Tools
- To list installed drivers: open elevated CMD and run driverquery.
- To remove driver packages: pnputil /enum-drivers and pnputil /delete-driver oem##.inf /uninstall /force.
Notes
- Keep a copy of working drivers before uninstalling if possible.
4. User account or permissions problems
Why this causes the problem
- Device Manager needs administrative privileges for many actions. If your account lacks permissions or UAC is misbehaving, Device Manager can appear non-responsive.
Step-by-step solution
- Ensure you’re signed into an administrator account. Press Win, type Control Panel > User Accounts to check account type.
- Run Device Manager as admin: press Win, type devmgmt.msc, right-click and choose Run as administrator.
- If UAC settings are preventing actions, open Control Panel > User Accounts > Change User Account Control settings and temporarily set to a lower level (not recommended long-term). Test and reset afterwards.
- If the account is corrupted, create a temporary administrative account: Settings > Accounts > Family & other users > Add someone else to this PC, make it an administrator, log in and test.
Notes
- Don’t permanently lower UAC; use it for protection.
5. Group Policy or registry restrictions
Why this causes the problem
- Administrators or security software can block access to Device Manager or prevent device installation via Group Policy or registry keys.
Step-by-step solution
- If you have Windows 10 Pro/Enterprise, press Win + R, type gpedit.msc and press Enter.
- Navigate to User Configuration > Administrative Templates > Control Panel > Prohibit access to Control Panel and PC settings and ensure it’s Not Configured or Disabled.
- Check Computer Configuration > Administrative Templates > System > Device Installation for restrictive policies like “Prevent installation of devices not described by other policy settings.” Set to Not Configured if in doubt.
- For registry: press Win + R, type regedit, and go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Remove or set restrictive keys like NoDevMgr to 0 (backup first).
- Reboot and test.
Warnings
- Always back up the registry before changes: File > Export in regedit.
6. Recent Windows Update conflict
Why this causes the problem
- Sometimes an update changes drivers or system components and creates conflicts that break Device Manager.
Step-by-step solution
- Open Settings > Update & Security > Windows Update > View update history.
- Click Uninstall updates at the top. In the Control Panel window that opens, find the most recent update and click Uninstall.
- Alternatively create a System Restore point and perform a restore: Control Panel > Recovery > Open System Restore and choose a restore point before the problem began.
- Pause updates temporarily: Settings > Update & Security > Windows Update > Pause updates.
Notes
- Keep notes of installed updates so you can reinstall selectively after resolution.
7. Corrupted Device Manager MMC snap-in (devmgmt.msc)
Why this causes the problem
- The devmgmt.msc file or MMC configuration may be damaged — Device Manager won’t open or crashes.
Step-by-step solution
- Try launching from Run: Win + R, type devmgmt.msc and Enter. Observe any error text.
- If it fails, open mmc.exe: Win + R, type mmc, press Enter. Click File > Add/Remove Snap-in and add Device Manager; save a new console file.
- If MMC snap-in is corrupted, copy devmgmt.msc from another healthy Windows 10 PC with the same build to C:\Windows\System32 (requires admin).
- Re-register MMC components: open elevated CMD and run regsvr32 %windir%\system32\mmcndmgr.dll (if present) — note that DLL names vary; generally repairing system files (see item 1) is safer.
Notes
- Copying system files from another machine should be done only when versions match; avoid system instability.
8. Hardware or connection issue
Why this causes the problem
- Device Manager may seem broken because the hardware isn’t connected, powered, or is physically damaged.
Step-by-step solution
- For external devices, disconnect and reconnect cables, try different USB ports (preferably direct motherboard ports).
- Test the device on another PC to confirm it works.
- For internal devices, ensure connectors are seated and the device has power. If a recent hardware change caused the issue, remove or reseat the component.
- Use Hardware and Devices troubleshooter: press Win + R, type msdt.exe -id DeviceDiagnostic and follow the wizard.
- If a device draws too much power (USB), use a powered hub.
Notes
- If the device is intermittent, a hardware fault is likely. Replace cables or the device if necessary.
9. Malware or third-party software interference
Why this causes the problem
- Malware or aggressive security/driver utilities can block Device Manager or corrupt drivers.
Step-by-step solution
- Run a full scan with Windows Security: Start > Settings > Update & Security > Windows Security > Virus & threat protection > Scan options > Full scan.
- Use a second opinion scanner like Malwarebytes (free scan) to detect unwanted programs.
- Temporarily disable third-party antivirus or driver-management tools and test Device Manager. If the tool is the cause, uninstall or reconfigure it.
- If malware has altered system files, use the steps in item 1 (SFC/DISM) and consider a clean install if infection persists.
Notes
- Always keep antivirus updated. If you remove antivirus, ensure another protection method is in place.
Preventive Maintenance and When to Seek Help
- Keep drivers and Windows updated, but install updates in small batches and create restore points before major updates.
- Backup important drivers and create periodic system restore points: Control Panel > Recovery > Configure System Restore.
- If the fixes above fail or you’re uncomfortable editing the registry, contact a trusted technician or Microsoft Support. For company-managed devices, check with your IT department before changing Group Policy or drivers.
FAQ
How can I open Device Manager if the GUI won’t launch?
Try Win + R, type devmgmt.msc, and press Enter; or open an elevated Command Prompt and run mmc devmgmt.msc. If it still fails, use sfc /scannow and DISM (see above).
Can I reinstall Device Manager?
You can’t separately reinstall Device Manager, but repairing Windows system files with sfc /scannow and DISM /RestoreHealth, or copying a healthy devmgmt.msc from a matching Windows 10 build, effectively restores its functionality.
Will resetting Windows fix Device Manager problems?
A Windows Reset (Settings > Update & Security > Recovery > Reset this PC) can fix deep issues, but it’s a last resort because you may lose apps and settings. Try System Restore first.
How do I prevent driver conflicts in the future?
Keep drivers current from manufacturer sites, avoid driver updater utilities that install unsigned drivers, and create a System Restore point before large driver changes.
Does Safe Mode affect Device Manager?
Device Manager works in Safe Mode but only shows basic drivers. Safe Mode is useful to remove problematic drivers or apps without interference from third-party software.
Conclusion
Most cases of Device Manager doesn’t work on Windows 10 are caused by corrupted system files, disabled services, bad drivers, or third-party interference, and can be fixed with SFC/DISM scans, service checks, driver updates, and malware scans. Start with the simple checks (services, admin access, SFC/DISM) and progress to driver reinstall, Group Policy checks, and System Restore if needed — and seek professional help if problems persist.
