If you browse to "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\InstallShield" and delete the "InstallShield 20xx" shortcut, create a shortcut directly to isdev.exe, pin it, then rename the shortcut to the original shortcut's name you will still have the new shortcut pinned despite the presence of the word "install". Looks like Microsoft only checks for that at the time when the shortcut gets pinned. Works perfectly with 2009. ... View more

Am I the only one who has experienced this with a dynamic file link in a pure MSI package? Seems like a flaw in MSI or in the InstallShield interface. I can't fathom that every pure MSI package out there (created from InstallShield, of course) manually names each file in a component. ... View more

I am by no means an expert so ... your mileage may vary... In the Redistributables view, at the top right corner of the window, there should be a blue "Show Details" link. Click on that and you'll see a pop-out pane that shows you the path to the module that's currently selected. If your setup is anything like ours you'll see: Name: Visual C++ 9.0 MFC (x86) WinSXS MSM Path: C:\Program Files\InstallShield\2009\Modules\i386\policy_9_0_Microsoft_VC90_MFC_x86.msm Name: Visual C++ 9.0 MFC.Policy (x86) WinSXS MSM Path: C:\Program Files\InstallShield\2009\Modules\i386\Microsoft_VC90_MFC_x86.msm Name: Visual C++ 9.0 MFC (x86) WinSXS MSM Path: C:\Program Files\Common Files\Merge Modules\Microsoft_VC90_MFC_x86.msm Name: Visual C++ 9.0 MFC (x86) WinSXS MSM Path: C:\Program Files\Common Files\Merge Modules\policy_9_0_Microsoft_VC90_MFC_x86.msm They're listed under the same name but if you select the policy file the other one will automatically become selected. I can't speak for which one will work for you but we've been using the InstallShield\2009\Modules\i386 version and it's been working just fine for us. Show the details, select the policy file, the other one becomes enabled. Try it using one policy at a time and see which one works for you. ... View more

I believe Windows deletes this key after all the file rename operations have completed during the reboot cycle. ... View more

I knew it was going to be something really simple that I was overlooking. I thought there was a flag somewhere but I just couldn't find it. Thank you! ... View more

I finally figured out a way to make this work. What I had to do was add a key file that would be guaranteed to change from one build to the next. I also had to rearrange the the source files directory structure to accommodate both a static and dynamic link in the same component. Once I set the key file the upgrade has been working exactly as it should. ... View more

What type of setup are you using (network image, DVD-5, etc.)? Do you have it being compressed into a single executable image? ... View more

Is it possible that every time it fails it's actually doing an uninstall instead of an install? ... View more

Try using RegDBDeleteValue instead. You're can't delete a value with RegDBDeleteKey. Your key is "MyApp", not "ServerName". ... View more

Have you gone through the Release Wizard to make sure the settings in there are correct for building a single .exe? The Release Wizard is located under the Build menu. ... View more

I guess we could just launch the EXE like we are now and not try to be preemptive. The EXE we launch is not really a full-blown EXE. It's actually a Wise Script installer that's running as a plain executable (i.e. a wrapper executable). The author needed a solution and he only knew Wise Script at the time so that's what we got stuck with. I'll have to investigate the possibility of either doing this in a regular executable or possible a DLL call that gets added to our installation helper DLL. ... View more