Checking for Windows Updates
Here’s where I hit a snag — the Device Manager wouldn’t open and kept crashing right away. First, I made sure Windows itself was up to date. Sometimes, these quirks are caused by bugs that get patched in the latest updates, and it’s a common fix. To do that, I went to Settings > Windows Update and clicked Check for updates. Simple as that. If your Device Manager is acting up, it’s worth checking for available updates, including optional or driver updates—these can usually be found under Settings > Windows Update > Advanced options. Sometimes, updates are hidden by default, so it’s good to have a quick look. Installing those patches often sorts out glitches, especially when it comes to device management, and it’s just good practice overall. Trust me, once I had the latest updates installed, some strange issues just vanished. Plus, keeping Windows up to date isn’t just about fixing bugs; it’s also vital for security.
Repairing System Files with DISM and SFC
If updating Windows didn’t do the trick, the next thing was dealing with corrupted system files. Windows has these handy tools — SFC (System File Checker) and DISM (Deployment Image Servicing and Management). They’re designed to repair broken system files, which can sometimes cause Device Manager to crash or hang. Here’s what finally worked for me — first, run sfc /scannow in an Admin Command Prompt. Open it by searching for cmd, right-clicking, and choosing Run as administrator. The scan takes a few minutes and will attempt to automatically fix any corrupt or missing files. If that isn’t enough, I ran DISM /Online /Cleanup-Image /RestoreHealth. This can take some time and might need a couple of runs if your system’s really banged up. Don’t force shutdowns during this process. I found that running DISM multiple times with restarts in between helped to clear out lingering issues. It’s a bit like giving Windows a tune-up—if the core system files are dodgy, that can cause all sorts of strange hardware problems, including with Device Manager.
Boot into a Clean Boot State
What really threw me was conflict caused by third-party software. If your Device Manager crashes or won’t open, it might be a software conflict from background apps or driver issues. The way to troubleshoot this is to start Windows with only the essentials—what’s called a clean boot. To do this, I opened msconfig (type msconfig into Start or Run), went to the Services tab, checked Hide all Microsoft services, then clicked Disable all. Next, I went to the Startup tab and opened Task Manager from there (since Windows 11 changed how startup apps are handled). I disabled all non-essential startup items. Be cautious—don’t disable anything crucial, but generally, this cuts down on software conflicts. Once I restarted with this minimal setup, Device Manager opened without issue. If it works now, some third-party app or driver is causing the trouble. The process is to narrow it down—uninstall or update anything suspected once you identify the culprit.
Create a New User Profile
A sneaky cause can be a corrupted user profile. If your profile settings are messed up, Device Manager might refuse to work. Creating a fresh user account is usually straightforward. Go to Settings > Accounts > Family & other users > Add someone else to this PC. You can set up a Microsoft account or a local account — I went with a local one for simplicity. Log into that new profile and see if Device Manager functions normally there. In my case, that did the trick — I could open it without crashes. If the issue disappears, then your original profile is likely corrupted. Moving your files across and then deleting the faulty profile later is often the best course. It’s a quick way to check if the problem is user-specific rather than system-wide.
Use Third-Party Driver Updater Tools
If all else fails, I found that tools like Driver Booster or Snappy Driver Installer can be a real help. Since Windows’ own Device Manager was unreliable, these apps scan outside of Windows — before the OS even loads — which makes them perfect if Device Manager keeps crashing. They identify outdated or incompatible drivers and make updating them easy. After the scan, you can usually click a button to update all drivers or select specific ones. Always try to download drivers directly from the manufacturer’s site when possible, but these tools help speed up the process and reduce frustration when troubleshooting. It took me a few attempts—reboots and multiple scans—to get everything working smoothly, but at least I could get my devices recognised again. When Windows just won’t cooperate, these tools can be a lifesaver.
Hope this helps — it took me ages to figure out what was wrong. Troubleshooting Device Manager is usually about trying different angles. Make sure your BIOS firmware is current, TPM and Secure Boot are enabled, and your drivers are up to date. And don’t forget to back up your encryption keys before messing with TPM settings. Good luck—I hope this saves someone else a whole weekend of frustration!