WWolfe0001

New Member
I right click on the start icon and select Device Manager, and nothing happens. Some of the other options open, but not Device Manager.
 


It seems like you're facing an issue where Device Manager won't open when you try to access it through the Start menu. This can be quite frustrating, but there are several troubleshooting steps you can take to resolve the problem:

Possible Solutions:​

  1. Run Device Manager from Run Dialog:
    • Press Windows + R to open the Run dialog.
    • Type devmgmt.msc and hit Enter. This should directly open Device Manager.
  2. Use Command Prompt:
    • Open Command Prompt as an administrator:
      • Press Windows + X and select Windows Terminal (Admin) or Command Prompt (Admin).
    • In the Command Prompt window, type devmgmt.msc and press Enter.
  3. Check for Corrupted System Files:
    • Sometimes system files can become corrupted, which might prevent Device Manager from opening. You can run a System File Checker scan:
      • Open Command Prompt as an administrator.
      • Type sfc /scannow and hit Enter. Wait for the scanning process to complete and repair any issues it finds.
  4. Use DISM Tool:
    • If the SFC scan doesn't find issues, you can try using the Deployment Image Servicing and Management (DISM) tool:
      • In Command Prompt (admin), type:
        Code:
         DISM /Online /Cleanup-Image /RestoreHealth
      • Press Enter and wait for the process to complete.
  5. Create a New User Profile:
    • If the issue persists, it might be related to your user profile. You can create a new user account to check if Device Manager opens there:
      • Go to Settings > Accounts > Family & other users > Add someone else to this PC.
      • Follow the prompts to create a new account.
  6. Check for Windows Updates:
    • It's important to ensure Windows is updated, as updates might resolve bugs affecting system functionality:
      • Go to Settings > Windows Update and check for updates.
  7. Repair Windows Installation:
    • If none of the above methods work, consider repairing your Windows installation. You can do this using the Windows installation media to perform a repair install without losing your files.

Final Thoughts:​

If you try these steps and still cannot open Device Manager, please provide any error messages you encounter or further details about what happens when you attempt to open it. This will help to further narrow down the issue.
 


3 and 4 from the bot do basically the same thing. I would run one of those commands. If corrupt files are found and repaired, reboot and run the command again until it comes back clean
 


3 and 4 from the bot do basically the same thing. I would run one of those commands. If corrupt files are found and repaired, reboot and run the command again until it comes back clean
Nope, its not the same thing and both commands should be run. In fact, I think DISM /Online /Cleanup-Image /RestoreHealth && sfc /scannow should be run on the same line!

@ChatGPT Do you concur?
 


Yes, I concur! Running both DISM and SFC commands is an effective way to ensure the integrity of your Windows system files, especially when troubleshooting issues like the Device Manager not opening. Here’s a bit more detail on both commands:
  1. DISM (Deployment Image Service and Management Tool):
    • The command DISM /Online /Cleanup-Image /RestoreHealth is designed to repair the Windows image. It checks and fixes issues that may prevent Windows components from working properly. This command is really useful for resolving corruption in the system files.
  2. SFC (System File Checker):
    • The sfc /scannow command then scans the integrity of Windows system files and replaces any corrupted files it finds. It's typically run after DISM to ensure that all system files are in their correct state.

Running Both Commands​

You can actually run them together to streamline the process. Opening a Command Prompt as Administrator and entering the following command:
Code:
DISM /Online /Cleanup-Image /RestoreHealth && sfc /scannow
This will run both processes sequentially. After running these commands, if any repairs are made, it's good practice to reboot your computer. You may even want to run the commands again until the SFC command confirms that it found no integrity violations.

Conclusion​

Your approach is sound, and using both commands together can help diagnose and fix issues more effectively. If you have any more questions or need further assistance, feel free to ask!
 


Back
Top