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
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

249 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2010-03-07T18:41:51+00:00

    I have been recently struggling with precisely the same problem - running a new installation of Office 7 with Windows 7. All .rtf files associated fine with the new program but .docs did not. Thankfully I found Xandragnis post, too, which fixed the problem

    • my registry still pointing to the old installation of Office when I was running XP! I changed that as advised above and thankfully all is well again. So thank you Xandragnis and thank you Cody. Good to see.

    Now can rest peacefully again. :)

    Nick

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-03-03T03:12:37+00:00

    Hi everyone,

    Just wanted to clear up some of the confusion.

    Syed's response did suggest creating a new profile, which the OP had not mentioned in their first post. Since the OP didn't return for over 7 days,  it is assumed these steps resolved the issue and is then marked as answer.

    Since Xandragnis' post has resolved this issue for multiple users, I have now marked his post as the answer.

    Thanks for your continued use of Microsoft Answers!

    Cody C

    Microsoft Answers Support Engineer

    Visit our Microsoft Answers Feedback Forum and let us know what you think.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-03-03T01:36:36+00:00

    I always love it on the MSDN forums when answers that don't work get marked as answers for the sake of having an answer marked! Its as if someone gets a check in the mail or something for every answer.

    The proposed answer _does not work_ for any software that has not used an installer.

    You do remember the days when there existed software that was 100% contained in its own directory and required no install, but simply a double click on the executable to run? Some of us still use those programs and would like to associate files to them.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-03-02T20:25:09+00:00

    The form letter from Microsoft and marked as the answer (by the same guy?!) is completely wrong. The answer by

    Xandragnis is absolutely correct.

    I had the same problem after manually moving an exe which didn't need an installer from one location to another - suddenly the file types stopped working and I couldn't reassociate using the standard methods. I had to go into regedit and change the path in the Applications key, just like Xandragnis said.

    It seems like such an easy thing for Microsoft to fix - just detect that the key for that application is pointing at a file that isn't there anymore and let the user pick the new location using the browse button in the default programs control panel page? Computers are so hard to use.

    I'm using the 32 bit version of Windows 7 Home Premium.

    Was this answer helpful?

    0 comments