Version 1.2.0 New Agent - Quick Question ?

[timcanty]

Hi All,

I thought version 1.2.0 had an updated agent, have I miss understood? or was it just the installer that has changed?

Just we have "noAgentUpdate": 1, in the config, but previously when new version we would go click on the devices in the group, and click Force Agent Update

However after 30 seconds or so of the machine updating it shows the agent version is still compile time 18:56:58, Mar 6 2025 ?

Kind Regards

[si458]

ok so first things first, DO YOU CODE SIGN OR BUILD THE AGENT MANUALLY!?
if you arent sure, do you have a folder in meshcentral-data called agents
if you do then we just discovered a bug, DOH! #7866
can you quickly let me know this, then i know how to proceed

[timcanty]

no we won't code sign them ourselves, we just go with the bog standard out the box agents. we don't have an agents folder in the meshcentral-data folder, there is a signedagents folder in meshcentral-data that seems to have the date time of the last time i restarted the service.

[si458]

ok so if you check the meshcentral-data folder are you 110% sure the is no agents folder?
sorry to ask again ive just dealt with a lot of blind people 🤓
if thats the case, then simply backup the signedagents folder (rename it is fine)
then delete the signedagents folder and restart meshcentral
then it should resign and recreate them, then try downloading a new agent from the web ui and see if it shows the date 2026 in the properties

[timcanty]

Just to confirm that i'm not been blind, :)

upon renaming the folder, on start the status shows

new signed agents

dowloaded agent product details

and if i do a force agent update it now correctly shows Feb 2026

Not sure why it didnt work before, but it is now...

[si458]

Ur the 2nd person to report it so i will look into it when I get chance, I think its not copying copying over the new agents and signing them, instead it's just resigning the old agents for some dumb reason!?

[timcanty]

so possibly another issue, so gave up updating them one by one, and turned off the no update config option, and we have a few agents knock offline after updating, in mesh it shows no agent number/date against the device and when we go on the device and try restart the service, it says it can't start, if we run the -fullinstall on them, they come straight back online,

I've resolved the bulk of them but suspect some will come up in the next few days, is there any debugging you want us to try before running the installer on any broken agents. I have a feeling this happened in the past and that's why we turned the updates off and did it manually, so its not an new issue, just a recurrence.

I'm happy to ignore it, but if there is anything particular you want to look at on the devices we can do.

[si458]

Im not 100% sure I'm afraid as every instance of meshcentral is different?
If a simple -fullinstall fixes the issue then I wouldn't be too worried
But yes I would say in future set the noagentupdate and update one by one!
Also to be honest I have been thinking about setting the agent updates to false by default then maybe a message in the server console saying NEW AGENT PLZ UPDATE YOUR AGENTS!
Because in reality we only update the meshagent itself once in a blue moon!
It's only recently we updated them to fix little bugs

[timcanty]

Okay will just fix any that come up, but just for reference, incase this becomes a bigger issue.

The agent log on the machines have this:
[2026-06-03 04:01:45 PM] [168572E0999089DE] ..\microstack\ILibParsers.c:10994 (0,0) SelfUpdate -> Current Version: 28d67274264e140e0c7a4254ad0e32865d5c4a13
[2026-06-03 04:01:45 PM] [168572E0999089DE] ..\microstack\ILibParsers.c:10994 (0,0) SelfUpdate -> Updating and restarting service...

and the event log shows this in the application error when it trys to start:
The program or feature "??\C:\Program Files\Mesh Agent\MeshAgent.exe" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.

and in the system event log it has:
-
-

7031
0
2
0
0
0x8080000000000000

109747


System
SANATISED.


-
Mesh Agent
1
5000
1
Restart the service
4D0065007300680020004100670065006E0074000000

If there is any other logs be helpful to dig out, let me know.

[si458]

Sounds stupid, have u made sure u have the 64bit version installed and not the 32bit. Sounds stupid

[timcanty]

that crossed my mind when i saw the event log, (we only deploy the 64bit version,
but for info that was through the auto update it broke, so unless the auto update could be failing to check the correct install?

[si458]

The other thing to check is antivirus as maybe it deleted the update?

Because we download the update next to the original one with a different name then stop the service, remove old one, rename new one, start the service

So it could be the AV deleted the update and then broke the service by deleting the old agent and the was no new agent!?

It's really hard to say as I'm not c++ dev so i try and look after the meshagent as much as I can but it's very hard.

Also try excluding the folder in the av rather than the single file?

[timcanty]

could we reopen : #6868, its a pain not been able to filter by the agent number/date when these issues are happening

[si458]

Reopened :)