Software Deployment

Do either of the apps actually use the entry? If not - and my list of apps which do is painfully small - it's not a problem.

Could you give us an example?

sorry, ofcourse here is example:

- Application X have HKLM\....CurrentVersion\App Paths\myexe123.exe with default value=c:\program files\Application X\myexe123.exe
- but Application Y would like to have HKLM\....CurrentVersion\App Paths\myexe123.exe with default value=C:\program files\Application Y\myexe123.exe

myexe123.exe is convertor which is called by Application X and Application Y, both Application have their own myexe123.exe with different versions.

The conflict may not be a conflict depending on how the converter is called by the x/y application.

If the working directory is outside of the application's exe location it's just going to launch the converter that is specified in the App Paths registry.
Shimming may however fix the problem (hardcoding the return value of where the version exists).

Why not simply rename X's EXE name and deploy accordingly? Most apps don't care what the EXE is called.

Sorry I do not understand. I am affraid renaming of X's EXE(myexe123.exe) could cause no effect. Myexe123.exe is called from main X's application exe. So the goal should be change the main X's application exe to do not call myexe123.exe but e.g. myexe123X.exe.

I think AngelD have good idea by shimming it. I have to check if this is possible e.g. via Microsoft application compatibility tools and I have to negotiate support for shimmned application by vendor othervise create ticket and ask for vendor patch.

FYI: searching of myexe123.exe is in this order:
1. in the same folder as the double clicked document is located
2. HKLM\...\App paths
3.Users %temp% directory
4.C:\winnt\system32
5.C:\winnt\system
6.C:\winnt
7.C:\program files\Application Y\Programs -> success