>>Hi,
>>
>>My application is installed on the VM server. Each user's desktop has a shortcut pointing to the executable (GPMWIN.EXE) on the VM.
>>This one customer has the following problem:
>>Whenever any person from a different desktop starts the application, a call to old version of SETUP.EXE starts. The old version of SETUP.EXE used to install run-time DLLS for VFP 9.
>>An IT guy did some testing and found that whenever the application starts it calls a Key in the Registry that does not exist. Hence, the start up of SETUP happens. User clicks cancel and goes on. But it is annoying.
>>
>>The IT found that the application (GPMWIN.EXE) calls the following key:
>>

>>1:38:24.7972746 PM gpmwin.exe 7552 RegOpenKey HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualFoxPro\9.0\Setup\VFP NAME NOT FOUND 
>>Desired Access: Maximum Allowed
>>

>>
>>I know that GPMWIN.EXE (main program of the app) does not do it.
>>
>>Could one of the VFP?? file do it:
>>For example, VFP9ENU.DLL or VFP9.EXE?? I believe that the VFP 9 application uses these file (located in the application folder).
>>
>>TIA.
>
>UPDATED.
>I deleted what I wrote earlier today. Because I think it is not what causes the problem.
>
>I built my initial SETUP.EXE (the program that installs the ctlstbar.ocx and all MS-VFP DLLs) using VFP-supplied MS InstallShieldExpress.
>
>I think the SETUP.EXE was running some .MSI file. The .MSI was installing whatever components the application required.
>
>Now when a user starts the application, and when the program hits the point where the ctlstbar.ocx has to be initiated, the program tries to run some kind of .MSI program. That is, the program calls the KEY that I wrote above.
>
>So, I need a way to uninstall the "old" SETUP and the .MSI associated with it.
>
>How do I do it?
>
>TIA

Let me say, it's not impossible. The problem is, you need to understand the way the installer puts stuff to the registry. And that is complex. Basically you need all the UUIDs from you installer package. (Component IDs, update ID, package ID, name it) The name of the package. The name of components key files.
Backup the registry
Then you must search for your UUIDs, learn how it interacts and remove.
The big problem is, sometimes the UUID are in different byte order in registry, that is least significant byte might be first.

I do this once in a decade, so I just know there is a way, but learn the details every time again. I have no better description at hand.

You have the old installer package (with the old UUIDs!) or can recreate it? Try to uninstall the whole package ...