

In addition, the behaviors of a) Windows Explorer, b) ASSOC at the command line, c) ShellExecute, and d) the return value of AssocQueryString can get out of sync. machine level associations, losing the fine-grained control that we used to have in the control panel, and possible lack of write permission to the registry, users canĮnd up in a catch-22. Between UAC, user-specific associations vs. This is a mess in Windows 7, I have decided. Unfortunately with the above situation, my application displays a message confirming that the extension isĪlready successfully associated when its not! So is there a way around this? The problem however is I have a button in my application that uses the above mentioned code to check for extension association with my application. I know it might seem obvious that if a user through explorer sets the associated application to an extension, that it would be expected to do it the same way again to re-associate the extension to a different application. My question is: Is there a way to achieve this programmatically? What registry values can be changed to regain control of an extension, after is associated with another program?


