Jump to content

Recommended Posts

Posted (edited)

Try to update von 2225 to 2228. Not possible :(

 

And what means:

 

Support for Windows 8.1 Update 1

Did 2225 not working within 8.1U1?

Edited by Megachip
Posted

Thx, but if I remote uninstall eset, am I able to reinstall (do not having root credentials)

Posted

add to installation package commands: IGNORE_CONFLICTS=1 and than try again :)

Posted

add to installation package commands: IGNORE_CONFLICTS=1 and than try again :)

 

Hi Bart,

 

That switch isn't really a public switch, and can cause further problems if not used properly.

I'm not sure if it should be used here and would wait for staff to determine if it's ok or not in this scenario. :)

  • 1 year later...
Posted

So, since 2008 it is mostly impossible to do minor upgrades of ERA/ESS without loosing the configuration (remove ESET (or the registry key) and reinstall).

 

Any official solution for that?

 

Trying to upgrade 2242 to 2254 and running into the same issue. Why minor upgrades (of the same language, upgrading from german to english works fine) are blocked? 

 

Or is 2242 fine on Windows 10?

 

THX a lot,

Best,

Meg

  • ESET Moderators
Posted

I am not aware it would not be possible to perform incremental upgrades, millions of users perform them without any issues, so in your case it may be something specific.

I'd advise to submit a request via the in-product support form and our support team will investigate the cause of the installation/upgrade issue on your computer.

  • 4 months later...
Posted (edited)

Sometimes, upgrades will not work and the ESET Remote Installer stops with this error message.

 

What params will ERI check to determine if a package is already installed?

 

Only the Packagename from Registry Key or some other params like version?

 

If there is a minor version upgrade, I only replace the msi within the ERAS (not changing the package name).

 

 

BTW, the safe mode uninstall tool seems not removing these entries :/

 

P.S.

Topic allready exist, but search board search did not found it:

https://forum.eset.com/topic/2161-a-package-with-the-same-name-has-already-been-installed-on-this-computer/

 

Could be merged, if possible.

Edited by Megachip
Posted

 

 

Prevention of repeat installations

Immediately after the remote installation process is complete, the remote client is marked with a flag prohibiting repeated installations of the same installation package. If the Type and Name of the package defined in the einstaller.exe agent match the data in the registry, the installation will not be performed. The flag is written to the following registry key: 

HKEY_LOCAL_MACHINE\Software\ESET\ESET Remote Installer

So should I create for every minor update a new upgrade package? The last 6 Years I've simply replaced the msi files and only created new packages on major version upgrades.

 

But problem only occurs sporadic and not on every client/upgrade ... :/

  • 3 months later...
Posted

Suggestions? Same for 2242.2 -> 2260.1.

 

Except removing registry key before every update or creating new package in era every new update.

  • Administrators
Posted

Suggestions? Same for 2242.2 -> 2260.1.

Except removing registry key before every update or creating new package in era every new update.

 

Note that Endpoint 5.0.2260 cannot be installed using an Upgrade client task due to a new signature in the msi installer. It should be possible to deploy it via a push install, however. Could you post a screen shot of the message you're getting when attempting to push v5.0.2260 on clients?

Posted

Note that Endpoint 5.0.2260 cannot be installed using an Upgrade client task due to a new signature in the msi installer. It should be possible to deploy it via a push install, however. Could you post a screen shot of the message you're getting when attempting to push v5.0.2260 on clients?

 

PUSH installation is not possible. The upgrade procedure is providing the user the "remote installer" (300K) which is started by user manually. 

 

The installation mostly failed with this error line: "Status 2902, ID 103: A package with the same name has already been installed on this computer."

 

This isn't a problem of ??? -> 5.0.2260. 

I think the problem is, that the eri only checks package name, not package version :(

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...