devmgmt.msc: This file does not have a program associated
Written by Christian on March 2, 2008 – 1:47 pmWhen trying to open the Device Manager (Control Panel - System and Maintenance - System), the following error may occur:
C:\Windows\System32\devmgmt.msc
This file does not have a program associated with it for performing this action. Create an association in the Set Associations control panel.
When you get this error, there’s probably something wrong with your file association *.msc. In most cases, the association seems to be correct, but it isn’t. The best practice for this issue is re-importing the correct register settings. Follow the instructions below to import the correct settings:
- Click Start, click Run, type Regedit and click OK
- On the left side, navigate to HKEY_CLASSES_ROOT
- Make a backup of your HKEY_CLASSES_ROOT. To do this, right-click HKEY_CLASSES_ROOT, choose Export, and save it as “old-classes_root.reg“
- Delete these registry keys. To do this, right-click the keys and select Delete
- HKEY_CLASSES_ROOT\.MSC
- HKEY_CLASSES_ROOT\MSCFile
- The incorrect settings are now deleted.
Download the MSC fix for Vista. This registry file contains the correct file type association settings for Windows Vista. - Navigate to the file you have just downloaded. Double-click. A window will pop up whether you are sure to add the settings. Click Yes.
- Your file type association for MSC-files is now restored to its default. Opening your Device Manager should be working again.
People who read this article, also read:
- Howto: Repair Power schemes
- Set default font in Outlook 2007 with registry
- Disable Zip Folders in Vista
Posted in Windows Vista |
June 13th, 2008 at 9:14 am
Sounds like this would work, if only the link to the reg fix actually worked too.
August 15th, 2008 at 1:12 pm
I also had this problem but as Andrew wrote, the link does not work.
Apparently at some point the shell\RunAs\Command default value gets changed from REG_EXPAND_SZ to REG_SZ and this is what causes the mallfunction the %SystemRoot% does not get translated to C:\Windows (or whatever your systemroot is)
So here’s what i did:
Under HKEY_CLASSES_ROOT\MSCFile, select the open\command “folder” and export.
Edit the .reg file and change the key from open to RunAs:
[HKEY_CLASSES_ROOT\mscfile\shell\open\command] ->
[HKEY_CLASSES_ROOT\mscfile\shell\RunAs\command]
Import the edited .reg file.
October 22nd, 2008 at 10:47 pm
I know I most likely won’t get an answer, but I did not quite understand what you asked to change. When i open it up to edit, both keys are already present. ::sigh:: damn vista, i tried to love you… i tried.
October 27th, 2008 at 8:23 pm
Hi Paul,
The link to download the MSC fix seemed to be dead. I fixed it, so you can now download the MSC fix.
As instructed in my post, you should first delete the existing MSC registry keys (make a backup first!). After deletion, you can import the settings from the file I referenced in my post.
Please let me know the result!
November 10th, 2008 at 6:32 am
Hi,
I have been having this same problem. I followed the instructions and rebooted, but I’m still getting the same error. Are there any other things I can try?
Thanks.