Installing Wazuh Agent 4.10.1 sometimes fails

[MaP]

Hi everyone,

I noticed several things while updating the Windows Wazuh agent that I can't really explain:

1)

Sometimes the Wazuh agent 4.10.1 doesn't install correctly (regardless of whether it's installed via Powershell for unattended installation or via the GUI). The "Manage Agent" program then also won't start. At first, I thought you might have to upgrade from agent version 4.9 for the installation to work properly, but I also encountered errors there.

The only thing that helps to get the installation working is:
-Backup Agent Files
-uninstall agent
-install agent
-restore backup
-start service

2)

We have several agents. So far, I've found two that we updated from version 4.7.4 to version 4.10.1. (vie powershell-command and unattended installation).We noticed the following behavior regarding the log file.
A log is created that doesn't generate a new line for each entry.

So it looks like this:

2025/03/13 00:00:10 wazuh-agent: INFO: Starting new log after rotation. 2025/03/13 00:28:53 wazuh-modulesd:syscollector: INFO: Starting evaluation.2025/03/13 00:28:55 wazuh-modulesd:syscollector: INFO: Evaluation finished. 2025/03/13 01:28:56 wazuh-modulesd:syscollector: INFO: Starting evaluation. 2025/03/13 01:28:59 wazuh-modulesd:syscollector: INFO: Evaluation finished.

Strangely, the problem only occurs when the standard Windows editor opens the log file. Everything works fine with Wordpad.
So I think the problem might be related to the editor settings, but I don't know where.
Does anyone know this problem/phenomenon?

I now have all agents on version 4.10.1, so I don't really need help for this post, but I would like to know if other people have had or have had this experience when installing/updating to version 4.10.1 or if the problem is known.

Thank you for reading and best regards

MaP

[Stuti Gupta]

Hi Peter

Can you please share the following details, to investigate the issue further:

Can you please share the Windows OS version you are using?

Is this issue happening only during an upgrade, or does it also occur on a fresh installation?

If it's happening during an upgrade, which specific version are you upgrading from?

What method are you using for the upgrade?

Also, please provide the Wazuh Manager version you are currently using.

This will help us understand the issue more effectively. 

[MaP]

Hi Stuti,

- the Installation error occurs on Windows Server 2022 and Windows Server 2016 

- The Issue happens when upgrading to 4.10.1 , we made some two fresh installations and there doesn't occur the issue. 

- We updatet from 4.7.4 to 4.10.1 and it fails ,but we also updated clients where 4.9.0 was running to 4.10.1 and the issue also happens.

- As i wrote in my first post the Installation-error we used the manuel upgrade process via gui-installation and also on some clients the manuell installation process over powershell with .\wazuh-agent-4.10.1-1.msi /q as shown in https://documentation.wazuh.com/4.10/upgrade-guide/wazuh-agent/windows.html.

- Manager-Version is Wazuh v4.10.1 in Cluster-Config (and works fine and stable).

I hope I have not left any question unanswered.

Regards

MaP

[Stuti Gupta]

We attempted to replicate the issue but did not encounter any errors while upgrading the Wazuh agent using the GUI or performing a manual upgrade. Please let us know if you experience the same issue again in the future, and we will investigate it accordingly.

Let me know if you need any further assistance!

[MaP]

Hello Stuti,
Thanks for investigating this issue!

As I said, the problem didn't occur on every computer.

Since I know how to get everything working normally again, I don't need any further help at this point.

I'll keep you updated if I have any further problems.

Regards

MaP