Reported version of Windows Mesh Agent client incorrect

[justsomemate]

Describe the bug
After updating server to 1.1.41, the Mesh Agent clients update, but the version reported by Windows still shows the previous build version.
If the agent is manually or clean installed, the version properly shows the new build version.

To Reproduce
Steps to reproduce the behavior:

1. Have server on pre-1.1.41 and Windows clients added.
2. Update server to 1.1.41
3. Wait for client agents to update
4. Check a client version in Programs and Features or the registry. Version still shows 2022-12-02

Expected behavior
Version should show 2024-11-06

Screenshots
MeshCentral Details:

Windows (upgraded agent):

Windows (newly installed agent):

Server Software (please complete the following information):

• OS: Host is Alpine
• Virtualization: Docker
• Network: LAN/WAN, no reverse proxy, no ssl offload
• Version: 1.1.41 (from 1.1.40)
• Node: [e.g. 18.4.0]

Client Device (please complete the following information):
N/A

Remote Device (please complete the following information):

• Device: VM
• OS: Windows 11 24H2, Windows Server 2019
• Network: Local to MeshCentral
• Current Core Version (if known): Nov 25 2024, 448823723

Additional context
We have reports from a separate software management system that shows software versions. Having the correct version reported is useful for verifying all clients have updated or aren't having issues.

Your config.json file

{
  "$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
  "settings": {
    "plugins":{"enabled": false},
    "mongoDb": "mongodb://**redacted**",
    "cert": "**redacted**",
    "_WANonly": true,
    "_LANonly": true,
    "sessionKey": "**redacted**",
    "port": 443,
    "_aliasPort": 443,
    "redirPort": 80,
    "_redirAliasPort": 80,
    "AgentPong": 300,
    "TLSOffload": false,
    "SelfUpdate": false,
    "AllowFraming": false,
    "WebRTC": false
  },
  "domains": {
    "": {
      "_title": "MyServer",
      "_title2": "Servername",
      "minify": false,
      "_NewAccounts": false,
      "localSessionRecording": false,
      "_userNameIsEmail": true,
      "_certUrl": "my.reverse.proxy",
      "userAllowedIP": "10.0.0.0/8,192.168.254.0/24,192.168.1.0/24",
      "showModernUIToggle": true,
      "authStrategies": {
        "oidc": {
          "issuer": {
            "issuer": "https://**redacted**/application/o/meshcentral/",
            "authorization_endpoint": "https://**redacted**/application/o/authorize/",
            "token_endpoint": "https://**redacted**/application/o/token/",
            "endsession_endpoint": "https://**redacted**/application/o/meshcentral/end-session/",
            "jwks_uri": "https://**redacted**/application/o/meshcentral/jwks/"
          },
          "client": {
            "client_id": "**redacted**",
            "client_secret": "**redacted**",
            "redirect_uri": "https://**redacted**/auth-oidc-callback"
          },
          "custom": {
            "scope": ["openid", "profile", "email", "groups"]
          },
          "groups": {
            "recursive": true,
            "required": ["MeshCentral Computers Admin", "MeshCentral Computers Agent", "MeshCentral Servers Admin", "MeshCentral Servers Agent"],
            "siteadmin": ["MeshCentral Admin"],
            "revokeAdmin": false,
            "sync": {
              "filter": ["MeshCentral Computers Admin", "MeshCentral Computers Agent", "MeshCentral Servers Admin", "MeshCentral Servers Agent", "MeshCentral Admin"]
            }
          },
          "newAccounts": true
        }
      }
    }
  },
  "_letsencrypt": {
    "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before>",
    "_email": "[email protected]",
    "_names": "myserver.mydomain.com",
    "production": false
  }
}

[si458]

this is going to be hard to fix because it requires YET ANOTHER agent update!
the code that handles all the registry entries for the install is embedded in the agent side
but thank you for noticing/reporting it!

[tobias9931]

I agree that it would be very important that the version number in the registry is also updated after a selfUpdate. Otherwise it is not possible to analyse whether all clients have been updated successfully. We also have an external software management system which reads and analyses exactly these values.

In my case, I will deactivate the selfUpdate and will have the old agent uninstalled via our external software management system and then will have the new agent installed.
Then it should be okay.

[si458]

im going to look into that, im just looking into the fact the agents DONT work with windows 7 or server 2008r2 at the moment

[tobias9931]

What else occurs to me. What happens if you assign a separate file version for the agent in config.json? Does it then update itself?

[si458]

ok all fixed d49afdd,
everytime it now runs, it will make sure the version and the size is correct for the app in the control panel/apps 👍