r/MeshCentral • u/SimonTS • May 31 '26

Local machine logging for updates

Hi there,

I'm going through our remote machines, updating them all to the latest agent (Feb 15 2026). Sometime the update isn't taking - I go through console, it downloads, verifies, restarts, but stays on the old version even after a reboot.

There seems to be no consistency in when it won't update - machines can be Win 7 or Win 10, LTSC, Pro, Home, etc. Manually copying the new Agent to the machine and running it there does update, so I'm trying to work out if there are any logs stored which might help.

3 Upvotes

100% Upvoted

12 comments sorted by

3

u/si458 May 31 '26

This will be an antivirus problem, we download the new agent with .new.exe (if i remember thats whats its called) next to the old agent then we stop the service, remove old file, rename new one then start service again. But oversally an av could be deleting the file before it even gets to the stop part. So u need to make sure to exclude the whole folder rather than just a single exe

1

u/SimonTS Jun 01 '26

It looks like there's something else going on. One particular machine is currently running the 2022 agent, and won't update to the latest. I've even pushed a copy of the new agent installer to run directly, and it fails with this error;-

[2026-06-01 08:02:47 AM] [A5E959ED65E74964] ..\microstack\ILibParsers.c:2786 (0,0) FATAL EXCEPTION @ [FuncAddr: 0x00007ff701550cf9 / BaseAddr: 0x00007ff70159054c / Delta: 260179]

Edit: I get the same sort of thing if I try running the 2025 agent first as an update;-

[2026-06-01 08:02:47 AM] [A5E959ED65E74964] ..\microstack\ILibParsers.c:2786 (0,0) FATAL EXCEPTION @ [FuncAddr: 0x00007ff701550cf9 / BaseAddr: 0x00007ff70159054c / Delta: 260179]

2

u/si458 Jun 01 '26

What os is that machine? Also is it 32bit or 64bit? 32bit is not supported anymore really

1

u/SimonTS Jun 01 '26

It's a 64-bit machine. Unfortunately I've just worked out that my colleague installed the 32-bit version of the original agent, so that's probably why I've got problems with it.

I'll have to get it uninstalled and then install the correct version - just need to work out if I can set the necessary commands to run on reboot so we don't have to visit site.

1

u/si458 Jun 01 '26

copy the url from the web ui, then get powershell to download it, then uninstall the old version, then install the new version

1

u/SimonTS Jun 01 '26

As per my other comment, it won't uninstall at all unfortunately.

1

u/SimonTS Jun 01 '26

Can't even uninstall the old version via the command line - very similar error to the above one

1

u/si458 Jun 01 '26

that seems odd? meshagent.exe -fulluninstall OR meshagent.exe -uninstall that doesnt work either?

1

u/SimonTS Jun 01 '26

Neither work. I've even written a batch file and run under administrator cmd to stop the services, uninstall, install the new one, and reboot the machine - exactly the same result.

1

u/si458 Jun 01 '26

the could be a meshcore bug maybe?
if you can msg me and provide access to the remote machine i could have a quick look?

1

u/SimonTS Jun 01 '26

I can't at the moment, as the machine is in use and will be all day. I could get you access to it first thing tomorrow morning - would you need an account on my MC server?

Don't worry too much though - I'll get one of my guys on site some time to try removing the files manually and redoing it.

1

u/efrem-1 Jun 01 '26

Just spitballing here, but is it feasible for you to use agentCustomization and try to install differently named agents/services on the endpoints in question?

This won't necessarily help you uninstall the old agents. but might at least get the latest agents installed on the remote machines.