Problems with "File Association" in Windows 7 64-bit

Anonymous
2009-11-04T02:38:45+00:00

Although I am able to go through the "regular" process to associate a program with an extension it doesn't work.  After going through the browse process and selecting the program it brings me back to the "open with" window.  The program I've selected does not appear in the "open with" window and it appears that it is simply ignoring me.

I've also tried the "Default Programs" route but wind up at the same "open with" window that still ignores me.

Suggestions?


[EDIT]

  1. I've realized that this is probably not the proper forum for this question so feel free to ignore!
  2. I've also realized that this may be an issue with associating extensions with non-64-bit programs and appears to be a non-issue if trying to associate with a 64-bit program... go figure.
Windows for home | Previous Windows versions | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2009-11-22T16:57:44+00:00

After playing around a lil I think I've figured it out.. [for me at least..]

The program that you're pointing to isn't registered correctly.

In regedit: Navigate to Computer\HKEY_CLASSES_ROOT\Applicationsand find your .exe name.

Navigate under its name to shell>open>command. In the Default change its location to the actual location of the executable, hit okay and then try and reassociate the file type as you normally would.

Let me know if that doesn't seem to work.

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments

249 additional answers

Sort by: Newest
  1. Anonymous
    2011-04-05T06:15:10+00:00

    I had a similar problem. I wanted .xls files to open in MS Excel 2003 but could not get it to appear in the Open With window even after selecting browse and selecting the 2003 version of excel.exe. When I returned to the Open With window only excel 2007 would be available.

    I fixed the problem by changing the extension on an excel file to one which did not exist/was not registered e.g. .xlrs.

    I then used the Open With window and navigated to the 2003 excel.exe and selected it with the always open with box ticked.

    Then when I selected another .xls file and Open With, both versions of excel (2003 & 2007) were available and I could select the 2003 version and set it as the default program for .xls. I then changed the file with the .xlrs extension back to .xls and everything now works as I wanted it.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-04-04T21:08:31+00:00

    I am having the same problem, but this solution didn't work for me, at all.

    I am trying to persuade Visual Foxpro to open its own configuration file, extension .fpw  I go through the "Open with" dialogue, select the vfp9.exe and return to the "Open WIth" dialogue as if I'd never made a choice.

    That extension doesn't exist in the association list, and there is no indication in it of how to add an extension. Help is useless and irrelevant on the subject.

    vfp9.exe was not in the applications list at all, despite being installed, so I added it. I also added the shell, open and command keys and pointed to the executable's location. None of this made any difference at all.

    My choice for "Open with" is still being discarded/ignored.  This is extremely annoying behavior.

    How can I force Win7/64 to respect my choice here and open the file with what I tell it to open with?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-03-31T04:41:02+00:00

    Thank you. I was about to pull my hair out, and then I found your fix for the issue and it was taken care of in seconds.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-03-24T04:15:42+00:00

    Thank you Xandragnis,

    This worked for me too! My problem was stupid Nero 10 with the registry pointing to the replaced Nero 9. Win7 - 64 also . . .

    Was this answer helpful?

    0 comments No comments