Fix an Empty Device Manager in Windows 7, Vista, or XP — Historical Guide

Historical support note: This article covers Windows 7, Windows Vista, and Windows XP, all of which are unsupported.

An entirely empty Device Manager is different from one or two missing devices. It can indicate a damaged management component, service problem, corrupted system files, profile issue, or permissions damage.

1. Restart and verify the behavior

Restart Windows and reopen devmgmt.msc. If Device Manager works in another administrator account, the original profile may be damaged.

2. Check Plug and Play

Open services.msc and locate Plug and Play. On these Windows versions it should not be disabled. Do not change unrelated hardware services in bulk.

3. Run System File Checker

On Windows Vista/7, open an elevated Command Prompt and run:

sfc /scannow

Windows XP may request installation media while SFC repairs protected files.

4. Use System Restore if the problem began recently

If Device Manager became empty after a software, driver, or registry change, restore to a point from before the change where practical.

5. Test another administrator account

Create or use another administrator profile and open Device Manager there. This helps separate per-user shell/profile corruption from a machine-wide problem.

Avoid broad registry-permission resets

The original guide changed permissions on the entire HKLM\SYSTEM\CurrentControlSet\Enum tree and granted broad access. That can weaken device/security permissions and is removed from this revision. If registry ACLs are genuinely damaged, restore from backup/System Restore or repair the installation rather than applying blanket permissions.