MSI Error 1720 - wazuh-agent-4.2.3.msi

[Chris Barrett]

I have about 20/70 agents that at some point since v3.13.1 have failed an upgrade of the agent using "/var/ossec/bin/agent_upgrade -a xxx" and have been left in an offline/patially installed state. Manager is now at 4.2

When manually trying to fix the agents  I am getting the below MSI errors in the verbose log when using the wazuh-agent-4.2.3.msi installer. I am not sure the location of the script to check the specific command which is failing. Any help appreciated!

MSI (s) (70:A0) [15:10:58:578]: Product: Wazuh Agent -- Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.  Custom action CustomAction_InstallerScripts script error -2146828212, Microsoft VBScript runtime error: Path not found Line 67, Column 5,  

MSI (s) (70:B8) [15:10:58:578]: Note: 1: 2318 2:  
Error 1720. There is a problem with this Windows Installer package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.  Custom action CustomAction_InstallerScripts script error -2146828212, Microsoft VBScript runtime error: Path not found Line 67, Column 5, 

[Miguel Angel Fernandez Torralbo]

Hello, sorry for the late response. Do you still have this problem?
It seems like the path is missing. Could you check that the directory C:\Program Files (x86)\ossec-agent exists?

[Chris Barrett]

Hi there, yes I am still encountering the error. Thanks for responding

It does exist. The Program Files\ossec-agent directory was all that was left after the failed upgrade of v3.13.1 - all the binaries had been removed. (This is using the wazuh agent_upgrade of v4.2 wazuh-manager)

I have tried removing the directory, and rerunning the install MSI but the same error is produced each time and the directory is left behind after the MSI rollback.

Is there any way to determine the script line 67 this error refers to? I'm guessing there is some residual file or registry preventing the install

[Miguel Angel Fernandez Torralbo]

Hi Chris! I'm trying to reproduce this error but I'm not able to. Line 67 what it does is that it creates an empty client.key file on the first install. I guess it detects that this file it's not in the system and when it proceeds to create it gives you an error because of the path.
This is the script:
https://github.com/wazuh/wazuh/blob/4.2/src/win32/InstallerScripts.vbs#L67

What is the operating system that you are using?

[Chris Barrett]

This has impacted hosts running Windows Server 2016 and Windows 10.

After re-running - I can see that the MSI re-creates the ossec-agent directory in Program Files (x86), and creates the empty client.keys. These files are left behind after the MSI rollback