Another version of this product is already installed как исправить

I have 32-bit and 64-bit versions of my installer which have (nearly) the exact same code & custom action sequence (there are only minor differences which are not relevant to this issue)

I want my installer to detect whether it has already been previously installed and in this case run my own code instead of showing the default Windows Installer error:

Another version of this product is already installed. Installation of
this version cannot continue. To configure or remove the existing
version of this product, use Add/Remove Programs on the Control Panel.

My 32-bit installer works perfectly fine in that it runs my custom code if I run the installer when the product is already installed, but the same code & custom action in my 64-bit installer does NOT work correctly and always shows the unwanted error msg.

CheckPreviousVersion is the first function called as a Custom Action during the UI sequence, I’ve tried putting it in different spots like after InstallValidate but nothing works.

I’ve examined the verbose log file but I can’t find anything that might explain this behavior, here is a part of the log:

=== Verbose logging started: 05/03/2013  16:27:20  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:Windowssystem32msiexec.exe
===

MSI (c) (0C:94) [16:27:20:331]: Machine policy value 'Debug' is 0 MSI (c) (0C:94) [16:27:20:331]: ******* RunEngine:
           ******* Product: foo.msi
           ******* Action: 
           ******* CommandLine: ********** MSI (c) (0C:94) [16:27:21:546]: Machine policy value 'DisableUserInstalls' is 0 MSI (c) (0C:94) [16:27:21:557]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:Builds.msi' against software restriction policy MSI (c) (0C:94) [16:27:21:557]: Note: 1: 2262 2: DigitalSignature 3:
-2147287038  MSI (c) (0C:94) [16:27:21:557]: SOFTWARE RESTRICTION POLICY: C:Builds.msi is not digitally signed MSI (c) (0C:94) [16:27:21:558]: SOFTWARE RESTRICTION POLICY: C:Builds.msi is permitted to run at the 'unrestricted' authorization level. MSI (c) (0C:94) [16:27:21:584]: Cloaking enabled. MSI (c) (0C:94) [16:27:21:584]: Attempting to enable all disabled privileges before calling Install on Server MSI (c) (0C:94) [16:27:21:586]: End dialog not enabled MSI (c) (0C:94) [16:27:21:586]: Original package ==> C:Builds....msi MSI (c) (0C:94) [16:27:21:586]: Package we're running from ==> C:Builds.....msi MSI (c) (0C:94) [16:27:21:589]: APPCOMPAT: Uninstall Flags override found. MSI (c) (0C:94) [16:27:21:589]: APPCOMPAT: Uninstall VersionNT override found. MSI (c) (0C:94) [16:27:21:589]: APPCOMPAT: Uninstall ServicePackLevel override found. MSI (c) (0C:94) [16:27:21:589]: APPCOMPAT: looking for appcompat database entry with ProductCode '{B8CBA92E-2140-48AB-B4EA-A4C3FF10295B}'. MSI (c) (0C:94) [16:27:21:589]: APPCOMPAT: no matching ProductCode found in database. MSI (c) (0C:94) [16:27:21:599]: MSCOREE not loaded loading copy from system32 MSI (c) (0C:94) [16:27:21:608]: Machine policy value 'DisablePatch' is 0 MSI (c) (0C:94) [16:27:21:608]: Machine policy value 'AllowLockdownPatch' is 0 MSI (c) (0C:94) [16:27:21:608]: Machine policy value 'DisableLUAPatching' is 0 MSI (c) (0C:94) [16:27:21:608]: Machine policy value 'DisableFlyWeightPatching' is 0 MSI (c) (0C:94) [16:27:21:609]: APPCOMPAT: looking for appcompat database entry with ProductCode '{}'. MSI (c) (0C:94) [16:27:21:609]: APPCOMPAT: no matching ProductCode found in database. MSI (c) (0C:94) [16:27:21:609]: Transforms are not secure. MSI (c) (0C:94) [16:27:21:609]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:BuildsAngossProductsWorkstationsingle-execINSTALL64.LOG'. MSI (c) (0C:94) [16:27:21:609]: Command Line: CURRENTDIRECTORY=C:BuildsAngossProductsWorkstationsingle-exec CLIENTUILEVEL=0 CLIENTPROCESSID=7948  MSI (c) (0C:94) [16:27:21:609]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{}'. MSI (c) (0C:94) [16:27:21:609]: Product Code passed to Engine.Initialize:  '' MSI (c) (0C:94) [16:27:21:609]: Product Code from property table before transforms: '{}' MSI (c) (0C:94) [16:27:21:609]: Product Code from property table after transforms:  '{}' MSI (c) (0C:94) [16:27:21:609]: Product registered: entering maintenance mode MSI (c) (0C:94) [16:27:21:609]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine. MSI (c) (0C:94) [16:27:21:609]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'. MSI (c) (0C:94) [16:27:21:609]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'. MSI (c) (0C:94) [16:27:21:609]: Entering CMsiConfigurationManager::SetLastUsedSource. MSI (c) (0C:94) [16:27:21:609]: Specifed source is already in a list. MSI (c) (0C:94) [16:27:21:609]: User policy value 'SearchOrder' is 'nmu' MSI (c) (0C:94) [16:27:21:609]: Machine policy value 'DisableBrowse' is 0 MSI (c) (0C:94) [16:27:21:609]: Machine policy value 'AllowLockdownBrowse' is 0 MSI (c) (0C:94) [16:27:21:609]: Adding new sources is allowed. MSI (c) (0C:94) [16:27:21:609]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'. Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

Many users have been facing the Another version of this product is already installed windows error on their windows system. The error usually occurs when you try to install any program or try to update any existing software. The error stops the installation or updating process. When we talk about the cause of this issue, it generally occurs if the installer file is itself corrupted or an instance or part of the program is already installed in your system. This usually happens when you do not perform a clean uninstall. The error is not that critical, but fixing it can be a big headache. So in this troubleshooting guide on this error. We will give you some methods to fix this issue.

Another Version of This Product Is Already Installed

Causes of Another Version of this Product is Already Installed Error:

If we closely examine the Another Version of this Product is Already Installed windows error, we find that the error appears only if any instance or part of the program is already installed in your system, then this error appears. Furthermore, viruses or malware can also be the possibility of this issue. In some cases, a corrupted installer file was causing the problem.

  • An instance or part of the program is already installed.
  • The installer file is corrupted.
  • Virus or malware attack on the system

Similar Types of Another Version of this Product is Already Installed Error:

  • InstallShield
  • MSI
  • MySQL
  • Vc++
  • Another Version of this Product is Already Installed Wix
  • Cisco anyconnect
  • One or newer versions of the product are already installed.
  • Qxdm identical version of this product is already installed.

Here in this section, we will go through all the possible troubleshooting methods that you can use to eliminate Another Version Of This Product Is Already Installed Windows Error. In the first method, we will talk about clean, uninstalling. In the second method, we will use the windows official install uninstall utility. Finally, in the third method, we will use the registry to fix the error.

1. Clean Uninstalling –

Clean uninstalling means when you are uninstalling any sort of the program, especially if its heavy program kindly uninstall it completely. Suppose you have installed iTunes in windows, now when you install iTunes, other related components also get installed like Bonjour, Apple application support, Apple Mobile Device Support, and Apple software update. Now when you uninstall iTunes, only iTunes gets uninstall, not all of its components. So kindly check for the remaining components of the software. So that you will get rid out of cisco anyconnect Another Version of this Product is Already Installed Corel error.

  • Uninstall every component of the program
  • After successful uninstall do not forget to restart your system

2. Using the Windows Uninstaller Utility –

If you are still getting the cisco anyconnect Another Version of this Product is Already Installed Corel error after uninstalling all the components, or you do not know about what other components of the program are. Then you can go with this method. In this method, we will use the Windows Program install and uninstall utility. Follow the steps now.

  • STEP 1. Download a fresh copy of windows Program install and uninstall utility
  • STEP 2. Once the file is downloaded start the program by double-clicking
  • STEP 3. Here you have to choose Uninstalling because we want clean uninstall
  • STEP 4. Now select the application that is causing the issue, then click next

troubleshooter

  • STEP 5. The program will search for all the related components and registries of the problematic program and fix it

troubleshooter

  • STEP 6. Finally, restart your system and checking the Microsoft visual c++ 2015 redistributable Another Version of this Product is Already Installed trend micro error still persists

3. Using Registry Editor –

In this method, we will be using the registry editor. We will manually delete the leftover keys and registry that is causing the twitch Another Version of this Product is Already Installed AutoDesk issue. Make sure to follow each step carefully to avoid any further system instability.

  • STEP 1. In the Start Menu, type Run then hit Enter
  • STEP 2. In the Run box type regedit and then hit Enter
  • STEP 3. Now in the registry windows navigate to the following location
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall

  • STEP 4. Here you need to find the software that is causing the issue
  • STEP 5. After finding delete the Registry of that problematic program
  • STEP 6. Now navigate to the following location
HKEY_LOCAL_MACHINESOFTWAREWow6432Node

HKEY_LOCAL_MACHINESOFTWAREWow6432Node

  • STEP 7. Here also locate the problematic software and delete its respective registry
  • STEP 8. Finally, after removing the keys, restart your system for getting back of this league of legends Another Version of this Product is Already Installed windows 7 issue.
Conclusion:

By following the above methods and their step by step guide, you will surely get rid of Another version of this product is already installed windows Error. In this article, we have seen various causes, effects, and troubleshooting methods that can be used to fix this issue. However, if you still face any problem, tell us in the comments.

We hope this Another Version of this Product is Already Installed windows article provides you some information, and you have fixed the issue for more articles on troubleshooting. Follow us. Thank You!

Check out the prerequisite before you install Local Configuration Store.

Symptoms

When you run Microsoft Skype for Business Server 2015 Deployment Wizard to install Local Configuration Store on a computer that has Unified Communications Managed API (UCMA) 5.0 SDK installed, the installer cannot find the location of Microsoft Skype for Business Server 2015, Core Components (OCSCore.msi). You receive the following error message:

INSTALLDIR=”C:Program FilesSkype for Business Server 2015″)…failure code 1638
Error returned while installing OcsCore.msi(Feature_LocalMgmtStore), code 1638. Error Message: Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs in Control Panel. For more details please consult log at C:Users[User]AppDataLocalTemp1Add-OcsCore.msi-Feature_LocalMgmtStore-[Date][Time].log

Cause

This issue occurs because UCMA 5.0 SDK installs a newer version of OCSCore.msi than Local Configuration Store. Therefore, you cannot install Local Configuration Store after the UCMA 5.0 SDK installation.

Resolution

To resolve this issue, follow one of the following methods, depending on which scenario you’re in, and install Local Configuration Store on your computer:

  • If you do not have UCMA 5.0 SDK installed on your computer, do the following:

    • Run the installer from the full Skype for Business Server setup and install Local Configuration store.

    • Then install UCMA 5.0 SDK.


    Note These steps will make sure that when UCMASdkSetup.exe is running, the installation of OCSCore.msi is skipped.

  • If you have already installed UCMA 5.0 SDK, do the following:

    • Uninstall OCSCore.msi that was installed by the UCMA 5.0 SDK. OCSCore.msi is listed as Skype for Business Server 2015, Core Components in Control Panel > Programs > Programs and Features.

    • Rerun the installation for Local Configuration Store.


    Note If you are trying to run Skype for Business Server Deployment Wizard that was installed by UCMA 5.0 SDK, point to the full Skype for Business Server setup when you are asked for the path of MSIs.

Prerequisite

To install Local Configuration Store, you must have access to the full Skype for Business server 2015 setup.

More Information

For more information about the deployment scenarios for UCMA applications, see Deploying UCMA 4.0 and UCMA 5.0 Applications in a Skype for Business Server 2015 Environment.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

‘Another version of this product is already installed’

I’m trying to download and play Crusader Kings 3, I’ve installed it and clicked play and windows installer starts running then comes up with an error saying ‘Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove programs on the Control Panel.’ I’ve uninstalled both via control panel and steam app and still this error comes up when reinstalling, please help 🙁

Date Posted: 2 Sep, 2020 @ 12:50am

Posts: 3

  • Remove From My Forums
  • Question

  • I thought I had this sorted out but it appears that the VS2008 generated MSI behavior is different from the IDE compared to just running the MSI.
    I researched my problem in this forum but am more confused now than when I started.  Plus all the posts were VS2005 and earlier.

    I am changing code and versions and such in the application assemblies but not changing any of the values of the Setup project.

    If I have DetectNewInstalledVersion=False and RemovePreviousVersions=True, AND right-click Install from the IDE, then a small progress dialog appears while the “previous” version is removed before the “current” version is installed.   This the exactly behavior I want.

    BUT, if I immediately run setup.exe or the MSI I get the dreaded “Another version of this product is already installed…” dialog.

    If I try the proposed solution, i.e. increment the version and change the Product Code, then the installation completely ignores the fact that a previous version is installed.

    1) how is it that Install from the IDE works differently from the MSI?
    1) is it really possilble to configure MSI to automatically remove whatever version is currently installed?  how exactly is this done? (please explain as I have read the 5 similar questions along with hits for DetectNewInstalledVersion and RemovePreviousVersions – none of these seem to really answer the question)

Answers

  • Visual Studio 2005’s RemovePreviousVersions behaved as a full install of the older product and a fresh install of the new setup. Visual Studio 2008’s RemovePreviousVersions also removes the older *product* (so Add/Remove Programs shows the new one) but at the file level the version rules are followed, so you’re right, files will not be updated unless the file versions have been incremented.  I think the idea behind this is that when people install databases you don’t want an upgrade to remove that database (which is what happened on VS 2005). It’s also a bit more efficient in the case that you have hundreds of files but you only need to update a couple, so you just rebuild those, incrementing the version, and then they will be the only files updated. 

    It’s normal in the setup world that you increment file versions when you want to replace existing files. This has been the way installs have behaved since years before .NET and Visual Studio setups, but if anyone is used to the way that VS 2005 RemovePreviousVersions works it’s a bit of a surprise.  


    Phil Wilson

    • Marked as answer by

      Wednesday, May 20, 2009 1:43 PM

Добавить комментарий