Problems with group policy and auto update feature

I confirm (by marking “x” in the [ ] below: [x]):

• This is not a troubleshooting question. Troubleshooting questions go here: https://docs.mattermost.com/install/troubleshooting.html.
• This doesn’t reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
• I have read contributing guidelines.

---

Summary Disabling the auto update function doesn’t work via group policies

Environment

• Operating System: Windows 10 1809
• Mattermost Desktop App version: 5.1.0
• Mattermost Server version: 6.3.9

Steps to reproduce

• distribute group policies as described in the docs and set “EnableAutoUpdater” to “0”
• start desktop client

Expected behavior

• no “update available” popup and icon in the right corner

Observed behavior

• “update available” popup and icon in the right corner

With gpresult, we confirmed that the group policy is distributed and active. We checked via regedit that the registry key is set as follows:

Path: HKEY_LOCAL_MACHINE\Software\Policies\Mattermost Key: EnableAutoUpdater Value: 0

In the user context HKEY_CURRENT_USER we didn’t find any entry like this, though.

In C:\Users\censored\AppData\Roaming\Mattermost\logs\main.log I found this error multiple times:

[2022-09-09 14:17:28.796] [info]  Found version 5.1.1 (url: 5.1.1/mattermost-desktop-setup-5.1.1-win.exe)
[2022-09-09 14:17:28.828] [info]  [Mattermost] available version 5.1.1
[2022-09-09 14:17:29.014] [info]  Log level set to: info
[2022-09-09 14:17:34.166] [info]  [<censored>___T...] finished loading https://<censored>/
[2022-09-09 14:17:35.817] [error] error: ProcessUncleanExitError: ADD command exited with code 1:
FEHLER: Die Registrierungsbearbeitung wurde vom Administrator deaktiviert.
    at mkErrorMsg (C:\Program Files\Mattermost\Desktop\resources\app.asar\index.js:51742:10)
    at ChildProcess.<anonymous> (C:\Program Files\Mattermost\Desktop\resources\app.asar\index.js:52354:10)
    at ChildProcess.emit (node:events:390:28)
    at maybeClose (node:internal/child_process:1064:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

Also, in C:\Users\censored\AppData\Roaming\Mattermost\config.json the auto update setting is configured as follows:

"autoCheckForUpdates": true,

When I manually set this to “false”, the popups disappear. But unfortunately this isn’t a sustainable solution for my whole company.

Possible fixes n/a

[rtfm98]

@devinbinnie Thanks for the follow-up. v5.2 is currently being packed into a SCCM package, so I can’t answer your question right now. As soon as we deployed v5.2 and there is an actual update available, I’ll come back to it.

[rtfm98]

@devinbinnie Hi again, we deployed v5.2.1 and I can confirm that the “update available” popup is gone (even though v5.2.2 is available) 👍