I have created a few file associations using the new file association wizard.
It looks like the installer is creating a value for command with nonsense for the value rather than just setting the key default to the command.
See this screenshot
https://imgur.com/a/jAXTS0A
As a result, the file association is giving a "the parameter is incorrect" error.
If I delete the command value and leave the command key with the default value in tact, the file association works as expected.
https://imgur.com/a/ED729KP
Any help would be appreciated.
https://imgur.com/a/KE65n1h
Suggested Articles
Re: File Associations broken
Hello,
That strange value string was placed there by Windows Installer. It is the so-called Darwin descriptor that Windows Installer uses to figure out what program to run when the verb is invoked by the shell. For compatibility with programs that read the registry directly, the default value is set to something approximating the local executable’s path. That default value might be incorrect if the application has moved in the meantime, and it might be missing entirely if the application is marked as install-on-demand and has never been used, but at least it keeps those rogue programs working 99% of the time.
Most likely, here is another issue that is not related to the command key value.
I will reply to your email with the resources we need to further investigate this issue.
Best regards,
Liviu
That strange value string was placed there by Windows Installer. It is the so-called Darwin descriptor that Windows Installer uses to figure out what program to run when the verb is invoked by the shell. For compatibility with programs that read the registry directly, the default value is set to something approximating the local executable’s path. That default value might be incorrect if the application has moved in the meantime, and it might be missing entirely if the application is marked as install-on-demand and has never been used, but at least it keeps those rogue programs working 99% of the time.
Most likely, here is another issue that is not related to the command key value.
I will reply to your email with the resources we need to further investigate this issue.
Best regards,
Liviu