Jump to content

Problem durring installation


Recommended Posts

  • Administrators

Please provide:
- install logs created as per https://support.eset.com/en/how-do-i-generate-an-installation-error-log-for-windows-eset-products
- a Procmon log from the installation: https://support.eset.com/en/using-process-monitor-to-create-log-files
- logs collected with ESET Log Collector.

I would also recommend opening a support ticket with customer care so that the issue is tracked properly.

Link to comment
Share on other sites

  • 2 weeks later...
On 1/12/2020 at 7:09 PM, Marcos said:

Please provide:
- install logs created as per https://support.eset.com/en/how-do-i-generate-an-installation-error-log-for-windows-eset-products
- a Procmon log from the installation: https://support.eset.com/en/using-process-monitor-to-create-log-files
- logs collected with ESET Log Collector.

I would also recommend opening a support ticket with customer care so that the issue is tracked properly.

have any idea?

i've already try some method
1. uninstall another existing Antivirus before install eset File Security

2. using eset fix installer

3. scanning using sys-rescue or online scanner to ensure that server dont infected malware

 

 

Link to comment
Share on other sites

  • Administrators

Please provide install logs as well as a Procmon log from installation as requested. I'd recommend opening a ticket with customer care so that the case is tracked properly.

Link to comment
Share on other sites

Appears MSI.1920 error code is related to the Win installer Eset deploys. Code 1920 for that indicates insufficient privileges when starting a Win service.

Here's a thread related to the same error code given during an ERA installation: https://forum.eset.com/topic/15212-unable-to-isntall-era_installer_x86_en_usexe-error-code-msi1920/ . The last posting in that thread gave a solution that worked for one user.

Another proposed solution in the last reply to this thread: https://forum.eset.com/topic/16123-new-install-error-1920/ . Make sure you reboot after the reg. modification for it to become effective.

Warning: note the existing reg. key value prior to modification. Ensure you set it back to that value when done with installation or another install failure w/modified key value.

Edited by itman
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

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