Any ideas? I believe that the installation of VS uses the administrative install method so that an application can install without the 4. An administrative installation creates an uncompressed source image for a product, typically to be used for installing or running an application from a network location. An administrative installation is not a typical installation, in that it does not create any shortcuts, register COM servers, create an Add or Remove Programs entry, and so on.
Often an administrative installation enables a user to install the product in such a way that its features run from the uncompressed installation source. As it turns out, it ended up being an issue with a third party licensing utility that is installed during our installation process. The issue indeed was only present on machines with Windows Installer 4. Not really sure how WI 4. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How to rollback Windows Installer 4. Ask Question. Asked 10 years, 4 months ago. Active 10 years, 1 month ago. Viewed 3k times. Improve this question. Diogo Bender the Greatest Bender the Greatest 1 1 gold badge 10 10 silver badges 15 15 bronze badges. I need to absolutely confirm that it is a compatibility issue with 4.
And we have a customer that needs a quick workaround. The installer uses WiX 3. If the update is not showing there then you have to restore the system. I'd be surprised if you didn't already have Windows Installer 4.
Isn't it pushed as a critical update through Windows Update? Custom action execution on update uninstallThis feature lets an update add or change a custom action so that the custom action is called when an update is uninstalled. The issues present in earlier versions of Windows Installer that are addressed in Windows Installer 4. This lack hindered any custom actions that needed this user right. Some case-sensitive service-name comparisons in the InstallValidate action resulted in an unnecessary "files in use" message in Windows Vista.
When you uninstalled an update that added a new component, the component was also uninstalled. This occurred even if the component was shared by other products.
The following new and improved features have been implemented in Windows Installer 4. Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help.
Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback?
0コメント