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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2015-01-27T12:20:55+00:00

    I've tried all of these methods, and none work for me. I have trouble finding any program in Programs (x86) folders, including Quickpar and Calibre. As for Amazon's Kindle, this is a nightmare.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-02-24T10:44:11+00:00

    ANSWER: CCLEANER

    Run CCLEANER's REGISTRY CLEANER

    after all of that is cleared out it should work fine

    I just had this same issue, then I ran CCLeaner's registry cleaner,

    AFTERWARDS the issue was resolved

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-02-24T17:09:46+00:00

    Thank you for your contribution.

    Unfortunately, I have already tried this, many times (I find ccleaner pro very useful) all with no improvement.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-03-13T02:48:52+00:00

    This solution worked for me too. 

    It would be nice if Microsoft added some code that validated paths to applications referred to in this part of the registry tree, and reset/removed those associations when the paths proved invalid. I am assuming that when I tried to point to SciTE in a new location, even though it was a newer version, since it was found in the registry already but with an invalid path, an error was thrown and whoever wrote the code just exited the routine on the error thrown instead of updating the application path to the newly selected application path. Tisc Tisc!

    Judging from the number of replies, this has been a fairly omnipresent issue. A simple code fix like what I recommended above would have certainly adverted this problem for me and many of my associates.

    Was this answer helpful?

    0 comments