RocketChat / Rocket.Chat.Electron

Official OSX, Windows, and Linux Desktop Clients for Rocket.Chat
https://rocket.chat/
MIT License
1.59k stars 700 forks source link

Version 3.0.3 /disableAutoUpdates didnt work anymore #1829

Closed nexidus closed 2 years ago

nexidus commented 3 years ago

My Setup

Description

/disableAutoUpdates switch didnt work anymore. Up to version 2.17.11 it worked wonderfully with the switches in the order: /S /allusers /disableAutoUpdates. Since version 3.0.3 every user gets the message that a new version is available and you should update. Of course, this does not work for the users because they have no rights to install software.

Current Behavior

It doesn't matter whether it is installed manually via CMD with the switches or via SCCM it is rolled out with the same switches. The result is the same, the users are asked to perform an update.

Expected Behavior

mape2k commented 3 years ago

We'll test 3.0.6 - maybe #1861 should fix the issue...

mape2k commented 3 years ago

We can confirm, that the problem is fixed in 3.0.6.

morgens commented 3 years ago

Is there a way do disable autoupdates with MSI installer?

mape2k commented 3 years ago

@morgens: Just create a file update.json in the directory resources in the unstallation dir with

{
  "canUpdate": false,
  "autoUpdate": false
  }
VasiliyMooduckovich commented 3 years ago

it seems to be moved to client config named config.json string "doCheckForUpdatesOnStartup": true, that located in the user profile %appdata%\Rocket.Chat\config.json

mape2k commented 3 years ago

it seems to be moved to client config named config.json string "doCheckForUpdatesOnStartup": true, that located in the user profile %appdata%\Rocket.Chat\config.json

As mentioned in previous post update.json in resources directory of installation dir (C:\Program Files\Rocket.Chat\resources) did not work in versions between 3.0.0 and 3.0.5. Problem is fixed in #1861 - which is delivered in 3.0.6. So please check again on version 3.0.6 - 3.0.5 won't work.

jeanfbrito commented 2 years ago

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.

Thank you!