I'm trying to figure out the same problem. After the "This setup will perform an upgrade..." message, if there isn't a specific event for it, is there something one can add to the OnBegin event to tell it's trying to perform an update?  We need to distinguish this from an attempt to uninstall.   ... View more

Its not seems to be working .Please suggest How to check this ... View more

If you would like, you can send the COM servers that do not get all information extracted as expected to jstechnij@flexerasoftware.com. It is possible that the behavior you are seeing is related to an existing known issue with the current COM extraction implementation (if the COM server registration depends on any existing registry information, this information will be unavailable during COM extraction) or if this is a different issue. As a whole, COM extraction was not changed much from IS 2009 to 2010, so the issue here could be related to the underlying operating system used to perform COM extraction on. ... View more

Cool. I'm not sure what your .NET experience is, but VB.NET and C# both compile to the same intermediate language so strategically they are equivilant. You can easily write DTF CA's using VB.NET if you choose... I don't. 🙂 ... View more

Is it possible to cache the setup.exe like you can cache the msi? That way it never asks the user for the original setup.exe when modifying / repairing an install. ... View more

Those only language that should have this problem is the default language, as the base MSI is populated with the same strings as the default language uses. Every other language should have different text, so it will only have the correct code page used for it. ... View more

MichaelU wrote: Yes, that is correct. You're targeting Windows 7 systems and not using IS2010 already? :eek: (Just kidding! Mostly.) Just PM me a valid license key then I will make use of it, premier preferred of course :cool: ... View more

MichaelU wrote: I'd check the message with the type 19 error action, and any string IDs associated with it. I agree the symptom looks like it's getting an empty string (which then formats to 1: ). Found it by looking at a new project. IDS_PREVENT_DOWNGRADE_EXIT was missing in the string table. Thanks for the type 19 error action hint, will try that in the future. ... View more

MichaelU wrote: Sorry, I meant to get back to you on this, but I lost track. We've reproduced it and are tracking it under IOC-000080419. The core of the problem can be reproduced with setup.exe /l1034 /jm, followed by setup.exe /l1034 even without prerequisites; it is due to passing the language transform incorrectly for an advertised setup. I expect we will have a fix for this in our next release. Let me know if that is likely to be too late for your needs. Thanks for the update, Michael. Sure, it would be very nice to get a fix for IS2009 since we publish our release in a few weeks and it uses a Prereq that needs elevated privileges to run. But we can live with an additional UAC prompt for now. And I am not sure if we will purchase IS2010 or a new Maintenance Plan. ... View more

The attached document was written a few months ago, so the Wix version and location may not be exact. ... View more

We looked into this, and it appears it may be due to INSTALLDIR (and any other relevant directories) not being in SecureCustomProperties. Let me know if adding it fixes the behavior for you too. ... View more

Hi everyone, I have a problem when uninstalling a software under Windows 7. I am using InstallScript MSI Project to make the software's setup.exe. When I try to uninstall a software that I created via Control Panel's Uninstall a Program, it can be uninstalled. However if I install the software for the second time and then uninstall it, an error message pops up saying "The installation source for this product is not available. Verify that the source exists and that you can access it. C:\WINDOWS\Installer\97675.msi" I've checked to make sure that the 97675.msi is located under C:\WINDOWS\Installer,and the software installs and uninstalls perfectly on XP/Vista without any problems. Any ideas or suggestions? Many thanks to those who help me out. ... View more

-LaunchCondition is NOT VersionNT64 -Launching the .msi directly does not prevent later installs and does not put them in repair/maintenance mode -The main MSI becomes only partially installed when launching Setup.exe and the Prerequisite gets installed ( I did not tested it without any Prerequisite yet), MSI Sleuth reports 'Error Reading Product Information' for that Product. ... View more

If you have MSI APIs available to you, perhaps you can check the package code (or possibly other version markers depending on what changed in your updates) of the cached MSI package. You can find the package via lookup from the product code. ... View more

The only built-in option for 1 is the RemoveFile table, which can remove associated files when a component is installed or uninstalled. At uninstall, this can only be an component uninstall, and unfortunately there is no way to condition that. You might be able to fake out conditioning by creating an extra Directory entry and carefully setting it to something unusable, but I don't think I'd recommend that sort of trick, even if it works. So yeah, go custom action. For 2, built-in will only handle the current user, and that only if it's resources installed by the .msi tables. If this configuration is supplied by the application when it runs, etc., there's nothing built-in for the uninstall. In general it is recommended that configuration be left behind so user B doesn't lose settings when user A uninstalls and reinstalls a per-machine installation. ... View more